agentleFS
tatashbartatashbar/Economic-Modeling-Studio/.agents/skills/build-game-model/SKILL.md

build-game-model

Skill4 starsChanged 6 days agoMITView on GitHub

Builds a game-theoretic or mechanism-design model: specification, equilibria, computation and policy interpretation.

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
  1. Very specific:

    If a required input is ABSENT, that part is NOT ASSESSED — NO DATA: do not estimate or invent it.

    line 25
  2. Very specific:

    Collaboration: Follow .claude/docs/collaboration-protocol.md: ask questions first, present options, get approval before writing files, and …

    line 27
  3. Distinctive:

    Verify equilibrium conditions numerically

    line 50
  4. Distinctive:

    Run comparative statics and welfare analysis

    line 51
  5. Distinctive:

    After formalization: confirm players, timing and payoffs

    line 59
  6. Distinctive:

    After solution: confirm the selection argument if equilibria are multiple

    line 60
  7. Distinctive:

    Before policy implications: confirm which assumptions are realistic for the case

    line 61
  8. Distinctive:

    All equilibria found are reported

    line 75

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md
<!-- 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

  1. Check required inputs. For each input below record FOUND or ABSENT (never 'assumed'):
    • Approved model-spec with players, actions, information, payoffs If a required input is ABSENT, that part is NOT 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.
  2. 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.
  3. Collaboration. Follow .claude/docs/collaboration-protocol.md: ask questions first, present options, get approval before writing files, and update production/session-state/active.md after each approved section.

Agents

  • game-theory-specialist — primary agent; coordinates the work and integrates results
  • mechanism-design-specialist — Designs mechanisms and incentives
  • policy-interaction-games-specialist — Models policy interaction
  • sovereign-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)

DecisionTypical optionsWhat it changes
Game formnormal-form, extensive-form, repeated, dynamic stochasticEquilibrium concepts available
Informationcomplete, incomplete (Bayesian), global gamesMultiplicity and selection
Commitmentcommitment, discretion, reputationTime-consistency and welfare
Solutionanalytical, numerical enumeration, homotopy, value iterationCompleteness of the equilibrium set
Calibrationstylized, calibrated to dataQuantitative interpretation

Workflow

  1. Formalize players, strategies, information and payoffs from economic primitives
    • Payoffs derived from objectives (mandates, profits, utility), not chosen to reach a result
  2. Solve for equilibria (analytical and numerical); list all equilibria and the selection argument
    • Verify equilibrium conditions numerically
  3. Run comparative statics and welfare analysis
    • Vary timing, information and commitment assumptions
  4. Calibrate where feasible and test against stylized facts
  5. Translate into policy implications and caveats
    • State which conclusions survive alternative assumptions
  6. 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

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.