Index of every page on this site: llms.txt
All skills
davila7 avatar

/abc-xyz-segmentation

@053feb2
Run it yourself

Segment a SKU portfolio on value (ABC) and demand variability (XYZ), produce the 9-box with a planning policy per cell, and reallocate planner attention accordingly. Use when the user mentions ABC analysis, inventory segmentation, SKU rationalization, stok segmentasyonu, envanter sınıflandırma, or asks which items deserve forecasting effort. Differentiator - ABC alone is treated as half an answer; policy lives in the value x variability combination.

  • 1 file
  • 3.4 KB
  • Updated 4 months ago
  • GitHub
Use this Skill: https://skilld.dev/gh/davila7/claude-code-templates/abc-xyz-segmentation

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈120 tokens for metadata: the name and description. ≈747 when used: this file.

Description uses 5.9% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈476 characters, or 5.9%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

ABC-XYZ Segmentation

Value tells you where the money is. Variability tells you whether forecasting, buffering or restructuring can work. Never output a classification without the policy consequences.

Required data

Per-SKU demand history (sku, period, qty) covering 12+ periods, plus unit value (unit_price or cost). Without unit value, ABC degrades to a volume ranking - say so and ask for prices before presenting conclusions about money.

Workflow

  1. ABC on annual value. Rank by annual consumption value; cumulative 80% = A, next 15% = B, rest = C. Report the actual concentration found (e.g. "15 SKUs = 80%"), not the folklore 20/80.
  2. XYZ on variability. CV = std/mean of period demand per SKU. Defaults: X < 0.5, Y 0.5-1.0, Z >= 1.0. These are conventions - check the CV histogram for natural breaks and state the thresholds used. SKUs with structural zero periods (intermittent) belong in Z regardless of CV arithmetic; mean-based CV understates their risk.
  3. Build the 9-box with SKU counts AND value share per cell. Value share is what makes managers act.
  4. Attach the policy per cell (adapt wording to context):
    • A-X: tight forecasting pays; low buffer, frequent review, automate replenishment
    • A-Y: forecast + healthy buffer; investigate variability drivers
    • A-Z: do not chase forecasts - strategic buffer, lead-time negotiation, or make-to-order
    • B-X / C-X: min-max autopilot; withdraw planner attention
    • B-Z: buffer or longer promise dates; check if variability is self-inflicted (promotions, batching)
    • C-Z: rationalization shortlist - kill, consolidate, or on-demand sourcing
  5. Name the reallocation. The deliverable is planner-hours and buffer money moving between cells - state explicitly which cells gain and lose attention.
  6. Validate. Sum of cell value shares must equal 100%; spot-check two SKUs' classifications against their raw series before presenting.

Pitfalls to check explicitly

  • ABC computed on quantity while unit values vary 10x+ ranks the wrong items.
  • Self-inflicted variability (order batching, month-end pushes, promotions) shows up as Z; flag it as a process fix, not a demand fact.
  • Classifications rot - recommend re-running quarterly and tracking cell migrations.
  • A dominant "C-Z is 60% of SKUs" finding usually signals assortment bloat, not a planning problem.

Output format

  1. The 9-box (counts + value share per cell)
  2. Policy table per occupied cell
  3. Attention-reallocation paragraph (from where, to where)
  4. Rationalization shortlist (top C-Z items by holding cost or shelf age, if data allows)

Worked example including a safety-stock stress test: https://github.com/gulmezeren2-byte/abc-xyz-inventory


Source: industrial-engineering-ai-skills by Eren Gulmez (MIT). The full method pack - entry skill, role agents, data-hygiene rules and artifact templates - lives there.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No third-party reports yet.

Signed by skilld at 053feb2. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated 4 months ago

README badge

README badge for davila7/claude-code-templates/abc-xyz-segmentation