CtrlK
BlogDocsLog inGet started
Tessl Logo

forecasting

How to produce a demand forecast for a SKU, and when to delegate that to a subagent vs. compute it yourself. Load this for any task involving "forecast", "how much will we sell", "next month", promos, or seasonal SKUs.

93

1.40x
Quality

90%

Does it follow best practices?

Impact

98%

1.40x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

92%Weight 40%Scale 1-5

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

The body is highly actionable and well-structured: concrete commands, explicit decision gates, validation/escalation feedback loops, and a worked example. The only ding is a handful of narrative asides that slightly dilute token efficiency.

DimensionReasoningScore

Conciseness

Mostly lean and assumes Claude's competence (no explaining what a forecast or rolling mean is), but a few narrative asides — the F1 agent anecdote and 'the 90 rows live there, not here' — could be trimmed to fully earn every token.

4 / 5

Actionability

Fully executable: copy-paste bash commands with concrete args, an explicit JSON contract, specific confidence thresholds, and a worked example covering the common Path B case.

5 / 5

Workflow Clarity

Clear two-path sequence with explicit boolean gates and validation checkpoints (strict JSON parsing, the callable_agents fallback, and the escalate-don't-auto-order feedback loop for uncertain promos).

5 / 5

Progressive Disclosure

No bundle files exist; the self-contained body is organized into clearly signaled sections with only one-level-deep external script paths and no nested references, appropriate for a single-file skill.

5 / 5

Total

19

/

20

Passed

Description

87%Weight 40%Scale 1-5

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 is strong: it states concrete capabilities, gives natural user-facing trigger phrases, and clearly separates what the skill does from when to load it. Minor trigger-term coverage gaps (reorder, stockout) keep it just short of a perfect mark on two dimensions.

DimensionReasoningScore

Specificity

Names the domain and several concrete actions — 'produce a demand forecast for a SKU' and 'delegate that to a subagent vs. compute it yourself' — with only minor coverage gaps, fitting the anchor that lists several specific actions.

4 / 5

Completeness

Explicitly answers both what (produce a forecast; when to delegate vs compute) and when ('Load this for any task involving...') with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

Strong natural trigger phrases users would actually say ('forecast', 'how much will we sell', 'next month', promos, seasonal SKUs); a few related terms like reorder/stockout/days-of-cover are absent, so it sits just below comprehensive.

4 / 5

Distinctiveness Conflict Risk

A clear forecasting niche with distinct triggers ('forecast', 'how much will we sell', seasonal SKUs) and minimal overlap risk with adjacent skills like reorder-policy.

5 / 5

Total

18

/

20

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.

Validation16 / 16 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.