apsr-data-analysis
Use when executing and reporting the analysis for an American Political Science Review (APSR) manuscript so it survives expert, double-anonymous review — honest uncertainty, robustness, and triangulation appropriate to quantitative, experimental, or computational work. Guides analysis norms; it does not fabricate results.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill apsr-data-analysis --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Data Analysis (apsr-data-analysis) APSR reviewers are methodologically sophisticated and the editorial office will later **re-run your code** against the manuscript's tables and figures (see `apsr-transparency-and-data-policy`). Analyze as if both are true — because they are. This skill covers execution and reporting norms; design decisions live in `apsr-research-design`. ## When to trigger - Running main and supporting analyses; building the results section - A reviewer asked for robustness, heterogeneity, or alternative specifications - Reconciling preregistered vs. exploratory analyses - Making the analysis reproducible before deposit ## Analysis norms APSR expects 1. **Report uncertainty honestly.** Confidence/credible intervals, not just stars; the magnitude and substantive meaning of the estimate, not just its significance. 2. **Robustness that probes, not decorates.** Show specifications that could *break* the result (alternative measures, samples, estimators, fixed effects), and say what you learn. 3. **Heterogeneity with discipline.** Pre-specify subgroups where possible; correct for multiple comparisons; do not mine for a significant interaction and theorize it post hoc
- When to trigger
- Analysis norms APSR expects
- Computational / text-as-data specifics
- Reproducibility while you work (not at the end)
- Execution bridge (StatsPAI / Stata MCP)
- Anti-patterns
- Output format
- What APSR reviewers probe, by analytic tradition
- Worked micro-example (illustrative numbers)
- Referee-pushback patterns and the APSR-specific repair
- Calibration anchors (hedged)
- Supplementary resources
What does the apsr-data-analysis skill do?
Use when executing and reporting the analysis for an American Political Science Review (APSR) manuscript so it survives expert, double-anonymous review — honest uncertainty, robustness, and triangulation appropriate to quantitative, experimental, or computational work. Guides analysis norms; it does not fabricate results.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill apsr-data-analysis --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From brycewang-stanford/Awesome-Journal-Skills, a repository with 909 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.