build-fpas
Skill4 starsChanged 6 days agoMITView on GitHub
Designs and builds a forecasting and policy analysis system: core model, nowcasts, judgment layer, forecast process.
In this repository210 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .cursor/rules/ai-ml-code.mdcCursor rule
- .cursor/rules/code-translation.mdcCursor rule
- .cursor/rules/data-pipelines.mdcCursor rule
- .cursor/rules/documentation.mdcCursor rule
- .cursor/rules/dsge-code.mdcCursor rule
- .cursor/rules/econometrics-code.mdcCursor rule
- .cursor/rules/eviews-code.mdcCursor rule
- .cursor/rules/forecasts.mdcCursor rule
- .cursor/rules/gempack-code.mdcCursor rule
- .cursor/rules/lego-manifests.mdcCursor rule
- .cursor/rules/llm-code.mdcCursor rule
- .cursor/rules/model-code.mdcCursor rule
- .cursor/rules/notebooks-and-scripts.mdcCursor rule
- .cursor/rules/r-code.mdcCursor rule
- .cursor/rules/restricted-data.mdcCursor rule
- .cursor/rules/rl-code.mdcCursor rule
- .cursor/rules/sectoral-trade-climate-code.mdcCursor rule
- .cursor/rules/semi-structural-code.mdcCursor rule
- .cursor/rules/stata-code.mdcCursor rule
- .cursor/rules/tests.mdcCursor rule
- .cursor/rules/validation.mdcCursor rule
- adoptSkill
- ai-auditSkill
- backtestSkill
- build-abmSkill
- build-causal-mlSkill
- build-cgeSkill
- build-climate-macroSkill
- build-deep-forecasterSkill
- build-drl-policySkill
- build-dsgeSkill
- build-financial-programmingSkill
- build-game-modelSkill
- build-hankSkill
- build-io-samSkill
- build-llm-agentsSkill
- build-llm-pipelineSkill
- build-multicountrySkill
- build-neural-solverSkill
- build-rag-kbSkill
- build-semi-structuralSkill
- build-sfcSkill
- build-trade-modelSkill
- calibrate-modelSkill
- calibration-planSkill
- carbon-pricing-analysisSkill
- chart-packSkill
- climate-scenarioSkill
- code-inventorySkill
- code-reviewSkill
- country-typologySkill
- create-exerciseSkill
- data-requirementsSkill
- debt-decompositionSkill
- debt-sustainabilitySkill
- design-trainingSkill
- distributional-analysisSkill
- equivalence-testSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 5 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 20
Do not use it when: only a model is needed (/build-semi-structural, /build-dsge) or a single forecast is needed (/forecast-round).
- Very specific: line 26
If a required input is ABSENT, that part is NOT ASSESSED — NO DATA: do not estimate or invent it.
- Very specific: line 28
Collaboration: Follow .claude/docs/collaboration-protocol.md: ask questions first, present options, get approval before writing files, and …
- Distinctive: line 54
Run a mock forecast round on historical data and review lessons
- Distinctive: line 55
Use a frozen vintage; evaluate the mock forecast against outturns
- Distinctive: line 61
After the process design: confirm calendar and roles with the institution
- Distinctive: line 62
After integration: confirm the overlay rules
- Distinctive: line 63
After the mock round: agree changes before handover
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
<!-- Generated from .claude/skills/build-fpas/SKILL.md by tools/sync_agents.py. Edit the source, then run the script. -->/build-fpas — Build FPAS
Category: Build · Primary agent: fpas-modeler
Designs and builds a forecasting and policy analysis system: core model, nowcasts, judgment layer, forecast process.
Arguments: whatever the user wrote after the command name.
Purpose
Design and build a forecasting and policy analysis system: not only a core model but the process around it, including nowcasting tools for the near term, a judgment layer with an overlay log, forecast-story templates, a calendar with roles and sign-offs, and the training that lets a counterpart team run it. The output is a system that completes a full forecast round from a frozen data vintage.
Use it when an institution needs a regular, documented forecast process tied to policy decisions, or an existing process needs a model core, a judgment layer or better documentation.
Do not use it when only a model is needed (/build-semi-structural, /build-dsge) or a single forecast is needed (/forecast-round).
Before you start
- Check required inputs. For each input below record
FOUNDorABSENT(never 'assumed'):- Core model or approved model-spec
- Data pipeline
If a required input is
ABSENT, that part isNOT ASSESSED — NO DATA: do not estimate or invent it; name what is missing and which skill produces it. If all required inputs are absent, stop and say so.
- Check confidentiality. Identify the data classification level of the inputs (
.claude/docs/confidentiality-and-ai-use.md). Do not proceed with restricted or confidential data in a way the policy does not allow. - Collaboration. Follow
.claude/docs/collaboration-protocol.md: ask questions first, present options, get approval before writing files, and updateproduction/session-state/active.mdafter each approved section.
Agents
fpas-modeler— primary agent; coordinates the work and integrates resultsdfm-nowcasting-specialist— Builds dynamic factor models and nowcastsstakeholder-liaison-specialist— Interfaces with stakeholders and counterpartsvisualization-dashboard-specialist— Designs charts and dashboards
Each agent is defined in .claude/agents/<name>.md. If your tool runs subagents, run these agents as subagents, in parallel where the steps are independent; otherwise read each agent's file and apply its instructions in turn. Subagents only write to the paths named in your instructions.
Key design decisions (present options, let the user choose)
| Decision | Typical options | What it changes |
| Core model | semi-structural gap model, small DSGE, suite | Transparency versus structure |
| Near-term tools | bridge equations, DFM nowcasts, expert judgment | Accuracy of initial conditions |
| Judgment layer | add-factors, tuned shocks, conditioning on paths | Traceability of overlays |
| Cycle | monthly, quarterly; number of meetings per round | Workload and timeliness |
| Outputs | forecast report, risk scenarios, fan charts, policy rate path | Communication |
Workflow
- Define the forecast process calendar, roles and sign-offs
- Data cut-off, nowcast, model runs, judgment meetings, sign-off, publication
- Integrate core model, near-term nowcast tools and judgment-overlay log
- Overlays recorded with reason, evidence and owner
- Build the shock-decomposition and forecast-story templates
- Templates link every story element to a decomposition or overlay
- Run a mock forecast round on historical data and review lessons
- Use a frozen vintage; evaluate the mock forecast against outturns
- Prepare training material for the counterpart team
- Hands-on exercises on the core model and the process (
/design-training)
- Hands-on exercises on the core model and the process (
- Register the model as a lego set (
/lego-map): a baseplate plus bricks with declared studs (variables, units, timing) and stubs, so components can later be attached, detached or swapped
Checkpoints with the user
- After the process design: confirm calendar and roles with the institution
- After integration: confirm the overlay rules
- After the mock round: agree changes before handover
Common pitfalls
- A model without a process, or a process without documentation
- Overlays that are not recorded
- Near-term tools inconsistent with the core model's initial conditions
- Training that ends at the workshop with no follow-up
Output
models/fpas/<name>/ and docs/models/<name>/fpas-design.md (+ model.lego.json)
The model folder holds the core model, nowcast tools, templates and run scripts; the design document covers the calendar, roles, overlay rules and the mock-round review; the lego manifest registers the model and its satellites. Every run saves its results to output/<run-id>/ in the model folder, with a run log (.claude/rules/model-code.md).
Gate / verdict
- A full mock round runs end-to-end from a frozen data vintage
- Lego manifest passes
python tools/lego.py check - The overlay log is in place and used in the mock round
- Training material exists for the counterpart team
Suggested next steps
/forecast-round/design-training/lego-map
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

