build-game-model
Skill4 starsChanged 6 days agoMITView on GitHub
Builds a game-theoretic or mechanism-design model: specification, equilibria, computation and policy interpretation.
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-fpasSkill
- 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 50
Verify equilibrium conditions numerically
- Distinctive: line 51
Run comparative statics and welfare analysis
- Distinctive: line 59
After formalization: confirm players, timing and payoffs
- Distinctive: line 60
After solution: confirm the selection argument if equilibria are multiple
- Distinctive: line 61
Before policy implications: confirm which assumptions are realistic for the case
- Distinctive: line 75
All equilibria found are reported
≈ “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-game-model/SKILL.md by tools/sync_agents.py. Edit the source, then run the script. -->/build-game-model — Build Game Model
Category: Build · Primary agent: game-theory-specialist
Builds a game-theoretic or mechanism-design model: specification, equilibria, computation and policy interpretation.
Arguments: whatever the user wrote after the command name.
Purpose
Build a game-theoretic or mechanism-design model in which outcomes depend on strategic interaction: policymakers, creditors, firms or countries choosing actions that depend on what others do. The output is a specified game, all of its equilibria within the search, an explicit selection argument where several exist, and policy implications whose dependence on timing, information and commitment is shown.
Use it when strategy is central: policy coordination, credibility and commitment, bargaining and restructuring, auctions and incentive design, crisis coordination.
Do not use it when agents take prices as given and strategic interaction is negligible (/build-dsge, /build-cge), or learning dynamics among many agents are the focus (/build-abm, /build-drl-policy).
Before you start
- Check required inputs. For each input below record
FOUNDorABSENT(never 'assumed'):- Approved model-spec with players, actions, information, payoffs
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.
- Approved model-spec with players, actions, information, payoffs
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
game-theory-specialist— primary agent; coordinates the work and integrates resultsmechanism-design-specialist— Designs mechanisms and incentivespolicy-interaction-games-specialist— Models policy interactionsovereign-crisis-games-specialist— Models sovereign debt, default and currency crises
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 |
| Game form | normal-form, extensive-form, repeated, dynamic stochastic | Equilibrium concepts available |
| Information | complete, incomplete (Bayesian), global games | Multiplicity and selection |
| Commitment | commitment, discretion, reputation | Time-consistency and welfare |
| Solution | analytical, numerical enumeration, homotopy, value iteration | Completeness of the equilibrium set |
| Calibration | stylized, calibrated to data | Quantitative interpretation |
Workflow
- Formalize players, strategies, information and payoffs from economic primitives
- Payoffs derived from objectives (mandates, profits, utility), not chosen to reach a result
- Solve for equilibria (analytical and numerical); list all equilibria and the selection argument
- Verify equilibrium conditions numerically
- Run comparative statics and welfare analysis
- Vary timing, information and commitment assumptions
- Calibrate where feasible and test against stylized facts
- Translate into policy implications and caveats
- State which conclusions survive alternative assumptions
- 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 formalization: confirm players, timing and payoffs
- After solution: confirm the selection argument if equilibria are multiple
- Before policy implications: confirm which assumptions are realistic for the case
Common pitfalls
- Reporting one equilibrium when several exist
- Assuming commitment the player cannot deliver
- Payoffs reverse-engineered from the desired outcome
- Off-equilibrium beliefs left unspecified in dynamic games
Output
models/games/<name>/ (+ model.lego.json)
The folder holds the game specification, solution code, equilibrium list with verification, comparative statics, calibration files where used 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 equilibria found are reported
- Payoffs trace to primitives
- Lego manifest passes
python tools/lego.py check - Equilibrium conditions are verified numerically
- Sensitivity to timing, information and commitment is reported
Suggested next steps
/validate-model/policy-simulation/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.

