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

build-multicountry

Skill4 starsChanged 6 days agoMITView on GitHub

Builds or extends a large multi-country model with trade and financial linkages and global scenarios.

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 4 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

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

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

    line 28
  3. Distinctive:

    Run standard global scenarios and compare to a reduced-form benchmark

    line 53
  4. Distinctive:

    After defining blocks: confirm regions and linkages

    line 59
  5. Distinctive:

    After calibration: confirm steady-state aggregates

    line 60
  6. Distinctive:

    After benchmark comparison: agree on how differences will be explained

    line 61

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

/build-multicountry — Build Multicountry

Category: Build · Primary agent: multi-country-dsge-specialist

Builds or extends a large multi-country model with trade and financial linkages and global scenarios.

Arguments: whatever the user wrote after the command name.

Purpose

Build or extend a large multi-country model with trade and financial linkages for global scenarios and spillover analysis. The output is a model in which global accounting closes (world trade balances, net foreign assets sum to zero), each region is calibrated, results are benchmarked against a reduced-form alternative, and runtime is good enough for regular use.

Use it when spillovers, global scenarios or coordinated policies across several economies are the question, and bilateral trade and financial links matter.

Do not use it when a single small open economy with a foreign block suffices (/build-dsge), or the question is empirical spillover estimation (/spillover-analysis).

Before you start

  1. Check required inputs. For each input below record FOUND or ABSENT (never 'assumed'):
    • Approved model-spec
    • Bilateral trade and financial data 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

  • multi-country-dsge-specialist — primary agent; coordinates the work and integrates results
  • global-spillover-specialist — Analyzes global spillovers
  • trade-gvc-specialist — Models trade and global value chains
  • 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
Regionsnumber of countries and rest-of-world blocksDetail versus runtime
Model type per blockDSGE, semi-structural, mixedConsistency and speed
Linkagestrade, commodities, financial (portfolio, banking), confidenceSpillover channels
Bilateral weightstrade, financial, time-varying or fixedTransmission strength
Solutionstacked linear, block recursive, nonlinearSpeed and accuracy

Workflow

  1. Define the regional blocks and bilateral matrices; verify consistency
    • World exports equal world imports; bilateral asset positions sum consistently
  2. Implement the model with a block structure for speed
  3. Calibrate each region and cross-check steady-state aggregates
    • Steady-state trade and NFA positions match data
  4. Run standard global scenarios and compare to a reduced-form benchmark
    • Compare spillovers with GVAR or panel estimates (/spillover-analysis)
  5. Profile runtime and parallelize where useful
  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 defining blocks: confirm regions and linkages
  • After calibration: confirm steady-state aggregates
  • After benchmark comparison: agree on how differences will be explained

Common pitfalls

  • Global accounts that do not close
  • Bilateral weights from one year applied to all periods without checking
  • Regions calibrated inconsistently with each other
  • Spillovers driven by a single channel left unexamined

Output

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

The folder holds regional blocks, bilateral matrices, calibration files, global scenario scripts, the benchmark comparison, runtime profile 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

  • Global accounting closes
  • Benchmark comparison documented
  • Lego manifest passes python tools/lego.py check
  • Each region's calibration targets are documented
  • Runtime is profiled and reported

Suggested next steps

  • /spillover-analysis
  • /validate-model
  • /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.