CtrlK
BlogDocsLog inGet started
Tessl Logo

reorder-policy

How to decide whether and how much to reorder a SKU. Load this whenever a task involves reorder recommendations, purchase orders, or "should we restock" questions.

69

Quality

84%

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

SKILL.md
Quality
Evals
Security

Quality

Content

90%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 highly actionable, concise, well-structured procedural skill with concrete formulas, thresholds, and a worked example that leave no ambiguity about what to do. The main gap is the absence of an explicit post-placement validation feedback loop and any progressive-disclosure structure for a skill that exceeds the simple-skill line count.

Suggestions

Add an explicit verification step after PO placement (e.g., confirm the appended purchase_orders.jsonl entry is well-formed and that no duplicate open PO exists for the SKU) to form a validate-fix-retry loop appropriate for a destructive/batch skill.

Since the skill exceeds 50 lines, consider splitting the Prioritization and Transfer-vs-reorder sections into a references/ file with a one-line pointer from SKILL.md to improve progressive-disclosure structure.

Add a brief error-recovery note for when input files (stock_levels.csv, products.csv) are missing or stale, so the workflow has a fallback path rather than implicitly assuming inputs are present.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence: it uses a compact inputs table, formulas, and a worked example with no over-explanation of what SKUs, reorder, or POs are; every section adds StockPilot-specific knowledge Claude would not already have.

5 / 5

Actionability

Guidance is fully executable: exact file paths, numeric formulas (safety_stock, order_qty), concrete thresholds (confidence < 0.6, $10,000, >30 days cover), and copy-paste-ready JSON output schemas, plus a fully worked numeric example.

5 / 5

Workflow Clarity

The four-step decision rules are clearly sequenced with explicit checkpoints (stop at step 1, escalate at step 3) and guardrails (confidence guard, no-duplicate-PO, batch accounting), but for a batch/destructive PO skill there is no explicit validate-then-fix-then-retry feedback loop after placement.

4 / 5

Progressive Disclosure

Content is well organized into clearly headed sections with no material that belongs in a separate file, but at ~90 lines (over the simple-skill threshold) and with no bundle files or one-level-deep references, it is a single self-contained document rather than an overview-plus-references structure.

4 / 5

Total

18

/

20

Passed

Description

78%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 well-crafted description that cleanly answers both what and when with concrete, natural trigger terms and a clear reorder/restock niche. Its only gap is moderate capability coverage and a slight overlap risk on the shared 'purchase orders' trigger.

DimensionReasoningScore

Specificity

"How to decide whether and how much to reorder a SKU" names the domain and two concrete actions (whether-to-reorder, how-much), but omits other capabilities like expedite, transfer, and prioritization, so it is not comprehensive.

3 / 5

Completeness

It explicitly answers what ("How to decide whether and how much to reorder a SKU") and when ("Load this whenever a task involves reorder recommendations, purchase orders, or 'should we restock' questions") with concrete trigger phrases.

5 / 5

Trigger Term Quality

"reorder recommendations, purchase orders, or 'should we restock' questions" provides good natural keywords with a synonym (reorder/restock); a few common variations (PO, replenishment) are missing, keeping it just below comprehensive.

4 / 5

Distinctiveness Conflict Risk

The reorder/restock niche is mostly distinct, but the "purchase orders" trigger carries minor overlap risk with a generic PO-creation skill, so it is not a clear-no-conflict 5.

4 / 5

Total

16

/

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.