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.

49

Quality

53%

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/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

48%Scale 1-5

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

This skill contains comprehensive domain expertise for inventory demand planning but suffers significantly from verbosity — it reads more like a textbook than a skill file, explaining many concepts Claude already knows. The decision frameworks and tables are well-structured and provide concrete thresholds, but the lack of executable code and missing bundle files weaken actionability and progressive disclosure. The duplicate 'When to Use' section and monolithic structure suggest the content needs significant reorganization.

Suggestions

Drastically reduce the Core Knowledge section by removing explanations of well-known concepts (exponential smoothing, EOQ formula, ABC classification) and keeping only the retailer-specific thresholds, decision rules, and non-obvious guidance that Claude wouldn't already know.

Move detailed method descriptions and formulas into reference files (e.g., references/forecasting-methods.md, references/safety-stock.md) and keep only the decision tables and key thresholds in the main SKILL.md.

Add executable code examples — e.g., Python snippets for safety stock calculation, Croston's method implementation, or promotional lift estimation — to make the guidance directly actionable.

Remove the duplicate 'When to Use' section at the bottom and provide the actual bundle files (edge-cases.md, communication-templates.md, decision-frameworks.md) that are referenced.

DimensionReasoningScore

Conciseness

The skill is extremely verbose at ~400+ lines, extensively explaining forecasting methods, safety stock formulas, and inventory concepts that Claude already knows well. Much of this reads like a textbook chapter rather than actionable instructions that add novel knowledge. The detailed explanations of exponential smoothing parameters, EOQ formulas, and ABC/XYZ classification are standard domain knowledge that doesn't need this level of exposition.

2 / 5

Actionability

The skill provides concrete decision tables, specific thresholds (e.g., Z-scores, WMAPE targets, lift percentages), and formulas, which is good. However, there is no executable code, no specific tool commands, and much of the guidance remains at the conceptual/instructional level rather than providing copy-paste-ready implementations. The communication templates are sketched but not fully fleshed out (deferred to reference files).

3 / 5

Workflow Clarity

The decision frameworks are well-structured with clear tables mapping conditions to actions. The escalation protocols have explicit triggers, timelines, and chains. The promotional lift decision framework follows a clear numbered sequence. However, there are no explicit validation/verification checkpoints in the workflows — for example, the markdown timing and slow-mover kill processes lack feedback loops to verify that actions taken achieved the desired outcome.

4 / 5

Progressive Disclosure

The skill references external files (edge-cases.md, communication-templates.md, decision-frameworks.md) which is good structure, but no bundle files are provided so these references are broken. The main file itself is far too long — much of the core knowledge section (forecasting methods, safety stock formulas, ABC/XYZ classification) could be moved to reference files. The 'When to Use' section appears twice (top and bottom), indicating poor organization.

3 / 5

Total

12

/

20

Passed

Description

58%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 names a clear domain (multi-location retail) and lists four concrete capabilities, giving it reasonable specificity and distinctiveness. However, it lacks an explicit 'Use when...' clause, which is critical for skill selection, and the trigger terms lean technical rather than matching natural user language. The phrase 'Codified expertise for' is somewhat vague filler that doesn't add selection value.

Suggestions

Add an explicit 'Use when...' clause with trigger phrases, e.g., 'Use when the user asks about inventory planning, stock replenishment, demand prediction, or promotional impact at retail locations.'

Include natural synonyms and simpler terms users might say, such as 'inventory management', 'stock levels', 'reorder points', 'supply chain planning', or 'retail forecasting'.

Replace the vague opener 'Codified expertise for' with a direct action-oriented statement, e.g., 'Performs demand forecasting, optimises safety stock levels, plans replenishment, and estimates promotional lift for multi-location retailers.'

DimensionReasoningScore

Specificity

Lists several specific actions: demand forecasting, safety stock optimisation, replenishment planning, and promotional lift estimation. Also specifies the domain (multi-location retailers). Minor gaps in that it doesn't elaborate on sub-actions or outputs, but the named capabilities are concrete.

4 / 5

Completeness

The 'what' is reasonably clear (demand forecasting, safety stock optimisation, etc.), but there is no explicit 'when' clause. There is no 'Use when...' guidance or trigger phrases telling Claude when to select this skill, which caps this dimension at 3 per the rubric.

3 / 5

Trigger Term Quality

Includes domain-relevant terms like 'demand forecasting', 'safety stock', 'replenishment planning', and 'promotional lift estimation', but these are somewhat technical. Missing natural user phrases like 'inventory management', 'stock levels', 'reorder point', 'supply chain', or simpler synonyms a user might actually say.

3 / 5

Distinctiveness Conflict Risk

The combination of retail supply chain functions (demand forecasting, safety stock, replenishment, promotional lift) at multi-location retailers is fairly distinctive. Minor overlap risk with general supply chain or inventory skills, but the specificity to retail and the enumerated functions reduce conflict risk.

4 / 5

Total

14

/

20

Passed

Validation

90%

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

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

10

/

11

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.