CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

inventory-demand-planning

Codified expertise for demand forecasting, safety stock optimization, replenishment planning, and promotional lift estimation at multi-location retailers. Informed by demand planners with 15+ years experience managing hundreds of SKUs. Includes forecasting method selection, ABC/XYZ analysis, seasonal transition management, and vendor negotiation frameworks. Use when forecasting demand, setting safety stock, planning replenishment, managing promotions, or optimizing inventory levels.

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

The canonical home for this skill is inventory-demand-planning in affaan-m/ECC

SKILL.md
Quality
Evals
Security

Quality

Content

71%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.

A dense, expert-level knowledge skill whose real value is the specific thresholds, formulas, and decision matrices — actionability is excellent throughout. Its weaknesses are token efficiency (re-explains standard forecasting/inventory concepts Claude already knows) and the lack of any progressive disclosure, with everything packed into one long SKILL.md instead of being split across reference files.

Suggestions

Trim the textbook definitions of standard methods (moving averages, Holt-Winters variants, EOQ formula, MAPE/Bias definitions) and keep only the selection guidance, parameter ranges, and practitioner thresholds that Claude would not derive on its own.

Split the decision frameworks, communication templates, and escalation protocols into one-level-deep reference files (e.g., references/decision-frameworks.md, references/communication-templates.md) linked from a leaner SKILL.md overview.

Replace the generic 'Additional Resources' section, which references no actual files, with concrete links to the new bundle files or remove it.

DimensionReasoningScore

Conciseness

The body defines concepts Claude already knows — 'Single exponential smoothing (SES, alpha 0.1–0.3) suits stationary demand', 'EOQ = √(2DS/H) where D = annual demand, S = ordering cost', and 'MAPE (Mean Absolute Percentage Error)' — alongside the 'Role and Context' scene-setting, so it is mostly efficient but could be tightened to just the practitioner thresholds and selection rules.

3 / 5

Actionability

Highly concrete instruction-only guidance: exact formulas ('SS = Z × √(LT_avg × σ_d² + d_avg² × σ_LT²)'), quantitative thresholds (Z-scores by segment, 'Bias < ±5% is healthy', 'Tracking Signal... exceeds ±4'), decision tables, and a worked example with numbers ('Baseline: 500 units/week. Promotional lift estimate: 180% (900 incremental). Post-promo dip: −35% for 2 weeks').

5 / 5

Workflow Clarity

'How It Works' gives a clear 6-step sequence closing with an explicit feedback loop ('Monitor forecast accuracy (MAPE, bias) and adjust models in the next planning cycle') and quantitative review triggers, but the checkpoints sit in separate tables rather than being integrated into the steps and intermediate steps lack validation. Not 5 for those distributed, non-inline checkpoints; not 3 because the triggers and monitoring thresholds are explicit, not implicit.

4 / 5

Progressive Disclosure

Good internal structure (## sections, ### subsections, tables), but it is a 225-line monolith with no bundle files: decision frameworks, communication templates, and escalation protocols are inlined content that clearly belongs in separate reference files, and 'Additional Resources' points to no actual files. Not 2 because the section organization is strong rather than minimal.

3 / 5

Total

15

/

20

Passed

Description

92%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.

A strong description: it names concrete capabilities comprehensively, uses third person, and closes with an explicit 'Use when...' clause covering five natural trigger phrases. The only weaknesses are a credential sentence that adds no capability information and a few missing synonyms ('demand planning', 'stockouts') in the trigger list.

DimensionReasoningScore

Specificity

Lists multiple specific concrete capabilities — 'demand forecasting, safety stock optimization, replenishment planning, and promotional lift estimation' plus 'forecasting method selection, ABC/XYZ analysis, seasonal transition management, and vendor negotiation frameworks' — with comprehensive coverage of the domain. Not 4: there are no meaningful gaps in the action list; the 'Informed by demand planners with 15+ years experience' sentence is mild padding but does not make the actions vague.

5 / 5

Completeness

Explicitly answers both what ('Codified expertise for demand forecasting, safety stock optimization, replenishment planning, and promotional lift estimation at multi-location retailers') and when ('Use when forecasting demand, setting safety stock, planning replenishment, managing promotions, or optimizing inventory levels') with five concrete trigger phrases — a direct match for the 5 anchor.

5 / 5

Trigger Term Quality

'Use when forecasting demand, setting safety stock, planning replenishment, managing promotions, or optimizing inventory levels' covers natural phrases users would say. Not 5: common synonyms such as 'demand planning', 'stockouts', or 'buy plan / purchase orders' are missing, so coverage is good but not comprehensive with synonyms.

4 / 5

Distinctiveness Conflict Risk

'multi-location retailers' plus specialized planning vocabulary (safety stock, replenishment, promotional lift, ABC/XYZ) carves a clear niche with minimal conflict risk; only 'vendor negotiation frameworks' brushes against a generic procurement skill, which is too minor to reduce the score.

5 / 5

Total

19

/

20

Passed

Validation

81%

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

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

13

/

16

Passed

Repository

valeriibeck-star/claude-skills

Path

skills/inventory-demand-planning/SKILL.md

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.