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

build-trade-model

Skill4 starsChanged 6 days agoMITView on GitHub

Builds a trade model: gravity and structural gravity estimation, quantitative trade general equilibrium, and global value chain accounting.

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

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

    line 29
  3. Distinctive:

    Use observed trade shares.

    line 53
  4. Distinctive:

    Check the model reproduces baseline trade flows and the trade balance treatment is explicit

    line 54
  5. Distinctive:

    After choosing the model type: confirm sectors and partners

    line 60
  6. Distinctive:

    After estimation: confirm elasticities and ranges

    line 61
  7. Distinctive:

    Before reporting: confirm the trade-balance treatment

    line 62

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

/build-trade-model — Build Trade Model

Category: Build · Primary agent: trade-policy-simulation-specialist

Builds a trade model: gravity and structural gravity estimation, quantitative trade general equilibrium, and global value chain accounting.

Arguments: whatever the user wrote after the command name.

Purpose

Build a trade model fit for the question: reduced-form or structural gravity estimation of trade costs and policy effects, a quantitative general-equilibrium trade model solved in changes, or value-chain accounting. The output reproduces baseline trade flows, makes the trade-balance treatment explicit, and reports welfare and sectoral effects across the plausible range of trade elasticities.

Use it when the question involves tariffs, trade agreements, trade costs, retaliation, value chains or trade exposure across partners and sectors.

Do not use it when domestic tax and factor-market detail dominates (/build-cge) or the question is a supply disruption through production networks (/supply-chain-shock).

Before you start

  1. Check required inputs. For each input below record FOUND or ABSENT (never 'assumed'):
    • Bilateral trade data
    • Tariff and trade-cost data
    • Global input-output tables (optional) 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

  • trade-policy-simulation-specialist — primary agent; coordinates the work and integrates results
  • trade-gvc-specialist — Models trade and global value chains
  • production-networks-specialist — Models production networks and supply chains
  • cge-modeling-specialist — Builds computable general equilibrium models

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
Model typereduced-form gravity, structural gravity, quantitative GE (Armington, Eaton–Kortum), CGECounterfactual capability
Sectorssingle, multi-sector, with input-output linksAmplification through intermediates
Trade balancebalanced trade, fixed deficitsCounterfactual results
Elasticitiesestimated, sourced from literature, rangesWelfare magnitudes
Dataproduct-level trade, global IO tablesCoverage and detail

Workflow

  1. Define the question and choose between reduced-form gravity, structural gravity, quantitative GE trade or CGE
  2. Estimate trade elasticities and trade costs with PPML and high-dimensional fixed effects
    • Exporter–year, importer–year and pair fixed effects; treatment of zeros
  3. Calibrate the GE model and solve counterfactuals in changes
    • Use observed trade shares; state the solution algorithm and convergence
  4. Check the model reproduces baseline trade flows and the trade balance treatment is explicit
  5. Report welfare and sectoral effects with elasticity sensitivity
    • Decompose welfare; compare results with and without input-output links
  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 choosing the model type: confirm sectors and partners
  • After estimation: confirm elasticities and ranges
  • Before reporting: confirm the trade-balance treatment

Common pitfalls

  • OLS gravity on logs with zeros dropped
  • Single-sector models for policies hitting intermediates
  • Trade-flow changes reported as welfare
  • Elasticities from different aggregation levels

Output

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

The folder holds data, estimation scripts and results, the GE model and counterfactual scripts, the elasticity table with sources, results with welfare decomposition 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

  • Baseline trade flows reproduced
  • Elasticity sources and ranges documented
  • Trade balance closure stated
  • Lego manifest passes python tools/lego.py check
  • Gravity estimates use PPML with appropriate fixed effects
  • Welfare is decomposed into its sources

Suggested next steps

  • /trade-policy-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.