Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsCommunityBlog
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Crim Research Design

ASecurity

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.

1,052 stars
0 votes
0 copies
1 views
Added 6/5/2026
ai-agentsgitdocumentation

Security Analysis

A100/100

Scanned 6/5/2026

Install to Claude Code

$npx -y skills add brycewang-stanford/Awesome-Journal-Skills --skill crim-research-design --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Crim Research Design?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Crim Research Design
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/brycewang-stanford-crim-research-design/badge)](https://www.skillsdirectory.com/skills/brycewang-stanford-crim-research-design)

More formats (shields.io, HTML) on the badges page.

Download with Pro
Files
SKILL.md
---
name: crim-research-design
description: 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.
---

# 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.
- **Inference**: cluster at the level of treatment assignment (often place or agency); randomization
  inference for experiments; few-cluster corrections (wild-cluster bootstrap).
- **Crime-data validity**: state which construct you measure — reported crime (UCR/NIBRS), victimization
  (NCVS), or self-report — and how the **dark figure** and reporting/recording bias affect inference.

## Longitudinal / life-course / criminal careers
- **Within- vs. between-person**: use fixed effects or hybrid models to isolate within-individual change
  when the theory is about turning points or desistance.
- **Trajectory / group-based models (GBTM, growth mixture)**: justify the number of groups (BIC,
  AvePP ≥ 0.7, group shares, classification odds); treat groups as a summary, not literal types.
- **Survival / recidivism**: handle right-censoring and competing risks; distinguish timing from prevalence.
- **Criminal-career parameters**: separate onset, frequency (λ), seriousness, and desistance; do not let
  prevalence masquerade as incidence.

## Place-based & experimental
- Randomized field trials (patrol, deterrence, reentry): report power/MDE, attrition, fidelity, ethics/IRB.
- Spatial designs: address displacement vs. diffusion of benefits; near-repeat and hot-spot logic.

## Qualitative / case-based
- **Case selection** justified by design logic (typical, deviant, most/least-likely, paired comparison),
  not convenience. Say what the case is a case *of*.
- **Process tracing / life-history** with explicit tests; state what evidence would have **disconfirmed**
  the argument. Plan source documentation (see `crim-data-and-transparency`).

## The adjudication test (Criminology-specific)

For the **single strongest rival theory**, write one sentence: *"If the rival mechanism were operating
instead of mine, the crime data would look like ___; instead they look like ___."* If you cannot, the
design does not yet identify the contribution.

## Anti-patterns

- Naive TWFE on staggered policy adoption; clustering below the assignment level
- "Causal" language on a design that only supports association
- Reading trajectory groups as real, fixed offender types
- Ignoring the dark figure / reporting bias when using official counts
- Convenience case selection dressed up as theory-driven

## Output format

```
【Mode】quant-causal / longitudinal-life-course / place-experiment / qualitative
【Estimand or claim】what is being identified/shown (and within- vs. between-person)
【Crime measure】reported / victimization / self-report + dark-figure note
【Key assumption(s)】and how each is defended
【Rival ruled out】the adjudication sentence
【Robustness/sensitivity】planned checks
【Next】crim-data-analysis
```

## Supplementary resources

- [`../../resources/external_tools.md`](../../resources/external_tools.md) — trajectory/survival/spatial packages and longitudinal datasets
- [`../../resources/official-source-map.md`](../../resources/official-source-map.md) — Criminology scope and methodological breadth

Attribution

brycewang-stanfordbrycewang-stanford
View sourceMore from brycewang-stanford →
SSkills DirectorySkills Directory

Know which skills are safe — weekly.

Best new skills + every skill we flagged as malicious. From the team that scanned 103,619.

Join free

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Know which skills are safe — weekly.

Best new skills + every skill we flagged as malicious. From the team that scanned 103,619.

Join free

Related Skills

Caveman

Ultra-compressed communication mode that cuts output tokens while keeping technical accuracy. Levels: lite, full, ultra and the wenyan variants. Use for /caveman, "caveman mode", "talk like caveman", "be brief" or "less tokens".

1066601 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

693161 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3351 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

651 votes

math-skill

A comprehensive mathematical reasoning skill for AI assistants — handles arithmetic to research-level problems with rigorous step-by-step reasoning, systematic verification, and transparent uncertainty handling

381 votes
View all in ai-agents →