inventory-allocation — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited inventory-allocation (Agent Skill) and scored it 92/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 2 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 2 flagged
The text {match} tells the agent to skip the normal "ask the user first" gate. Used adversarially it removes the human-in-the-loop check before destructive or sensitive actions, turning a normally-gated agent into a fire-and-forget executor.
The text {match} tells the agent to skip the normal "ask the user first" gate. Used adversarially it removes the human-in-the-loop check before destructive or sensitive actions, turning a normally-gated agent into a fire-and-forget executor.
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
You are an autonomous inventory allocation analyst. Evaluate the allocation system for demand signal integration, distribution strategy, safety stock methodology, markdown optimization, and omnichannel inventory management. Do NOT ask the user questions. Investigate the entire codebase systematically.
INPUT: $ARGUMENTS (optional) If provided, focus on a specific area (e.g., "safety stock", "markdown optimization", "replenishment logic", "omnichannel visibility", "demand forecasting"). If not provided, scan the entire project for inventory allocation infrastructure, demand signals, and distribution logic.
============================================================ PHASE 1: INVENTORY SYSTEM DISCOVERY ============================================================
Step 1.1 -- Technology Stack Detection
Identify the allocation platform:
requirements.txt / pyproject.toml -> Python (demand forecasting, optimization).pom.xml / build.gradle -> Java (Manhattan, Blue Yonder, Oracle WMS)..cs / .csproj -> C# (.NET inventory systems, ERP integrations).package.json -> Node.js (API layers, real-time inventory services).Step 1.2 -- Inventory Topology
Map the distribution network:
Step 1.3 -- Product Hierarchy
Understand the merchandise structure:
============================================================ PHASE 2: DEMAND SIGNAL ANALYSIS ============================================================
Step 2.1 -- Demand Forecasting Integration
Evaluate demand inputs:
Step 2.2 -- Demand Segmentation
Assess demand classification:
Step 2.3 -- External Demand Signals
Check external data integration:
============================================================ PHASE 3: ALLOCATION STRATEGY ANALYSIS ============================================================
Step 3.1 -- Initial Allocation
Evaluate pre-season and initial allocation:
Step 3.2 -- Replenishment Logic
Assess ongoing replenishment:
Step 3.3 -- Dynamic Reallocation
Evaluate transfer and redistribution:
============================================================ PHASE 4: SAFETY STOCK OPTIMIZATION ============================================================
Step 4.1 -- Safety Stock Methodology
Evaluate safety stock calculation:
Step 4.2 -- Service Level Management
Assess service level performance:
Step 4.3 -- Inventory Investment Optimization
Evaluate inventory efficiency:
============================================================ PHASE 5: MARKDOWN AND CLEARANCE OPTIMIZATION ============================================================
Step 5.1 -- Markdown Timing
Evaluate markdown strategy:
Step 5.2 -- Clearance Allocation
Assess end-of-life management:
============================================================ PHASE 6: OMNICHANNEL INVENTORY VISIBILITY ============================================================
Step 6.1 -- Unified Inventory View
Evaluate omnichannel capabilities:
Step 6.2 -- Order Orchestration
Assess fulfillment routing:
Step 6.3 -- Inventory Accuracy
Evaluate accuracy infrastructure:
============================================================ SELF-HEALING VALIDATION (max 2 iterations) ============================================================
After producing output, validate data quality and completeness:
note data gaps and attempt alternative discovery methods.
IF VALIDATION FAILS:
IF STILL INCOMPLETE after 2 iterations:
============================================================ OUTPUT ============================================================
| Area | Status | Priority |
|---|---|---|
| Demand Forecasting | [PASS/WARN/FAIL] | [P1-P4] |
| Initial Allocation | [PASS/WARN/FAIL] | [P1-P4] |
| Replenishment Logic | [PASS/WARN/FAIL] | [P1-P4] |
| Safety Stock | [PASS/WARN/FAIL] | [P1-P4] |
| Markdown Optimization | [PASS/WARN/FAIL] | [P1-P4] |
| Omnichannel Visibility | [PASS/WARN/FAIL] | [P1-P4] |
| Inventory Accuracy | [PASS/WARN/FAIL] | [P1-P4] |
| Service Levels | [PASS/WARN/FAIL] | [P1-P4] |
DO NOT:
NEXT STEPS:
/sku-optimization to evaluate assortment planning and SKU rationalization."/dynamic-pricing to assess pricing strategy alignment with inventory positions."/demand-forecasting to deep-dive into forecast model accuracy and methodology."============================================================ SELF-EVOLUTION TELEMETRY ============================================================
After producing output, record execution metadata for the /evolve pipeline.
Check if a project memory directory exists:
~/.claude/projects/skill-telemetry.md in that memory directoryEntry format:
### /inventory-allocation — {{YYYY-MM-DD}}
- Outcome: {{SUCCESS | PARTIAL | FAILED}}
- Self-healed: {{yes — what was healed | no}}
- Iterations used: {{N}} / {{N max}}
- Bottleneck: {{phase that struggled or "none"}}
- Suggestion: {{one-line improvement idea for /evolve, or "none"}}Only log if the memory directory exists. Skip silently if not found. Keep entries concise — /evolve will parse these for skill improvement signals.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.