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

Ajps Research Design

ASecurity

Use when defending the research design of an American Journal of Political Science (AJPS) manuscript — causal identification for observational work, experimental and survey-experimental design, formal-empirical linkage, or case-based inference. AJPS reviewers are quantitatively demanding, so identification must license the claim being made. Strengthens the design; it does not write code.

1,052 stars
0 votes
0 copies
0 views
Added 6/4/2026
ai-agentspythondocumentation

Security Analysis

A100/100

Scanned 6/4/2026

Install to Claude Code

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

Installs into .claude/skills of the current project.

Are you the author of Ajps Research Design?

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

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

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

Download with Pro
Files
SKILL.md
---
name: ajps-research-design
description: Use when defending the research design of an American Journal of Political Science (AJPS) manuscript — causal identification for observational work, experimental and survey-experimental design, formal-empirical linkage, or case-based inference. AJPS reviewers are quantitatively demanding, so identification must license the claim being made. Strengthens the design; it does not write code.
---

# Research Design (ajps-research-design)

AJPS publishes many methods but holds identification and inference to a high standard. The design must
credibly connect the argument (`ajps-theory-building`) to evidence and rule out the strongest rival.
This skill is mode-aware: pick the section that matches your work and defend it on its own terms.

## When to trigger

- Specifying identification, sampling, case selection, or experimental design
- A reviewer questioned causal claims, a confound, external validity, or inference
- Preparing a **pre-analysis plan** before collecting/analyzing data
- Justifying why your design adjudicates the rival from `ajps-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; do not assert them.
- **Designs**: experiments (incl. survey/conjoint), DID/event study (use modern staggered-adoption
  estimators, not naive TWFE), IV (first-stage strength, exclusion, weak-IV-robust inference), RDD
  (density/manipulation tests, bandwidth robustness), matching/weighting with balance + sensitivity.
- **Inference**: cluster at the level of treatment assignment; randomization inference for
  experiments; small-cluster corrections (wild-cluster bootstrap) when clusters are few.
- **Sensitivity**: how strong must an unobserved confounder be to overturn the result?

## Experiments (lab / survey / field)
- Preregister the design and primary analyses; report power / MDE; pre-specify subgroups.
- Address attention/manipulation checks, attrition, balance, and ethics/IRB and consent (the AJPS
  submission portal asks for human-subjects documentation — see `ajps-submission`).
- For survey experiments: sampling frame, treatment realism, and the limits on generalization.

## Formal-empirical linkage
- Make the **empirical test follow from the model's comparative statics**, not a loose analogy.
- Distinguish predictions unique to your model from those shared with rivals, and test the unique ones.

## Case-based / qualitative & multi-method
- **Case selection** justified by design logic (typical, deviant, most/least-likely, paired) — say what
  the case is a case *of*.
- **Process tracing** with explicit tests (hoop, smoking-gun, straw-in-the-wind); state what evidence
  would have **disconfirmed** the argument; plan source documentation (see
  `ajps-replication-and-verification`, qualitative path).

## The adjudication test (AJPS-specific)

For the single strongest rival explanation, write: *"If the rival were true rather than my argument,
the 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 treatment; clustering at the wrong level
- "Causal" language on a design that supports only association
- Convenience case selection dressed up as theory-driven
- Survey/conjoint experiments over-generalized to real-world behavior with no caveat
- A design that cannot distinguish your argument from the leading alternative

## Output format

```
【Mode】quant-causal / experiment / formal-empirical / case-based
【Estimand or claim】what is being identified/shown
【Key assumption(s)】and how each is defended
【Rival ruled out】the adjudication sentence
【Inference】clustering / RI / small-cluster correction
【Robustness/sensitivity】planned checks
【Next】ajps-data-analysis
```

## Supplementary resources

- [`../../resources/external_tools.md`](../../resources/external_tools.md) — design/identification packages (R/Stata/Python) and CAQDAS for qualitative work
- [`../../resources/official-source-map.md`](../../resources/official-source-map.md) — human-subjects / IRB requirements and submission policy

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".

1074701 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.

691 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 →