Use when executing and reporting the analysis for a Criminology (ASC / Wiley) manuscript so it survives expert review — honest uncertainty, robustness, and methods appropriate to crime counts, longitudinal panels, trajectory models, and recidivism survival. Guides analysis norms; it does not fabricate results.
Scanned 6/5/2026
Install to Claude Code
npx -y skills add brycewang-stanford/Awesome-Journal-Skills --skill crim-data-analysis --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Crim Data Analysis?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/brycewang-stanford-crim-data-analysis)More formats (shields.io, HTML) on the badges page.
---
name: crim-data-analysis
description: Use when executing and reporting the analysis for a Criminology (ASC / Wiley) manuscript so it survives expert review — honest uncertainty, robustness, and methods appropriate to crime counts, longitudinal panels, trajectory models, and recidivism survival. Guides analysis norms; it does not fabricate results.
---
# Data Analysis (crim-data-analysis)
*Criminology* reviewers are methodologically sophisticated and increasingly expect that your results
can be reproduced from deposited materials (see `crim-data-and-transparency`). Analyze as if both are
true. This skill covers execution and reporting norms; design decisions live in `crim-research-design`.
## When to trigger
- Running main and supporting analyses; building the results section
- A reviewer asked for robustness, heterogeneity, or alternative specifications
- Fitting a trajectory model, fixed-effects panel, count model, or survival model
- Making the analysis reproducible before deposit
## Analysis norms Criminology expects
1. **Report uncertainty honestly.** Confidence/credible intervals, not just stars; the **magnitude and
substantive meaning** (e.g., incident-rate ratios, predicted counts, change in offending), not just
significance.
2. **Right model for crime data.** Counts are over-dispersed and zero-heavy — prefer negative binomial /
zero-inflated / hurdle over OLS on raw counts; rates need exposure offsets; rare-event cautions apply.
3. **Within- vs. between-person.** When the theory is developmental, isolate within-individual change
(fixed effects / hybrid models); do not interpret a between-person association as a life-course effect.
4. **Trajectory models with discipline.** Report BIC across solutions, group shares, average posterior
probabilities (AvePP ≥ 0.7), and odds of correct classification; do not over-interpret the group count.
5. **Survival / recidivism.** Handle right-censoring and competing risks; report the relevant hazard, not
just a binary "recidivated."
6. **Robustness that probes, not decorates.** Show specs that could *break* the result (alternative crime
measures, samples, estimators, fixed effects) and say what you learn.
7. **Right inference.** Cluster at the assignment/sampling level (often place or agency); randomization
inference for experiments; few-cluster corrections when clusters are sparse.
## Crime-measurement specifics
- State whether the outcome is reported crime, victimization, or self-report, and how the **dark figure**,
reporting, and recording changes (e.g., UCR→NIBRS transition) could bias trends.
- Validate scales (self-report delinquency, legitimacy, collective efficacy); report reliability.
## Reproducibility while you work (not at the end)
- One **master script** regenerates every table and figure from the (raw or constructed) data.
- **Set and report seeds** for bootstrap, randomization inference, EM-based trajectory fitting, simulation.
- Pin software/package versions (`renv.lock`, `requirements.txt`, recorded `ssc`/`net`/`traj` installs).
- Keep table/figure numbers matched to script outputs; document restricted-data steps that others can't rerun.
## Anti-patterns
- OLS on raw, over-dispersed crime counts; ignoring exposure/offsets
- Stars-only tables with no rate ratios, effect sizes, or intervals
- Treating trajectory groups as literal offender types; cherry-picking the group count
- Reading a between-person coefficient as within-individual desistance
- "Robustness" that only reruns near-identical specs; p-hacking a significant interaction
## Output format
```
【Main estimate】magnitude (IRR / predicted count / hazard) + interval + substantive meaning
【Crime measure】reported / victimization / self-report + dark-figure caveat
【Within vs between】isolated correctly? [Y/N/NA]
【Model fit】counts: dispersion handled? trajectory: BIC/AvePP reported? [Y/N/NA]
【Robustness】specs that could break it → what held
【Reproducible】master script + seeds + pinned versions? [Y/N]
【Next】crim-tables-figures
```
## Supplementary resources
- [`../../resources/external_tools.md`](../../resources/external_tools.md) — count, trajectory, survival, and spatial packages
- [`../../resources/official-source-map.md`](../../resources/official-source-map.md) — transparency expectations and crime-data sources
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!