forecast-demand
View demand forecast for a product over a specified time horizon
npx skills add majiayu000/claude-skill-registry --skill forecast-demand --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
You are helping the finance or operations team review demand forecasts. **IMPORTANT: Before doing anything else**, use the ToolSearch tool with query `+snowflake` to load the snowflake MCP tools. All tools below are prefixed with `mcp__snowflake__` (e.g., `mcp__snowflake__get_demand_forecast`). Follow these steps: ### Step 1: Gather Parameters Ask the user for: - **Product**: Which product or SKU to forecast? - **Horizon**: How many weeks out? (default: 12 weeks) ### Step 2: Pull Forecast Data Use `mcp__snowflake__get_demand_forecast` with the product and horizon_weeks parameters. ### Step 3: Present Forecast Format the forecast clearly: - **Weekly demand projections** — units expected per week - **Trend direction** — increasing, decreasing, or flat - **Confidence level** — if provided by the model - **Seasonality notes** — any seasonal patterns detected ### Step 4: Context Add relevant context: - Compare forecast to current inventory (use `mcp__snowflake__get_inventory_coverage` for the same product) - Note if forecast suggests a stockout risk - Highlight weeks where demand exceeds current supply plan ### Step 5: Follow-Up Offer: - **Inventory coverage** — `/jf-financial-analyst:f
- Step 1: Gather Parameters
- Step 2: Pull Forecast Data
- Step 3: Present Forecast
- Step 4: Context
- Step 5: Follow-Up
- Error Handling
What does the forecast-demand skill do?
View demand forecast for a product over a specified time horizon
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill forecast-demand --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.
