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

build-abm

Skill4 starsChanged 6 days agoMITView on GitHub

Builds an agent-based model with ODD documentation, calibration, validation and experiment design.

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 5 are distinctive, and 2 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.

  • 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:

    Document the model with the ODD protocol before coding

    line 47
  4. Distinctive:

    Use common random numbers across policy variants

    line 58
  5. Distinctive:

    After the ODD document: confirm agents, rules and protocols before coding

    line 64
  6. Distinctive:

    After calibration: confirm targets and fit are adequate for the question

    line 65
  7. Distinctive:

    Before policy experiments: confirm the experiment design and replications

    line 66

≈ “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-abm/SKILL.md by tools/sync_agents.py. Edit the source, then run the script. -->

/build-abm — Build ABM

Category: Build · Primary agent: agent-based-modeling-specialist

Builds an agent-based model with ODD documentation, calibration, validation and experiment design.

Arguments: whatever the user wrote after the command name.

Purpose

Build an agent-based model whose aggregate behavior emerges from heterogeneous, boundedly rational agents interacting in markets and networks, documented well enough that someone else can rebuild it and calibrated tightly enough that its results are more than illustrations. The output is a reviewed, reproducible simulation model with a validation record, not a single striking simulation run.

Use it when heterogeneity, interaction, networks, disequilibrium or learning drive the question: financial contagion, housing booms, firm dynamics, distributional dynamics, or policy experiments where behavioral responses differ from rational-expectations benchmarks.

Do not use it when a representative-agent or heterogeneous-agent equilibrium model answers the question (/build-dsge, /build-hank), or when accounting consistency of sectoral balances is the main concern without agent heterogeneity (/build-sfc).

Before you start

  1. Check required inputs. For each input below record FOUND or ABSENT (never 'assumed'):
    • Approved model-spec with agent rules 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

  • agent-based-modeling-specialist — primary agent; coordinates the work and integrates results
  • simulation-based-inference-specialist — Estimates complex models with neural simulation-based inference
  • hpc-gpu-engineer — Engineers high-performance computing

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
Agent typeshouseholds, firms, banks, government, foreign sector; number of eachMechanisms available; runtime
Behavioral rulesfixed heuristics, adaptive learning, reinforcement learning, LLM-informed rulesRealism versus discipline; calibration burden
Market protocolsdecentralized matching, search, posted prices, order booksPrice formation and frictions
Accountingfull stock–flow consistency or partialCredibility of aggregate dynamics
Calibration methodmoment matching, indirect inference, simulation-based inferenceIdentification and uncertainty
Scalehundreds to millions of agentsStatistical stability versus compute

Workflow

  1. Document the model with the ODD protocol before coding
    • Overview (purpose, entities, state variables, scales, process scheduling), Design concepts (emergence, adaptation, learning, interaction, stochasticity, observation) and Details (initialization, input data, submodels)
    • State each behavioral rule with its evidence or rationale
  2. Implement with explicit random-seed management and unit tests for agent rules
    • One generator per stochastic process; seeds recorded in every output
    • Unit tests for each rule and for stock–flow consistency at the aggregate
  3. Calibrate by indirect inference or SBI; check stylized facts
    • Targets: business-cycle moments, firm-size and income distributions, fat tails, volatility clustering, as relevant to the question
    • Report fit to targeted and untargeted moments
  4. Design experiments and run with enough replications for stable estimates
    • Determine replications from the convergence of Monte Carlo averages; report confidence bands
    • Use common random numbers across policy variants
  5. Report sensitivity to parameters and seeds
    • Global sensitivity analysis on behavioral parameters; key-driver ranking
  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 the ODD document: confirm agents, rules and protocols before coding
  • After calibration: confirm targets and fit are adequate for the question
  • Before policy experiments: confirm the experiment design and replications

Common pitfalls

  • Behavioral parameters tuned freely until the model delivers the expected result
  • Results from a handful of runs
  • Accounting leaks that create or destroy money or assets
  • Undocumented code that reviewers cannot follow

Output

models/abm/<name>/ (+ model.lego.json)

The folder holds the ODD document, code, unit tests, calibration scripts and results, experiment scripts with seeds, the sensitivity 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

  • ODD complete
  • Stylized-facts validation and seed-robustness reported
  • Lego manifest passes python tools/lego.py check
  • Aggregate stock–flow consistency is verified by tests
  • Confidence bands come from enough replications to be stable

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.