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

build-drl-policy

Skill4 starsChanged 6 days agoMITView on GitHub

Builds a deep reinforcement learning policy environment and agent for monetary, fiscal or macroprudential policy.

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:

    Verify the environment: known-optimal cases and unit tests for state transitions

    line 50
  4. Distinctive:

    After the reward: confirm it matches the mandate

    line 60
  5. Distinctive:

    After environment verification: confirm the simulator is fit for purpose

    line 61
  6. Distinctive:

    After benchmarks: decide whether robustness testing is warranted

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

/build-drl-policy — Build DRL Policy

Category: Build (AI) · Primary agent: deep-reinforcement-learning-specialist

Builds a deep reinforcement learning policy environment and agent for monetary, fiscal or macroprudential policy.

Arguments: whatever the user wrote after the command name.

Purpose

Build a deep reinforcement learning environment and agent that learns a monetary, fiscal or macroprudential policy inside a validated structural simulator, and test whether the learned policy is better than simple rules, robust outside its training conditions, and explainable. The output is a policy evaluation, not a recommendation, until all comparisons and robustness tests pass.

Use it when the policy problem is nonlinear or high-dimensional enough that classical optimal-policy methods are impractical, or robustness across models and regimes is the focus.

Do not use it when a linear-quadratic optimal policy or optimized simple rule can be computed directly (/policy-simulation), or the simulator itself is not yet validated (/validate-model).

Before you start

  1. Check required inputs. For each input below record FOUND or ABSENT (never 'assumed'):
    • Structural simulator or approved environment spec
    • Welfare criterion 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

  • deep-reinforcement-learning-specialist — primary agent; coordinates the work and integrates results
  • monetary-policy-rules-specialist — Designs and evaluates monetary policy rules
  • multi-agent-rl-specialist — Builds multi-agent reinforcement learning systems for strategic economic interaction
  • differentiable-programming-specialist — Builds differentiable economic models in JAX/PyTorch/Julia

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
Simulatorsemi-structural, DSGE, agent-basedRealism and speed
Observationobservable data only, latent statesReal-world implementability
Rewardwelfare, quadratic loss with mandate weightsWhat the policy optimizes
AlgorithmPPO, SAC, TD3, model-basedStability and sample efficiency
Robustness designdomain randomization, adversarial shocks, model ensemblesOut-of-distribution performance

Workflow

  1. Agree the welfare-based reward with the economic-reasoning-specialist and write the environment spec
    • States, actions with bounds, reward, discounting, episode design
  2. Verify the environment: known-optimal cases and unit tests for state transitions
    • Reproduce known optimal policies in a linear-quadratic special case
  3. Train agents (PPO/SAC/TD3) with multiple seeds; log learning curves
  4. Compare the learned policy with Taylor-type and optimal-policy benchmarks
    • Same shock sequences for all policies; welfare differences with uncertainty
  5. Stress-test out-of-distribution: other shocks, parameters, misspecified models
    • Explain the learned policy with policy-function plots or a surrogate rule
  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 reward: confirm it matches the mandate
  • After environment verification: confirm the simulator is fit for purpose
  • After benchmarks: decide whether robustness testing is warranted

Common pitfalls

  • Reward that differs from welfare
  • Policies that exploit simulator artifacts
  • Best-seed reporting
  • Recommending policies without simple-rule comparison

Output

models/ai/<name>-drl/ and docs/models/<name>/experiment-log.md (+ model.lego.json)

The model folder holds the environment, agent code, training logs across seeds, benchmark comparisons and robustness results; the experiment log records every run; the lego manifest registers the policy brick. Every run saves its results to output/<run-id>/ in the model folder, with a run log (.claude/rules/model-code.md).

Gate / verdict

  • Reward is welfare-based and approved
  • Simple-rule benchmark compared
  • Out-of-distribution test passed or limits documented
  • Lego manifest passes python tools/lego.py check
  • Results are reported across seeds
  • The learned policy is explained with a policy-function plot or surrogate rule

Suggested next steps

  • /ai-audit
  • /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.