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

build-hank

Skill4 starsChanged 6 days agoMITView on GitHub

Builds a heterogeneous-agent (HANK) model with household block, sequence-space solution and distributional outputs.

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

    Test against analytical cases and a representative-agent limit

    line 49
  4. Distinctive:

    Check grid convergence and distribution accuracy

    line 51
  5. Distinctive:

    After the household block: confirm asset structure and income process

    line 61
  6. Distinctive:

    After calibration: confirm micro targets and the fit

    line 62
  7. Distinctive:

    After IRFs: confirm the distributional outputs needed

    line 63

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

/build-hank — Build HANK

Category: Build · Primary agent: hank-specialist

Builds a heterogeneous-agent (HANK) model with household block, sequence-space solution and distributional outputs.

Arguments: whatever the user wrote after the command name.

Purpose

Build a heterogeneous-agent New Keynesian model: a household block with idiosyncratic income risk and borrowing constraints, solved for its stationary distribution and sequence-space Jacobians, embedded in general equilibrium with firms and policy. The output is a model that delivers both aggregate and distributional impulse responses, matches key micro moments, and passes market-clearing and aggregation checks.

Use it when the distribution of income, wealth or marginal propensities to consume matters for the question: monetary and fiscal transmission through heterogeneity, distributional effects of policy, precautionary saving, inequality dynamics.

Do not use it when a representative-agent model answers the question (/build-dsge) or when static distributional incidence is enough (/distributional-analysis).

Before you start

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

  • hank-specialist — primary agent; coordinates the work and integrates results
  • neural-solver-specialist — Solves high-dimensional economic models with neural networks
  • inequality-distribution-specialist — Analyzes inequality and distribution
  • numerical-methods-specialist — Specializes in numerical methods

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
Asset structureone asset, two assets (liquid and illiquid)MPCs and wealth distribution
Income processAR(1), richer processes from micro dataRisk and precautionary saving
Nominal rigiditiessticky prices, sticky wagesTransmission and income incidence
Solution methodsequence-space Jacobians, Reiter methodSpeed and nonlinearity
Calibration targetsMPCs, wealth shares, liquid wealth, aggregate ratiosDistributional realism

Workflow

  1. Implement the household block (endogenous grid method) and test it against known cases
    • Test against analytical cases and a representative-agent limit
  2. Compute steady-state distribution and sequence-space Jacobians
    • Check grid convergence and distribution accuracy
  3. Assemble general equilibrium; verify market clearing
    • Asset, goods and labor markets clear in steady state and along transitions
  4. Calibrate to micro and aggregate moments
    • Targets from household surveys and national accounts; document gaps
  5. Produce aggregate and distributional IRFs
    • Decompose consumption responses into direct and indirect effects
  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 household block: confirm asset structure and income process
  • After calibration: confirm micro targets and the fit
  • After IRFs: confirm the distributional outputs needed

Common pitfalls

  • Coarse grids that distort the wealth distribution
  • Calibrating MPCs without micro evidence
  • Ignoring aggregation errors
  • Over-interpreting the distribution from a one-asset model

Output

models/dsge/<name>-hank/ (+ model.lego.json)

The folder holds the household block and tests, steady-state and Jacobian code, the GE assembly, calibration files, the aggregate and distributional IRF pack 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

  • Market clearing and aggregation checks pass
  • Micro targets are matched or gaps documented
  • Lego manifest passes python tools/lego.py check
  • Grid-convergence and accuracy checks are reported
  • Distributional IRFs are reported alongside aggregates

Suggested next steps

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