inventory-demand-planningCodified expertise for demand forecasting, safety stock optimisation, replenishment planning, and promotional lift estimation at multi-location retailers. In...
Install via ClawdBot CLI:
clawdbot install nocodemf/inventory-demand-planningGrade Fair — based on market validation, documentation quality, package completeness, maintenance status, and authenticity signals.
Calls external URL not in known-safe list
https://github.com/evos-ai/evos-capabilitiesAudited Apr 17, 2026 · audit v1.0
Generated Mar 20, 2026
A multi-location retailer needs to forecast demand for seasonal products like winter apparel or holiday decorations, using triple exponential smoothing (Holt-Winters) to account for 52-week cycles and manage inventory transitions. This prevents overstock after the season ends and stockouts during peak periods, aligning with promotional calendars.
A grocery chain faces intermittent demand for specialty items, requiring safety stock calculations that incorporate lead time variability and non-normal distributions to avoid stockouts. Using adjusted formulas with service level targets (e.g., 95% for A-items) helps balance inventory costs and availability across distribution centers.
A general merchandise retailer plans a promotional campaign, needing to estimate demand lift using causal regression models with features like price elasticity and promotional flags. This ensures accurate replenishment orders and minimizes excess inventory post-promotion, supporting GMROI targets set by finance.
A retailer with 300-800 SKUs performs ABC/XYZ analysis to categorize items by value and demand variability, applying different forecasting methods (e.g., moving averages for stable items, ML for promotional ones). This optimizes replenishment planning and resource allocation across store locations.
Operates 40-200 stores and regional distribution centers, managing inventory across grocery, general merchandise, and seasonal assortments. Revenue is driven by in-store sales, with a focus on minimizing stockouts and excess inventory to meet GMROI targets through demand planning and vendor negotiations.
Integrates online and offline sales channels, requiring demand forecasting that accounts for both POS data and digital trends. Revenue streams include e-commerce sales and in-store purchases, with inventory optimization across warehouses to support seamless customer experiences and promotional campaigns.
Supplies products to multiple retail clients, focusing on bulk replenishment planning and safety stock management to meet service level agreements. Revenue is generated through wholesale transactions, with an emphasis on lead time variability and vendor negotiation frameworks to maintain profitability.
💬 Integration Tip
Integrate with demand planning suites like Blue Yonder or Oracle Demantra and ERP systems such as SAP for seamless data flow, ensuring POS and WMS feeds are aligned to support accurate forecasting and inventory optimization.
Scored Apr 22, 2026
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
Transform AI agents from task-followers into proactive partners with memory architecture, reverse prompting, and self-healing patterns. Lightweight version f...
Persistent memory for AI agents to store facts, learn from actions, recall information, and track entities across sessions.
Search and discover OpenClaw skills from various sources. Use when: user wants to find available skills, search for specific functionality, or discover new s...
Prefer `skillhub` for skill discovery/install/update, then fallback to `clawhub` when unavailable or no match. Use when users ask about skills, 插件, or capabi...
Orchestrate multi-agent teams with defined roles, task lifecycles, handoff protocols, and review workflows. Use when: (1) Setting up a team of 2+ agents with different specializations, (2) Defining task routing and lifecycle (inbox → spec → build → review → done), (3) Creating handoff protocols between agents, (4) Establishing review and quality gates, (5) Managing async communication and artifact sharing between agents.