Agent skill

Inventory Demand Planning

by sickn33 in sickn33/agentic-awesome-skills

Codified expertise for demand forecasting, safety stock optimisation, replenishment planning, and promotional lift estimation at multi-location retailers.

MITAuto-check passedData & Analytics

Install Inventory Demand Planning

skills CLI
$ npx skills add sickn33/agentic-awesome-skills --skill inventory-demand-planning -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install sickn33/agentic-awesome-skills inventory-demand-planning --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/inventory-demand-planning .claude/skills/inventory-demand-planning && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
inventory-demand-planning
GitHub stars
47k
Used in
8 other repos
Token cost
~6.5k tokens
SKILL.md length
3,142 words
Files
4 (incl. references)
Skills in repo
1,493
Repo updated
First seen
Licence
MIT

At a glance

Codified expertise for demand forecasting, safety stock optimisation, replenishment planning, and promotional lift estimation at multi-location retailers.

  • Works in 5 steps: Is there historical lift data for this… → No own-item data but same category has… → Brand-new category or promo type? → Use… → …
  • Tasks that involve Forecasting and time series
  • SKILL.md covers When to Use, Role and Context, Core Knowledge and Decision Frameworks, plus 6 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Inventory Demand Planning is an agent skill from sickn33/agentic-awesome-skills. Codified expertise for demand forecasting, safety stock optimisation, replenishment planning, and promotional lift estimation at multi-location retailers.

Its SKILL.md is about 6.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including reference files (for example `references/communication-templates.md`, `references/decision-frameworks.md` and `references/edge-cases.md`).

It sits in Data & Analytics, covering Forecasting and time series. The repository describes itself as: AAS Core is the local, agent-first control plane for complete catalog discovery, agent-owned selection, stack validation, and planning, backed by 2,400+ agentic skills. Includes… The licence is MIT.

When your agent uses it

  • Tasks that involve Forecasting and time series

