Come usare
- Copia il comando e controlla il pacchetto prima di installarlo nel tuo ambiente agente.
- Controlla strumenti, credenziali e ambienti richiesti nel documento originale.
- Descrivi input e risultato desiderato; confronta l’output con le fonti.
npx skills add https://github.com/shah-mohammed/ecommerce-claude-skills --skill inventory-risk-brief-ecommercePrima di iniziare
- L’installazione non include abbonamenti, quote API o accesso ai file.
- Stelle e installazioni indicano attività, non un test indipendente di qualità o sicurezza.
Contenuto dal repository con titoli, esempi, codice, tabelle, link e immagini preservati.
Inventory Risk Brief - E-commerce
Use this skill when
The user wants an inventory-aware growth or promo review from exports.
Common requests:
- "Review this inventory export."
- "Which products are at risk of stockout?"
- "Which products need promo support?"
- "What should we avoid pushing in ads?"
Required input
Minimum useful input:
- Inventory export with SKU, product name, current stock, and variant.
- Sales export for the last 30, 60, or 90 days.
- Date range and sales velocity.
- Promo calendar or planned campaign notes if available.
Recommended columns:
- SKU
- product name
- variant
- current inventory
- units sold
- revenue
- margin or priority flag if available
- incoming stock quantity and ETA if available
- supplier lead time if available
Before analysis
- Confirm the purpose: prevent stockout, reduce overstock, plan promo, or protect paid traffic.
- Ask for exports if the user only describes inventory from memory.
- Mark missing lead time, incoming stock, and margin data as caveats.
- Do not pretend to run demand forecasting.
Analysis workflow
- Normalize SKU and product names.
- Calculate simple signals where data allows:
- recent sales velocity
- days of inventory remaining
- sell-through risk
- slow mover status
- promo conflict risk
- Classify products:
- stockout risk
- overstock risk
- safe to promote
- do not scale traffic
- needs more data
- Tie risks to marketing action.
- Name what cannot be decided yet. Reorder quantity needs lead time and incoming stock; a promo decision needs margin. Where those are absent, hand the owner the question rather than a recommendation built on a guess.
Decision and evidence standard
Every finding should include:
- Evidence tag:
export,screenshot,url,review_cluster,support_ticket,return_reason,policy,feed_diagnostics,margin_csv,inventory_export,hypothesis, orneeds_data. - Severity: low, medium, high, or critical.
- Confidence: low, medium, or high.
- Business impact: revenue, margin, cashflow, retention, conversion, support_load, or risk.
- Effort: XS, S, M, or L.
- Owner decision: donow, test, investigate, monitor, ignore, or approvalneeded.
If the evidence is weak, mark the finding as hypothesis or needs_data and lower confidence.
Output format
Inventory verdict
Short owner-level summary.
Risk table
| Product/SKU | Status | Evidence | Marketing implication | Recommended action |
|---|
Promo notes
Products suitable for promotion, products to protect, and products to avoid scaling.
Missing data
Fields needed for better confidence.
Example input and output
Input:
- inventory export
- 60-day sales export
- incoming stock ETA
- promo calendar
Good output excerpt:
| Finding | Evidence | Severity | Confidence | Business impact | Effort | Owner decision |
|---|---|---|---|---|---|---|
| Bestseller SKU may stock out during planned campaign | inventory_export, export | high | medium | revenue/risk | S | approval_needed |
| Slow-moving variant has high stock and low recent sales velocity | inventory_export, export | medium | medium | cashflow | S | test |
What not to do yet: infer stock risk without inventory or sales exports, or recommend purchase orders without lead time and approval.
Guardrails
- Requires an inventory or sales export. Do not infer stock risk from product names alone.
- Do not replace ERP, inventory planning, or demand forecasting systems.
- Do not recommend purchase orders without lead time, margin, and business approval.
- Do not recommend pushing products that may stock out during the campaign.
- Do not ignore variant-level constraints.