CtrlK
BlogDocsLog inGet started
Tessl Logo

inventory-demand-planning

Codified expertise for demand forecasting, safety stock optimisation, replenishment planning, and promotional lift estimation at multi-location retailers.

59

Quality

68%

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

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/inventory-demand-planning/SKILL.md

The canonical home for this skill is inventory-demand-planning in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

67%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 a well-structured, highly actionable knowledge base with clear decision frameworks and sound progressive disclosure to three reference files, though some narrative prose could be trimmed for token efficiency.

Suggestions

Tighten the Role and Context paragraph and surrounding explanatory prose; keep the operational specifics (formulas, thresholds, tables) which earn their tokens.

Consider moving the full Communication Patterns examples and the Performance Indicators detail into the existing references to slim the core body.

Add a short explicit validation/review loop note for batch replenishment actions (e.g., re-check inventory position after PO placement) to strengthen workflow checkpoints.

DimensionReasoningScore

Conciseness

Mostly efficient specialized operational knowledge (Z-scores, WAPE targets, lift ranges) that Claude would not reliably produce at this specificity, but the long Role/Context paragraph and surrounding narrative prose could be tightened without losing substance.

3 / 5

Actionability

Provides concrete formulas (SS = Z × σ_d × √(LT + RP), EOQ = √(2DS/H)), specific thresholds (Z=1.65, tracking signal ±4, WMAPE <25%), and decision tables with minor gaps since no executable computational scripts are included.

4 / 5

Workflow Clarity

Multi-step decision frameworks (forecast method selection, markdown timing, slow-mover kill) are clearly sequenced with explicit review triggers and escalation timelines acting as checkpoints, with only minor validation gaps.

4 / 5

Progressive Disclosure

SKILL.md serves as an overview with well-signaled one-level-deep links to three real reference files (decision-frameworks.md, edge-cases.md, communication-templates.md), each summarized inline then deferred; the body itself is fairly large but well organized.

4 / 5

Total

15

/

20

Passed

Description

70%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 clearly scopes a specialized retail demand-planning skill with concrete capability areas and strong distinctiveness, but it omits an explicit 'Use when...' trigger clause and could use more natural synonym keywords.

Suggestions

Add an explicit 'Use when...' clause listing concrete trigger situations (e.g., forecasting product demand, setting safety stock, planning replenishment, sizing promotional lift).

Reword 'Codified expertise for' as direct third-person actions ('Forecasts demand, optimises safety stock, plans replenishment, estimates promotional lift') to lift specificity.

Include natural synonyms users say ('inventory planning', 'stockouts', 'demand planning') alongside the current terms.

DimensionReasoningScore

Specificity

Lists four concrete capability areas ('demand forecasting, safety stock optimisation, replenishment planning, and promotional lift estimation'), but frames them as scope under 'Codified expertise for' rather than as action verbs, leaving minor coverage gaps versus the comprehensive anchor.

4 / 5

Completeness

The 'what' is clearly stated, but there is no explicit 'Use when...' trigger clause or equivalent in the description, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

Good domain keywords ('demand forecasting', 'safety stock', 'replenishment planning', 'promotional lift', 'multi-location retailers') that practitioners would naturally say, but missing common synonyms like 'inventory planning', 'stockouts', or 'demand planning'.

4 / 5

Distinctiveness Conflict Risk

Targets a clear niche (inventory demand planning at multi-location retailers) with distinct, specialized triggers and minimal overlap risk with other skills.

5 / 5

Total

16

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-Skills
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.