AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Aejpol Theory Model

skill-brycewang-stanford-awesome-journal-skills-aejpol-theory-model · by brycewang-stanford

Use when an AEJ: Economic Policy manuscript needs a framework that maps reduced-form estimates into a welfare, cost-benefit, or distributional policy object — sufficient statistics, MVPF, optimal-policy, or a small applied model. Builds the estimate-to-welfare bridge and states its assumptions; it does not run the empirical estimation or write the prose.

No reviews yet
0 installs
35 views
0.0% view→install

Install

$ agentstack add skill-brycewang-stanford-awesome-journal-skills-aejpol-theory-model

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-brycewang-stanford-awesome-journal-skills-aejpol-theory-model)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
2mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Aejpol Theory Model? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Theory / Welfare Model — Estimate-to-Policy Bridge (aejpol-theory-model)

When to trigger

  • You have a credible causal estimate but no framework to say what it means for welfare or policy
  • A referee says the welfare claim is "hand-waved" or the "so what" is missing
  • You need to convert an elasticity / treatment effect into a cost-benefit or optimal-policy statement
  • A reviewer asks "what is the sufficient statistic, and does your estimate identify it?"

The AEJ: Policy role of theory

At AEJ: Policy theory is usually in service of the policy reading, not the headline. Most papers do not need a full structural model; they need a transparent framework that turns a reduced-form estimate into a welfare, cost-benefit, or distributional object a policymaker can use. Pick the lightest framework that delivers the policy statement and make its assumptions explicit.

Bridge paths (lightest first)

Path A: Sufficient statistics / MVPF
  • Write the welfare expression and show which estimated objects are the sufficient statistics (e.g., an elasticity, a fiscal externality, a pass-through). State that your design identifies exactly those.
  • For spending/tax policies, a Marginal Value of Public Funds (benefit to recipients per dollar of net government cost) is the canonical AEJ: Policy summary — define the numerator and denominator and which estimates feed each.
  • State the assumptions the sufficient-statistic formula buys you (envelope conditions, no income effects, partial-equilibrium scope) and where they could fail.
Path B: Cost-benefit / fiscal accounting
  • Build the explicit ledger: program cost, behavioral-response fiscal effects, benefits to recipients, externalities. Show the net cost per unit of outcome (cost per job, per ton abated, per QALY-equivalent, per child lifted) with uncertainty propagated from the estimate's SE.
  • Distinguish mechanical from behavioral effects; the behavioral term is what your causal estimate supplies.
Path C: Optimal-policy / re-optimization
  • Use the estimated elasticity in a standard optimal-tax / optimal-transfer formula to back out the policy-relevant optimum, then compare to the status quo. Frame as "the policy-relevant elasticity implies the current level is too high/low."
Path D: Small calibrated / structural model
  • Only when reduced-form + sufficient statistics cannot deliver the counterfactual (general-equilibrium feedback, extrapolation beyond observed variation). Tie parameters to data, validate against untargeted moments, and argue policy-invariance for the counterfactual (Lucas critique).

Distributional reading

Whatever the path, ask who gains and who pays. An incidence split across income, region, or demographic groups is often the AEJ: Policy contribution and is cheap to add once the estimate exists.

Checklist

  • [ ] The welfare/policy object is named (MVPF, net cost-per-outcome, optimum, incidence)
  • [ ] The sufficient statistic(s) are identified by the empirical design, not assumed
  • [ ] The framework's assumptions are stated and their failure modes flagged
  • [ ] Uncertainty from the estimate is propagated into the welfare number
  • [ ] A distributional / incidence reading is provided where the policy has clear winners and losers
  • [ ] The model is no heavier than the policy statement requires

Anti-patterns

  • A welfare claim with no formula linking it to the estimate ("this is welfare-improving" asserted)
  • Importing a sufficient-statistic formula whose assumptions your setting violates
  • A full structural model where a one-line MVPF would have sufficed (overengineering)
  • Reporting a point welfare number with no uncertainty band
  • Ignoring incidence when the policy obviously redistributes

Worked vignette (illustrative)

A clean RDD shows a benefit-eligibility threshold raises take-up and reduces hardship. Alone it is "the program helps." Bridged: the take-up and hardship estimates are the sufficient statistics for an MVPF — recipients value the transfer at, say, $1.20 per $1 of net government cost after behavioral offsets (illustrative) — and the incidence falls mostly on the lowest-income tercile. Now the paper states whether the program is a good use of public funds and for whom.

Output format

【Policy object】MVPF / net cost-per-outcome / optimum / incidence
【Framework】sufficient statistics / cost-benefit ledger / optimal-policy / small model
【Sufficient statistic(s)】which estimates feed the welfare expression
【Key assumptions + failure modes】[...]
【Uncertainty】how the estimate's SE propagates to the welfare number
【Distributional reading】who gains / who pays
【Next step】aejpol-robustness then aejpol-writing-style

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.