forecast
Predict likely next developments from internal development patterns (git history, archobs clusters) and external signals (intel feeds). Use when you need forward-looking intelligence — what's GOING to happen, not what already happened. NOT for gathering raw signals (use intel); NOT for architecture analysis (use archobs); NOT for implementation planning (use plan).
npx skills add majiayu000/claude-skill-registry --skill forecast --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.
# Forecast (Predictive Intelligence) ## Overview Predict likely next developments using two engines: - **Internal engine** (trajectory): analyzes git history and archobs cluster context to predict what the team is likely to build next — where momentum is concentrated, what kinds of changes are happening, and what areas are growing. - **External engine**: uses Bayesian scenario projection, exponential decay weighting, entropy-based surprise scoring, CUSUM change-point detection, and HMM lifecycle classification from collected intelligence feeds to predict external shifts. While `intel` tells you what happened, `forecast` tells you what's likely to happen next — internally from development patterns and externally from ecosystem signals. Success looks like: forward-looking intelligence with ranked scenarios, development momentum analysis, and actionable recommendations that a team can act on before events materialize. ## Chooser (When to Use) | Situation | Mode | |---|---| | "What are we likely to build next?" | **Internal** | | "Where is development concentrated?" | **Internal** | | "What external shifts should we prepare for?" | **External** | | "What's going to happen next?" (gener
- Overview
- Chooser (When to Use)
- Prerequisites
- Internal engine
- External engine
- Workflow
- Combined Mode
- Guardrails
- Output Template
- Internal mode (trajectory)
- External mode (forecast)
- Combined mode
- References
cd tools/intelligence && npm install && npm run build npm link # from tools/intelligence/ mkdir -p ~/.config/intel ~/.local/share/intel cp config/feeds.example.yaml ~/.config/intel/config.yaml intel collect --once sqlite3 ~/.local/share/intel/intel.db < tools/intelligence/migrations/003-published-at-analysis.sql
What does the forecast skill do?
Predict likely next developments from internal development patterns (git history, archobs clusters) and external signals (intel feeds). Use when you need forward-looking intelligence — what's GOING to happen, not what already happened. NOT for gathering raw signals (use intel); NOT for architecture analysis (use archobs); NOT for implementation planning (use plan).
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill forecast --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.