build-llm-agents
Skill4 starsChanged 6 days agoMITView on GitHub
Builds LLM-agent economic simulations (synthetic households, firms, forecasters, negotiators) with sensitivity and human-data checks.
In this repository210 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .cursor/rules/ai-ml-code.mdcCursor rule
- .cursor/rules/code-translation.mdcCursor rule
- .cursor/rules/data-pipelines.mdcCursor rule
- .cursor/rules/documentation.mdcCursor rule
- .cursor/rules/dsge-code.mdcCursor rule
- .cursor/rules/econometrics-code.mdcCursor rule
- .cursor/rules/eviews-code.mdcCursor rule
- .cursor/rules/forecasts.mdcCursor rule
- .cursor/rules/gempack-code.mdcCursor rule
- .cursor/rules/lego-manifests.mdcCursor rule
- .cursor/rules/llm-code.mdcCursor rule
- .cursor/rules/model-code.mdcCursor rule
- .cursor/rules/notebooks-and-scripts.mdcCursor rule
- .cursor/rules/r-code.mdcCursor rule
- .cursor/rules/restricted-data.mdcCursor rule
- .cursor/rules/rl-code.mdcCursor rule
- .cursor/rules/sectoral-trade-climate-code.mdcCursor rule
- .cursor/rules/semi-structural-code.mdcCursor rule
- .cursor/rules/stata-code.mdcCursor rule
- .cursor/rules/tests.mdcCursor rule
- .cursor/rules/validation.mdcCursor rule
- adoptSkill
- ai-auditSkill
- backtestSkill
- build-abmSkill
- build-causal-mlSkill
- build-cgeSkill
- build-climate-macroSkill
- build-deep-forecasterSkill
- build-drl-policySkill
- build-dsgeSkill
- build-financial-programmingSkill
- build-fpasSkill
- build-game-modelSkill
- build-hankSkill
- build-io-samSkill
- build-llm-pipelineSkill
- build-multicountrySkill
- build-neural-solverSkill
- build-rag-kbSkill
- build-semi-structuralSkill
- build-sfcSkill
- build-trade-modelSkill
- calibrate-modelSkill
- calibration-planSkill
- carbon-pricing-analysisSkill
- chart-packSkill
- climate-scenarioSkill
- code-inventorySkill
- code-reviewSkill
- country-typologySkill
- create-exerciseSkill
- data-requirementsSkill
- debt-decompositionSkill
- debt-sustainabilitySkill
- design-trainingSkill
- distributional-analysisSkill
- equivalence-testSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 7 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈7
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
- Very specific: line 26
If a required input is ABSENT, that part is NOT ASSESSED — NO DATA: do not estimate or invent it.
- Very specific: line 28
Collaboration: Follow .claude/docs/collaboration-protocol.md: ask questions first, present options, get approval before writing files, and …
- Distinctive: line 48
Use structured outputs; record prompts and versions
- Distinctive: line 49
Run pilot simulations across prompts, seeds and at least two LLMs
- Distinctive: line 52
Check for contamination from well-known published experiments
- Distinctive: line 54
Document reproducibility details (model versions, temperature, seeds)
- Distinctive: line 57
After the design: confirm personas and protocol
- Distinctive: line 58
After pilots: confirm sensitivity is acceptable before scaling
- Distinctive: line 59
Before reporting: agree on the labeling of results
≈ “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.
Files
<!-- Generated from .claude/skills/build-llm-agents/SKILL.md by tools/sync_agents.py. Edit the source, then run the script. -->/build-llm-agents — Build LLM Agents
Category: Build (AI) · Primary agent: llm-agent-simulation-specialist
Builds LLM-agent economic simulations (synthetic households, firms, forecasters, negotiators) with sensitivity and human-data checks.
Arguments: whatever the user wrote after the command name.
Purpose
Build an economic simulation populated by LLM-powered agents (synthetic households, firms, forecasters or negotiators) and measure how much of what they do reflects stable behavior rather than prompt wording or model choice. The output is an exploratory simulation with sensitivity and reproducibility evidence, compared with human data wherever it exists.
Use it when piloting surveys or experiments, exploring expectation formation and reactions to communication, or prototyping behavioral rules for agent-based models.
Do not use it when results will be presented as evidence of human behavior without validation, or when a calibrated behavioral or agent-based model already answers the question (/build-abm).
Before you start
- Check required inputs. For each input below record
FOUNDorABSENT(never 'assumed'):- Simulation design
- Human data for calibration (if any)
If a required input is
ABSENT, that part isNOT 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.
- 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. - Collaboration. Follow
.claude/docs/collaboration-protocol.md: ask questions first, present options, get approval before writing files, and updateproduction/session-state/active.mdafter each approved section.
Agents
llm-agent-simulation-specialist— primary agent; coordinates the work and integrates resultsagent-based-modeling-specialist— Builds agent-based macro and financial modelsmulti-agent-rl-specialist— Builds multi-agent reinforcement learning systems for strategic economic interaction
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)
| Decision | Typical options | What it changes |
| Personas | survey-grounded demographics, stylized types | Representativeness |
| Information and memory | fixed context, evolving memory, news feeds | Dynamics of beliefs |
| Protocol | survey questions, market game, negotiation | What is measured |
| Models | at least two LLMs; versions pinned | Model dependence |
| Validation data | human surveys, lab experiments | Strength of conclusions |
Workflow
- Specify agent personas, information sets, memory and decision protocols
- Use structured outputs; record prompts and versions
- Run pilot simulations across prompts, seeds and at least two LLMs
- Compare behavior to human experimental or survey evidence
- Compare means, dispersion, treatment effects and heterogeneity
- Check for contamination from well-known published experiments
- Quantify prompt and model sensitivity; label results exploratory unless validated
- Document reproducibility details (model versions, temperature, seeds)
Checkpoints with the user
- After the design: confirm personas and protocol
- After pilots: confirm sensitivity is acceptable before scaling
- Before reporting: agree on the labeling of results
Common pitfalls
- Treating simulated agents as representative humans
- Results driven by one prompt wording
- LLMs reciting famous experiments rather than behaving
- Large simulated samples giving false precision
Output
models/llm/<name>-agents/
The folder holds persona and protocol definitions, prompts, run scripts, raw outputs, sensitivity analysis, the human-data comparison and a reproducibility record. Every run saves its results to output/<run-id>/ in the model folder, with a run log (.claude/rules/model-code.md).
Gate / verdict
- Sensitivity across prompts and models reported
- Output labelled exploratory unless validated against human data
- Prompts, model versions, temperature and seeds are archived
- Contamination risk is assessed
Suggested next steps
/ai-audit/policy-simulation
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
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.

