build-financial-programming
Skill4 starsChanged 6 days agoMITView on GitHub
Builds an integrated financial-programming framework consistent across real, fiscal, monetary and external sectors.
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-fpasSkill
- 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, 6 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 25
If a required input is ABSENT, that part is NOT ASSESSED — NO DATA: do not estimate or invent it.
- Very specific: line 27
Collaboration: Follow .claude/docs/collaboration-protocol.md: ask questions first, present options, get approval before writing files, and …
- Distinctive: line 54
Run consistency checks across fiscal, monetary, BoP and national accounts
- Distinctive: line 56
Document assumptions for program-design use
- Distinctive: line 61
After the accounts layout: confirm coverage and the closure variable
- Distinctive: line 62
After behavioral assumptions: confirm sources and ranges
- Distinctive: line 63
After the baseline: confirm the macro story before alternatives
- Distinctive: line 77
All sectoral identities close
≈ “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-financial-programming/SKILL.md by tools/sync_agents.py. Edit the source, then run the script. -->/build-financial-programming — Build Financial Programming
Category: Build · Primary agent: financial-programming-specialist
Builds an integrated financial-programming framework consistent across real, fiscal, monetary and external sectors.
Arguments: whatever the user wrote after the command name.
Purpose
Build an integrated financial-programming framework: a consistent set of real, fiscal, monetary and external accounts linked by identities and a small number of behavioral relationships, used to design and check macroeconomic programs and to compute financing gaps. The output is a framework in which every identity closes in code and every behavioral assumption is sourced.
Use it when a program, budget or medium-term framework needs cross-sector consistency, financing gaps must be identified, or a counterpart needs a transparent accounting framework to own.
Do not use it when behavioral dynamics and expectations dominate the question (/build-semi-structural, /build-dsge) or when the question is only about debt dynamics (/debt-sustainability).
Before you start
- Check required inputs. For each input below record
FOUNDorABSENT(never 'assumed'):- Data sheet with sectoral accounts
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.
- Data sheet with sectoral accounts
If a required input is
- 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
financial-programming-specialist— primary agent; coordinates the work and integrates resultsbalance-of-payments-specialist— Builds balance-of-payments and international investment position analysesdebt-sustainability-analyst— Builds debt sustainability analysesrmsm-three-gap-modeler— Builds revised minimum standard, three-gap and growth-financing models for low-income and developing economies
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 |
| Frequency | annual, quarterly | Data needs; program monitoring |
| Sector coverage | central government or general government; depository corporations or broader | Consistency and data availability |
| Closure | which variable absorbs the gap (financing, reserves, spending) | Policy interpretation |
| Behavioral equations | trade elasticities, money demand, revenue elasticities, import propensities | Scenario responses |
| Exchange-rate regime | fixed, managed, flexible | Monetary–external links |
Workflow
- Lay out sectoral accounts and identities; implement in code with assertions
- National accounts, fiscal, monetary survey and BoP; saving–investment and sectoral balance links
- Assertions fail loudly on any residual
- Specify behavioral relationships and their sources
- Each elasticity or ratio with estimate, sample and source; ranges where uncertain
- Build baseline and alternative scenarios with financing gaps
- Gaps shown explicitly, not absorbed into residuals
- Run consistency checks across fiscal, monetary, BoP and national accounts
- Reconcile data discrepancies and document them (
/data-requirements)
- Reconcile data discrepancies and document them (
- Document assumptions for program-design use
- Make the framework simple enough for counterparts to operate
- 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 accounts layout: confirm coverage and the closure variable
- After behavioral assumptions: confirm sources and ranges
- After the baseline: confirm the macro story before alternatives
Common pitfalls
- Gaps hidden in errors and omissions or statistical discrepancies
- Mixing cash and accrual fiscal data
- Behavioral parameters from different periods or countries without justification
- Frameworks too complex for counterparts to maintain
Output
models/financial-programming/<country>/ (+ model.lego.json)
The folder holds the accounts code with identity assertions, the behavioral-parameter table, baseline and scenario files, the consistency report and the lego manifest. Every run saves its results to output/<run-id>/ in the model folder, with a run log (.claude/rules/model-code.md).
Gate / verdict
- All sectoral identities close
- Behavioral parameters are sourced
- Lego manifest passes
python tools/lego.py check - Financing gaps are shown explicitly
- Cross-sector consistency checks are recorded
Suggested next steps
/debt-sustainability/validate-model/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.

