Agent skill · Design & Presentation

crim-research-design

Use when defending the research design of a Criminology (ASC / Wiley) manuscript — causal identification for quantitative work, longitudinal and life-course designs, criminal-career and trajectory methods, place-based and experimental designs, or case selection and process tracing for qualitative work. Criminology judges each tradition on its own terms. Strengthens the design; it does not write code.

brycew6m878★ · +32/wk · 1 repos on radarProfile →
claude-codeMIT
Install
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill crim-research-design --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 8 KB
Bundled scripts: none
Path: Criminology-Skills/skills/crim-research-design/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 909 · +31 this week
Language: Stata
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Research Design (crim-research-design) *Criminology* accepts many methodologies but is demanding about each. The design must credibly connect the mechanism (`crim-theory-building`) to crime evidence. This skill is mode-aware: pick the section that matches your work and defend it against the strongest rival explanation. ## When to trigger - Specifying identification, a longitudinal design, case selection, or an experiment - A reviewer questioned causal claims, selection, the dark figure, or a confound - Choosing between a trajectory model, fixed-effects panel, or survival design - Justifying why your design adjudicates the rival theory from `crim-literature-positioning` ## Quantitative / causal inference - **Identification first.** State the estimand and the assumptions that license a causal reading (ignorability, parallel trends, exclusion, continuity). Defend them; don't assert them. - **Designs**: experiments (incl. randomized policing/hot-spot trials), DID/event study (use modern staggered-adoption estimators, not naive TWFE), IV (first-stage strength, exclusion), RDD (density/manipulation tests, bandwidth robustness), matching/weighting with balance + sensitivity. - **Inferen

What's inside
Steps it walks through
  1. When to trigger
  2. Quantitative / causal inference
  3. Longitudinal / life-course / criminal careers
  4. Place-based & experimental
  5. Qualitative / case-based
  6. The adjudication test (Criminology-specific)
  7. Execution bridge (StatsPAI / Stata MCP)
  8. Anti-patterns
  9. Identification expectations by design (Criminology calibration table)
  10. Worked micro-example: a deterrence-policy quasi-experiment (illustrative)
  11. Design-stage referee pushback (with the Criminology fix)
  12. Output format
  13. Supplementary resources
More from Awesome-Journal-Skills
All skills →
About this skill
What does the crim-research-design skill do?

Use when defending the research design of a Criminology (ASC / Wiley) manuscript — causal identification for quantitative work, longitudinal and life-course designs, criminal-career and trajectory methods, place-based and experimental designs, or case selection and process tracing for qualitative work. Criminology judges each tradition on its own terms. Strengthens the design; it does not write code.

How do I install it?

Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill crim-research-design --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.

Keep going