CtrlK
BlogDocsLog inGet started
Tessl Logo

weekly-report

Structure and data sources for the weekly inventory report. Load this when the task is "weekly report", "Monday report", or "summarize inventory status".

89

1.03x
Quality

88%

Does it follow best practices?

Impact

87%

1.03x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

87%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a strong, well-crafted skill that provides highly actionable guidance with excellent conciseness. It gives Claude exact file paths, column names, formulas, and a complete output template, all without unnecessary explanation. The main weakness is the lack of any validation or error-handling guidance for a batch data processing task over large CSVs, which prevents the workflow clarity from reaching the top score.

Suggestions

Add a brief validation checkpoint after loading CSVs, e.g., 'Verify row counts and that joins produce non-null results before generating the report' to catch data issues early.

DimensionReasoningScore

Conciseness

The content is lean and efficient. It doesn't explain what CSVs are, how Python works, or what inventory management is. Every section delivers specific, non-obvious information (file paths, column names, thresholds, cadence rules). The brief repetition in 'Do this in code' reinforces a critical constraint without excessive padding.

3 / 3

Actionability

Provides exact file paths, specific column names (on_hand, avg_daily_sales, lead_time_days, promo_next_month, is_seasonal), concrete formulas (on_hand / avg_daily_sales over 14d), exact thresholds (14d cover, >5 business days), and a complete markdown template. Claude can execute this without guessing any details.

3 / 3

Workflow Clarity

The skill clearly describes what to produce and from which data sources, and the cadence table is well-structured. However, there are no explicit validation checkpoints — e.g., verifying CSV loads succeeded, checking for missing joins, or confirming row counts. For a batch operation over ~67k rows producing a report, a validation step (even a simple sanity check) would be expected for a score of 3.

2 / 3

Progressive Disclosure

For a skill of this size (~60 lines) with no bundle files, the content is well-organized into logical sections (Structure, Operating cadence, Aging-PO check, Data sources, execution constraint). Each section is clearly headed and serves a distinct purpose. No external references are needed and none are falsely promised.

3 / 3

Total

11

/

12

Passed

Description

89%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description excels at providing explicit trigger guidance and occupying a distinct niche, making it easy for Claude to know when to select it. However, the 'what' portion is somewhat vague—'structure and data sources' doesn't convey specific actions or outputs the skill produces. Adding concrete actions would strengthen the description.

Suggestions

Add specific concrete actions the skill performs, e.g., 'Aggregates stock levels across warehouses, identifies low-stock items, and formats a summary table for the weekly inventory report.'

DimensionReasoningScore

Specificity

It names the domain ('weekly inventory report') and mentions 'structure and data sources,' but does not list specific concrete actions like 'aggregate stock levels,' 'calculate turnover rates,' or 'generate summary tables.'

2 / 3

Completeness

Clearly answers both 'what' (structure and data sources for the weekly inventory report) and 'when' (explicit 'Load this when...' clause with specific trigger phrases).

3 / 3

Trigger Term Quality

Includes natural trigger terms users would say: 'weekly report,' 'Monday report,' 'summarize inventory status.' These are concrete phrases that match real user requests well.

3 / 3

Distinctiveness Conflict Risk

The combination of 'weekly inventory report,' 'Monday report,' and 'summarize inventory status' creates a clear, narrow niche that is unlikely to conflict with other skills.

3 / 3

Total

11

/

12

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository
anthropics/cwc-workshops
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.