Claude Code SkillOperations

Abc Xyz Segmentation

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.

Install with the Claude Code Templates CLI
$ npx claude-code-templates@latest --skill="operations/abc-xyz-segmentation" --yes

Requires Claude Code. The command adds this skill to your project's .claudedirectory — nothing runs on ToolZip's servers.

What's inside this skill

Component source

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

  • 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.
  • 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.
  • Build the 9-box with SKU counts AND value share per cell. Value share is what makes managers act.
  • 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

  • Name the reallocation. The deliverable is planner-hours and buffer money moving between cells - state explicitly which cells gain and lose attention.
  • 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

  • The 9-box (counts + value share per cell)
  • Policy table per occupied cell
  • Attention-reallocation paragraph (from where, to where)
  • 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.

Type
Skill
Category
Operations
Installs
Source
GitHub ↗

Related Claude Code Skills

SkillOperations

Forecast Accuracy Review

Evaluate demand-forecast quality honestly - WMAPE, bias and Forecast Value Added against a naive benchmark over a rolling-origin backtest. Use when the user mentions forecast accuracy, MAPE, demand planning performance, tahmin doğruluğu, talep tahmini, or asks whether a forecasting process or tool is worth it. Differentiator - judges the process (value added vs doing nothing), not just the model.

1 installsView →
SkillOperations

Root Cause Pareto

Build a decision-grade Pareto for downtime, defects, complaints or delays - with unit-of-measure discipline, category hygiene, exposure normalization and a follow-up metric. Use when the user mentions pareto analysis, kök neden, duruş analizi, downtime, arıza analizi, defect ranking, şikayet analizi, 80/20 analysis. Differentiator - treats the Pareto as the start of a causal investigation, not a bar chart deliverable.

1 installsView →
SkillOperations

Weekly Ops Report

Turn raw operational data into a weekly management report that answers exactly three questions - what changed, where is it concentrated, what needs a decision. Use when the user mentions weekly report, haftalık rapor, yönetim raporu, ops review, KPI summary, or asks to summarize operational data for managers. Differentiator - contract-first reporting with plain-language findings and driver decomposition, never a chart dump.

1 installsView →
SkillOperations

Otif Analysis

Audit delivery performance from order-level data - compute the OTIF metric ladder (tolerant to strict), find where lateness concentrates, and quantify the gap between the reported KPI and what customers experience. Use when the user mentions OTIF, on-time delivery, delivery performance, late orders, teslimat performansı, zamanında teslimat, or asks why customers complain despite a high on-time score. Differentiator - exposes measurement choices before optimizing operations.

View →
SkillOperations

Safety Stock Review

Size or audit safety stock with assumption checks - the z*sigma*sqrt(LT) formula plus an empirical stress test of what it actually delivers (cycle service vs fill rate) per variability class. Use when the user mentions safety stock, emniyet stoku, emniyet stoğu, reorder point, service level, stok seviyesi belirleme. Differentiator - refuses to hand back a number without validating the demand-distribution assumptions behind it.

View →
SkillCreative Design

Frontend Design

Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.

4.2k installsView →

Catalog data and component content are sourced from the open-source davila7/claude-code-templates project (MIT license). ToolZip curates the listing and writes original descriptions; every component links back to its original source. Claude Code is a product of Anthropic. ToolZip is an independent catalog and is not affiliated with or endorsed by Anthropic.