Individual skill

jpam-data-analysis

Use when running and reporting the estimation for a Journal of Policy Analysis and Management (JPAM) manuscript — program-evaluation estimates plus the cost-benefit and distributional analysis JPAM expects, with robustness, heterogeneity, and honest uncertainty. Guides analysis norms; it does not replace the identification design.

Journal-of-Policy-Analysis-and-Management-Skills/skills/jpam-data-analysis/SKILL.md

Read pinned source

Source commit 932eb23331721b16e967c59f093781be1928b498

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Network or broad shell
Last checked
Nov 9, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,403
Repository last updated
Sep 27, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Data Analysis: Estimation, Cost-Benefit & Distribution (jpam-data-analysis)

JPAM analysis has two layers most field-journal papers skip: beyond the **causal estimate**, reviewers
expect attention to **cost-benefit** and **distributional** consequences — *who gains, who pays, and is
it worth it?* The estimate answers "does the policy work"; the cost-benefit and distributional work
answers "should we do it, and for whom." Both must be reported honestly, with uncertainty carried
through.

## When to trigger

- Producing the main estimates and the robustness/heterogeneity suite
- Adding (or being asked to add) cost-benefit or distributional analysis
- A reviewer questioned standard errors, robustness, or the policy-relevance of the magnitude
- Translating an effect size into a decision-relevant quantity (per-dollar, per-recipient, MVPF)
Back to top