Example prompts

  • “/inventory-demand-planning”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Is there historical lift data for this SKU-promo type combination? → Use own-item lift with recency weighting (most recent 3 promos…
  2. No own-item data but same category has been promoted? → Use analogous item lift adjusted for price point and brand tier.
  3. Brand-new category or promo type? → Use conservative category-average lift discounted 20%. Build in a wider safety stock buffer for the…
  4. Cross-promoted with another category? → Model the traffic driver separately from the cross-promo beneficiary. Apply cross-elasticity…
  5. Always model the post-promo dip. Default to 40% of incremental lift, concentrated 60/30/10 across the three post-promo weeks.

What it can do on your machine

Read from SKILL.md and the folder at commit 680176d. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Inventory Demand Planning loads about 6.5k tokens when it runs, and up to ~37k if it reads all its reference files. Until then it costs about 45 tokens; SKILL.md has 3,142 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~45
When it runs · the whole SKILL.md, loaded when a task matches
~6.5k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~37k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from sickn33/agentic-awesome-skills at commit 680176d, republished under its MIT licence (© sickn33). 3,142 words, ~6,516 tokens.

Download SKILL.mdSave it as .claude/skills/inventory-demand-planning/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.
name
inventory-demand-planning
description
Codified expertise for demand forecasting, safety stock optimisation, replenishment planning, and promotional lift estimation at multi-location retailers.
risk
safe
source
https://github.com/ai-evos/agent-skills
date_added
2026-02-27

When to Use

Use this skill when forecasting product demand, calculating optimal safety stock levels, planning inventory replenishment cycles, estimating the impact of retail promotions, or conducting ABC/XYZ inventory segmentation.

Inventory Demand Planning

Role and Context

You are a senior demand planner at a multi-location retailer operating 40–200 stores with regional distribution centers. You manage 300–800 active SKUs across categories including grocery, general merchandise, seasonal, and promotional assortments. Your systems include a demand planning suite (Blue Yonder, Oracle Demantra, or Kinaxis), an ERP (SAP, Oracle), a WMS for DC-level inventory, POS data feeds at the store level, and vendor portals for purchase order management. You sit between merchandising (which decides what to sell and at what price), supply chain (which manages warehouse capacity and transportation), and finance (which sets inventory investment budgets and GMROI targets). Your job is to translate commercial intent into executable purchase orders while minimizing both stockouts and excess inventory.

Core Knowledge

Forecasting Methods and When to Use Each

Moving Averages (simple, weighted, trailing): Use for stable-demand, low-variability items where recent history is a reliable predictor. A 4-week simple moving average works for commodity staples. Weighted moving averages (heavier on recent weeks) work better when demand is stable but shows slight drift. Never use moving averages on seasonal items — they lag trend changes by half the window length.

Exponential Smoothing (single, double, triple): Single exponential smoothing (SES, alpha 0.1–0.3) suits stationary demand with noise. Double exponential smoothing (Holt's) adds trend tracking — use for items with consistent growth or decline. Triple exponential smoothing (Holt-Winters) adds seasonal indices — this is the workhorse for seasonal items with 52-week or 12-month cycles. The alpha/beta/gamma parameters are critical: high alpha (>0.3) chases noise in volatile items; low alpha (<0.1) responds too slowly to regime changes. Optimize on holdout data, never on the same data used for fitting.

Seasonal Decomposition (STL, classical, X-13ARIMA-SEATS): When you need to isolate trend, seasonal, and residual components separately. STL (Seasonal and Trend decomposition using Loess) is robust to outliers. Use seasonal decomposition when seasonal patterns are shifting year over year, when you need to remove seasonality before applying a different model to the de-seasonalized data, or when building promotional lift estimates on top of a clean baseline.

Causal/Regression Models: When external factors drive demand beyond the item's own history — price elasticity, promotional flags, weather, competitor actions, local events. The practical challenge is feature engineering: promotional flags should encode depth (% off), display type, circular feature, and cross-category promo presence. Overfitting on sparse promo history is the single biggest pitfall. Regularize aggressively (Lasso/Ridge) and validate on out-of-time, not out-of-sample.

Machine Learning (gradient boosting, neural nets): Justified when you have large data (1,000+ SKUs × 2+ years of weekly history), multiple external regressors, and an ML engineering team. LightGBM/XGBoost with proper feature engineering outperforms simpler methods by 10–20% WAPE on promotional and intermittent items. But they require continuous monitoring — model drift in retail is real and quarterly retraining is the minimum.

Forecast Accuracy Metrics
  • MAPE (Mean Absolute Percentage Error): Standard metric but breaks on low-volume items (division by near-zero actuals produces inflated percentages). Use only for items averaging 50+ units/week.
  • Weighted MAPE (WMAPE): Sum of absolute errors divided by sum of actuals. Prevents low-volume items from dominating the metric. This is the metric finance cares about because it reflects dollars.
  • Bias: Average signed error. Positive bias = forecast systematically too high (overstock risk). Negative bias = systematically too low (stockout risk). Bias < ±5% is healthy. Bias > 10% in either direction means a structural problem in the model, not noise.
  • Tracking Signal: Cumulative error divided by MAD (mean absolute deviation). When tracking signal exceeds ±4, the model has drifted and needs intervention — either re-parameterize or switch methods.
Safety Stock Calculation

The textbook formula is SS = Z × σ_d × √(LT + RP) where Z is the service level z-score, σ_d is the standard deviation of demand per period, LT is lead time in periods, and RP is review period in periods. In practice, this formula works only for normally distributed, stationary demand.

Service Level Targets: 95% service level (Z=1.65) is standard for A-items. 99% (Z=2.33) for critical/A+ items where stockout cost dwarfs holding cost. 90% (Z=1.28) is acceptable for C-items. Moving from 95% to 99% nearly doubles safety stock — always quantify the inventory investment cost of the incremental service level before committing.

Lead Time Variability: When vendor lead times are uncertain, use SS = Z × √(LT_avg × σ_d² + d_avg² × σ_LT²) — this captures both demand variability and lead time variability. Vendors with coefficient of variation (CV) on lead time > 0.3 need safety stock adjustments that can be 40–60% higher than demand-only formulas suggest.

Lumpy/Intermittent Demand: Normal-distribution safety stock fails for items with many zero-demand periods. Use Croston's method for forecasting intermittent demand (separate forecasts for demand interval and demand size), and compute safety stock using a bootstrapped demand distribution rather than analytical formulas.

New Products: No demand history means no σ_d. Use analogous item profiling — find the 3–5 most similar items at the same lifecycle stage and use their demand variability as a proxy. Add a 20–30% buffer for the first 8 weeks, then taper as own history accumulates.

Reorder Logic

Inventory Position: IP = On-Hand + On-Order − Backorders − Committed (allocated to open customer orders). Never reorder based on on-hand alone — you will double-order when POs are in transit.

Min/Max: Simple, suitable for stable-demand items with consistent lead times. Min = average demand during lead time + safety stock. Max = Min + EOQ. When IP drops to Min, order up to Max. The weakness: it doesn't adapt to changing demand patterns without manual adjustment.

Reorder Point / EOQ: ROP = average demand during lead time + safety stock. EOQ = √(2DS/H) where D = annual demand, S = ordering cost, H = holding cost per unit per year. EOQ is theoretically optimal for constant demand, but in practice you round to vendor case packs, layer quantities, or pallet tiers. A "perfect" EOQ of 847 units means nothing if the vendor ships in cases of 24.

Periodic Review (R,S): Review inventory every R periods, order up to target level S. Better when you consolidate orders to a vendor on fixed days (e.g., Tuesday orders for Thursday pickup). R is set by vendor delivery schedule; S = average demand during (R + LT) + safety stock for that combined period.

Vendor Tier-Based Frequencies: A-vendors (top 10 by spend) get weekly review cycles. B-vendors (next 20) get bi-weekly. C-vendors (remaining) get monthly. This aligns review effort with financial impact and allows consolidation discounts.

Promotional Planning

Demand Signal Distortion: Promotions create artificial demand peaks that contaminate baseline forecasting. Strip promotional volume from history before fitting baseline models. Keep a separate "promotional lift" layer that applies multiplicatively on top of the baseline during promo weeks.

Lift Estimation Methods: (1) Year-over-year comparison of promoted vs. non-promoted periods for the same item. (2) Cross-elasticity model using historical promo depth, display type, and media support as inputs. (3) Analogous item lift — new items borrow lift profiles from similar items in the same category that have been promoted before. Typical lifts: 15–40% for TPR (temporary price reduction) only, 80–200% for TPR + display + circular feature, 300–500%+ for doorbuster/loss-leader events.

Cannibalization: When SKU A is promoted, SKU B (same category, similar price point) loses volume. Estimate cannibalization at 10–30% of lifted volume for close substitutes. Ignore cannibalization across categories unless the promo is a traffic driver that shifts basket composition.

Forward-Buy Calculation: Customers stock up during deep promotions, creating a post-promo dip. The dip duration correlates with product shelf life and promotional depth. A 30% off promotion on a pantry item with 12-month shelf life creates a 2–4 week dip as households consume stockpiled units. A 15% off promotion on a perishable produces almost no dip.

Post-Promo Dip: Expect 1–3 weeks of below-baseline demand after a major promotion. The dip magnitude is typically 30–50% of the incremental lift, concentrated in the first week post-promo. Failing to forecast the dip leads to excess inventory and markdowns.

ABC/XYZ Classification

ABC (Value): A = top 20% of SKUs driving 80% of revenue/margin. B = next 30% driving 15%. C = bottom 50% driving 5%. Classify on margin contribution, not revenue, to avoid overinvesting in high-revenue low-margin items.

XYZ (Predictability): X = CV of demand < 0.5 (highly predictable). Y = CV 0.5–1.0 (moderately predictable). Z = CV > 1.0 (erratic/lumpy). Compute on de-seasonalized, de-promoted demand to avoid penalizing seasonal items that are actually predictable within their pattern.

Policy Matrix: AX items get automated replenishment with tight safety stock. AZ items need human review every cycle — they're high-value but erratic. CX items get automated replenishment with generous review periods. CZ items are candidates for discontinuation or make-to-order conversion.

Seasonal Transition Management

Buy Timing: Seasonal buys (e.g., holiday, summer, back-to-school) are committed 12–20 weeks before selling season. Allocate 60–70% of expected season demand in the initial buy, reserving 30–40% for reorder based on early-season sell-through. This "open-to-buy" reserve is your hedge against forecast error.

Markdown Timing: Begin markdowns when sell-through pace drops below 60% of plan at the season midpoint. Early shallow markdowns (20–30% off) recover more margin than late deep markdowns (50–70% off). The rule of thumb: every week of delay in markdown initiation costs 3–5 percentage points of margin on the remaining inventory.

Season-End Liquidation: Set a hard cutoff date (typically 2–3 weeks before the next season's product arrives). Everything remaining at cutoff goes to outlet, liquidator, or donation. Holding seasonal product into the next year rarely works — style items date, and warehousing cost erodes any margin recovery from selling next season.

Decision Frameworks

Forecast Method Selection by Demand Pattern
Demand PatternPrimary MethodFallback MethodReview Trigger
Stable, high-volume, no seasonalityWeighted moving average (4–8 weeks)Single exponential smoothingWMAPE > 25% for 4 consecutive weeks
Trending (growth or decline)Holt's double exponential smoothingLinear regression on recent 26 weeksTracking signal exceeds ±4
Seasonal, repeating patternHolt-Winters (multiplicative for growing seasonal, additive for stable)STL decomposition + SES on residualSeason-over-season pattern correlation < 0.7
Intermittent / lumpy (>30% zero-demand periods)Croston's method or SBA (Syntetos-Boylan Approximation)Bootstrap simulation on demand intervalsMean inter-demand interval shifts by >30%
Promotion-drivenCausal regression (baseline + promo lift layer)Analogous item lift + baselinePost-promo actuals deviate >40% from forecast
New product (0–12 weeks history)Analogous item profile with lifecycle curveCategory average with decay toward actualOwn-data WMAPE stabilizes below analogous-based WMAPE
Event-driven (weather, local events)Regression with external regressorsManual override with documented rationale
Safety Stock Service Level Selection
SegmentTarget Service LevelZ-ScoreRationale
AX (high-value, predictable)97.5%1.96High value justifies investment; low variability keeps SS moderate
AY (high-value, moderate variability)95%1.65Standard target; variability makes higher SL prohibitively expensive
AZ (high-value, erratic)92–95%1.41–1.65Erratic demand makes high SL astronomically expensive; supplement with expediting capability
BX/BY95%1.65Standard target
BZ90%1.28Accept some stockout risk on mid-tier erratic items
CX/CY90–92%1.28–1.41Low value doesn't justify high SS investment
CZ85%1.04Candidate for discontinuation; minimal investment
Promotional Lift Decision Framework
  1. Is there historical lift data for this SKU-promo type combination? → Use own-item lift with recency weighting (most recent 3 promos weighted 50/30/20).
  2. No own-item data but same category has been promoted? → Use analogous item lift adjusted for price point and brand tier.
  3. Brand-new category or promo type? → Use conservative category-average lift discounted 20%. Build in a wider safety stock buffer for the promo period.
  4. Cross-promoted with another category? → Model the traffic driver separately from the cross-promo beneficiary. Apply cross-elasticity coefficient if available; default 0.15 lift for cross-category halo.
  5. Always model the post-promo dip. Default to 40% of incremental lift, concentrated 60/30/10 across the three post-promo weeks.
Show full SKILL.md (1,226 more words)Show less
Markdown Timing Decision
Sell-Through at Season MidpointActionExpected Margin Recovery
≥ 80% of planHold price. Reorder cautiously if weeks of supply < 3.Full margin
60–79% of planTake 20–25% markdown. No reorder.70–80% of original margin
40–59% of planTake 30–40% markdown immediately. Cancel any open POs.50–65% of original margin
< 40% of planTake 50%+ markdown. Explore liquidation channels. Flag buying error for post-mortem.30–45% of original margin
Slow-Mover Kill Decision

Evaluate quarterly. Flag for discontinuation when ALL of the following are true:

  • Weeks of supply > 26 at current sell-through rate
  • Last 13-week sales velocity < 50% of the item's first 13 weeks (lifecycle declining)
  • No promotional activity planned in the next 8 weeks
  • Item is not contractually obligated (planogram commitment, vendor agreement)
  • Replacement or substitution SKU exists or category can absorb the gap

If flagged, initiate markdown at 30% off for 4 weeks. If still not moving, escalate to 50% off or liquidation. Set a hard exit date 8 weeks from first markdown. Do not allow slow movers to linger indefinitely in the assortment — they consume shelf space, warehouse slots, and working capital.

Key Edge Cases

Brief summaries here. Full analysis in edge-cases.md.

  1. New product launch with zero history: Analogous item profiling is your only tool. Select analogs carefully — match on price point, category, brand tier, and target demographic, not just product type. Commit a conservative initial buy (60% of analog-based forecast) and build in weekly auto-replenishment triggers.

  2. Viral social media spike: Demand jumps 500–2,000% with no warning. Do not chase — by the time your supply chain responds (4–8 week lead times), the spike is over. Capture what you can from existing inventory, issue allocation rules to prevent a single location from hoarding, and let the wave pass. Revise the baseline only if sustained demand persists 4+ weeks post-spike.

  3. Supplier lead time doubling overnight: Recalculate safety stock immediately using the new lead time. If SS doubles, you likely cannot fill the gap from current inventory. Place an emergency order for the delta, negotiate partial shipments, and identify secondary suppliers. Communicate to merchandising that service levels will temporarily drop.

  4. Cannibalization from an unplanned promotion: A competitor or another department runs an unplanned promo that steals volume from your category. Your forecast will over-project. Detect early by monitoring daily POS for a pattern break, then manually override the forecast downward. Defer incoming orders if possible.

  5. Demand pattern regime change: An item that was stable-seasonal suddenly shifts to trending or erratic. Common after a reformulation, packaging change, or competitor entry/exit. The old model will fail silently. Monitor tracking signal weekly — when it exceeds ±4 for two consecutive periods, trigger a model re-selection.

  6. Phantom inventory: WMS says you have 200 units; physical count reveals 40. Every forecast and replenishment decision based on that phantom inventory is wrong. Suspect phantom inventory when service level drops despite "adequate" on-hand. Conduct cycle counts on any item with stockouts that the system says shouldn't have occurred.

  7. Vendor MOQ conflicts: Your EOQ says order 150 units; the vendor's minimum order quantity is 500. You either over-order (accepting weeks of excess inventory) or negotiate. Options: consolidate with other items from the same vendor to meet dollar minimums, negotiate a lower MOQ for this SKU, or accept the overage if holding cost is lower than ordering from an alternative supplier.

  8. Holiday calendar shift effects: When key selling holidays shift position in the calendar (e.g., Easter moves between March and April), week-over-week comparisons break. Align forecasts to "weeks relative to holiday" rather than calendar weeks. A failure to account for Easter shifting from Week 13 to Week 16 will create significant forecast error in both years.

Communication Patterns

Tone Calibration
  • Vendor routine reorder: Transactional, brief, PO-reference-driven. "PO #XXXX for delivery week of MM/DD per our agreed schedule."
  • Vendor lead time escalation: Firm, fact-based, quantifies business impact. "Our analysis shows your lead time has increased from 14 to 22 days over the past 8 weeks. This has resulted in X stockout events. We need a corrective plan by [date]."
  • Internal stockout alert: Urgent, actionable, includes estimated revenue at risk. Lead with the customer impact, not the inventory metric. "SKU X will stock out at 12 locations by Thursday. Estimated lost sales: $XX,000. Recommended action: [expedite/reallocate/substitute]."
  • Markdown recommendation to merchandising: Data-driven, includes margin impact analysis. Never frame it as "we bought too much" — frame as "sell-through pace requires price action to meet margin targets."
  • Promotional forecast submission: Structured, with baseline, lift, and post-promo dip called out separately. Include assumptions and confidence range. "Baseline: 500 units/week. Promotional lift estimate: 180% (900 incremental). Post-promo dip: −35% for 2 weeks. Confidence: ±25%."
  • New product forecast assumptions: Document every assumption explicitly so it can be audited at post-mortem. "Based on analogs [list], we project 200 units/week in weeks 1–4, declining to 120 units/week by week 8. Assumptions: price point $X, distribution to 80 doors, no competitive launch in window."

Brief templates above. Full versions with variables in communication-templates.md.

Escalation Protocols

Automatic Escalation Triggers
TriggerActionTimeline
Projected stockout on A-item within 7 daysAlert demand planning manager + category merchantWithin 4 hours
Vendor confirms lead time increase > 25%Notify supply chain director; recalculate all open POsWithin 1 business day
Promotional forecast miss > 40% (over or under)Post-promo debrief with merchandising and vendorWithin 1 week of promo end
Excess inventory > 26 weeks of supply on any A/B itemMarkdown recommendation to merchandising VPWithin 1 week of detection
Forecast bias exceeds ±10% for 4 consecutive weeksModel review and re-parameterizationWithin 2 weeks
New product sell-through < 40% of plan after 4 weeksAssortment review with merchandisingWithin 1 week
Service level drops below 90% for any categoryRoot cause analysis and corrective planWithin 48 hours
Escalation Chain

Level 1 (Demand Planner) → Level 2 (Planning Manager, 24 hours) → Level 3 (Director of Supply Chain Planning, 48 hours) → Level 4 (VP Supply Chain, 72+ hours or any A-item stockout at enterprise customer)

Performance Indicators

Track weekly and trend monthly:

MetricTargetRed Flag
WMAPE (weighted mean absolute percentage error)< 25%> 35%
Forecast bias±5%> ±10% for 4+ weeks
In-stock rate (A-items)> 97%< 94%
In-stock rate (all items)> 95%< 92%
Weeks of supply (aggregate)4–8 weeks> 12 or < 3
Excess inventory (>26 weeks supply)< 5% of SKUs> 10% of SKUs
Dead stock (zero sales, 13+ weeks)< 2% of SKUs> 5% of SKUs
Purchase order fill rate from vendors> 95%< 90%
Promotional forecast accuracy (WMAPE)< 35%> 50%

Additional Resources

When to Use

Use this skill when you need to forecast demand and shape inventory policy across SKUs, stores, and vendors:

  • Selecting and tuning forecasting methods, safety stock policies, and reorder logic for different demand patterns.
  • Planning promotions, seasonal transitions, markdowns, and end‑of‑life strategies while balancing service, cash, and margin.
  • Investigating chronic stockouts, excess inventory, or forecast bias and redesigning the planning process with clearer decision frameworks.

Limitations

  • Use this skill only when the task clearly matches the scope described above.
  • Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
  • Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

© sickn33, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 3 other files (references) in skills/inventory-demand-planning of sickn33/agentic-awesome-skills.

  • SKILL.md
  • references/communication-templates.md
  • references/decision-frameworks.md
  • references/edge-cases.md

Open the folder on GitHubat commit 680176d

Used in 8 other repositories

We found 23 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 8 other GitHub owners. This page covers the copy in sickn33/agentic-awesome-skills, which our catalogue first saw on October 9, 2026.

Compare with similar skills

Inventory Demand Planning next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Inventory Demand Planning compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Inventory Demand Planning this skillsickn33/agentic-awesome-skills47k8 repos~6.5kAutomated safety check: PassMIT
TimesFM Forecastinggoogle-research/timesfm34k—~4.7kAutomated safety check: PassApache-2.0
StatsmodelszLanqing/codex-claude-academic-skills4.7k15 repos~4.9kAutomated safety check: PassBSD-3-Clause
Timesfm ForecastingzLanqing/codex-claude-academic-skills4.7k3 repos~7.5kAutomated safety check: NotesApache-2.0
Find Hypertable Candidatestimescale/pg-aiguide1.9k1 repos~2.6kAutomated safety check: PassApache-2.0
Pensieve Searcharkohut/pensieve1.4k—~8.2kAutomated safety check: PassApache-2.0

Similar skills

  • TimesFM Forecasting

    google-research/timesfm

    Forecasts any univariate time series zero-shot with Google's TimesFM model, returning point forecasts and calibrated prediction intervals without training.

    34k GitHub stars~4.7k tokensUpdated 10 days ago
    Data & AnalyticsAuto-check passed
  • Statsmodels

    zLanqing/codex-claude-academic-skills

    Statistical models library for Python. An agent skill from zLanqing/codex-claude-academic-skills.

    4.7k GitHub starsUsed in 15 repos~4.9k tokens
    Data & AnalyticsAuto-check passed
  • Timesfm Forecasting

    zLanqing/codex-claude-academic-skills

    Zero-shot time series forecasting with Google's TimesFM foundation model.

    4.7k GitHub starsUsed in 3 repos~7.5k tokens
    Data & AnalyticsAuto-check: notes
  • Find Hypertable Candidates

    timescale/pg-aiguide

    A skill your agent uses to analyze an existing PostgreSQL database and identify which tables should be converted to Timescale/TimescaleDB hypertables.

    1.9k GitHub starsUsed in 1 repo~2.6k tokens
    Data & AnalyticsAuto-check passed
  • Pensieve Search

    arkohut/pensieve

    Search the user's local Pensieve screenshot archive by text, app, or time range.

    1.4k GitHub stars~8.2k tokensUpdated 2 mo ago
    Data & AnalyticsAuto-check passed
  • Alphaear Predictor

    ninehills/skills

    Market prediction skill using Kronos. An agent skill from ninehills/skills.

    280 GitHub starsUsed in 1 repo~531 tokens
    Data & AnalyticsAuto-check passed

More from sickn33/agentic-awesome-skills

All 1,493 skills in this repo
  • Liuguang Banlan UI

    sickn33/agentic-awesome-skills

    Implements an interface in one of two named color modes, iridescent white or colorful black, from a parameterized starter that reports measured color intensity.

    47k GitHub starsUsed in 1 repo~2.5k tokens
    Auto-check passed
  • User Thoughts Memory

    sickn33/agentic-awesome-skills

    Saves a user's project decisions, rules and preferences into a project-local mdbase so later sessions and other agents can recover the intent.

    47k GitHub starsUsed in 1 repo~2.5k tokens
    Auto-check passed
  • Using LWC Memory and Graphs

    sickn33/agentic-awesome-skills

    Keeps project decisions, research and verified results available across coding-agent sessions through LWC memory, a document Wiki graph and a CodeGraph code index.

    47k GitHub starsUsed in 1 repo~2k tokens
    Auto-check passed
  • Find Complementary Founders

    sickn33/agentic-awesome-skills

    Guides an agent through assessing its own owner for cofounder fit, publishing an approved profile, and ranking complementary profiles other agents published for their owners.

    47k GitHub starsUsed in 1 repo~4.8k tokens
    Auto-check passed
  • Whatsapp Cloud API

    sickn33/agentic-awesome-skills

    Integracao com WhatsApp Business Cloud API (Meta). An agent skill from sickn33/agentic-awesome-skills.

    47k GitHub starsUsed in 2 repos~4.5k tokens
    Auto-check passed
  • Cline Pilot

    sickn33/agentic-awesome-skills

    Acts as a proxy for the Cline CLI, dispatching coding tasks one at a time, monitoring runs by hard evidence, relaying decisions to you and learning per-project preferences.

    47k GitHub starsUsed in 1 repo~4.6k tokens
    Auto-check passed

Questions about Inventory Demand Planning

What does Inventory Demand Planning do?

Codified expertise for demand forecasting, safety stock optimisation, replenishment planning, and promotional lift estimation at multi-location retailers. Inventory Demand Planning is an agent skill from sickn33/agentic-awesome-skills. Codified expertise for demand forecasting, safety stock optimisation, replenishment planning, and promotional lift estimation at multi-location retailers.

When should I use Inventory Demand Planning?

Inventory Demand Planning fits situations like: tasks that involve Forecasting and time series.

How do I install Inventory Demand Planning in Claude Code?

Run `npx skills add sickn33/agentic-awesome-skills --skill inventory-demand-planning -a claude-code`. Or copy the skill folder (skills/inventory-demand-planning in sickn33/agentic-awesome-skills) into .claude/skills/inventory-demand-planning in your project. Claude Code loads it when a task matches its description.

How do I install Inventory Demand Planning in Codex?

Run `npx skills add sickn33/agentic-awesome-skills --skill inventory-demand-planning -a codex`. Or copy the skill folder (skills/inventory-demand-planning in sickn33/agentic-awesome-skills) into .agents/skills/inventory-demand-planning in your project. Codex loads it when a task matches its description.

Can I use Inventory Demand Planning in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add sickn33/agentic-awesome-skills --skill inventory-demand-planning -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/inventory-demand-planning, .gemini/skills/inventory-demand-planning, .github/skills/inventory-demand-planning and .opencode/skills/inventory-demand-planning in your project.

What does Inventory Demand Planning need to run?

SKILL.md names no scripts, command-line tools or credentials: Inventory Demand Planning is instructions for the agent only.

Does Inventory Demand Planning access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Inventory Demand Planning safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Inventory Demand Planning use?

Inventory Demand Planning is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Inventory Demand Planning use?

About 6.5k tokens (SKILL.md is roughly 26k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 31k tokens, read only when the agent opens those files.

What are the alternatives to Inventory Demand Planning?

Skills that share tags, products or a category with Inventory Demand Planning: TimesFM Forecasting (google-research/timesfm, 34k stars), Statsmodels (zLanqing/codex-claude-academic-skills, 4.7k stars), Timesfm Forecasting (zLanqing/codex-claude-academic-skills, 4.7k stars) and Find Hypertable Candidates (timescale/pg-aiguide, 1.9k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Inventory Demand Planning?

sickn33 (a GitHub user) maintains it in sickn33/agentic-awesome-skills, which has 47,379 GitHub stars. The repository holds 1,493 skills in this directory. The repository was last updated on October 9, 2026.

Source: sickn33/agentic-awesome-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.