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

Io Research Design

ASecurity

Use when defending the research design of an International Organization (IO) manuscript on international-level questions — causal identification with dyadic/TSCS/network data, case selection and process tracing for international cases, survey/conjoint experiments on foreign-policy attitudes, or formal-empirical linkage. IO judges each IR tradition on its own terms and verifies results and proofs before final acceptance. Strengthens the design; it does not write code.

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

Security Analysis

A100/100

Scanned 6/5/2026

Install to Claude Code

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

Installs into .claude/skills of the current project.

Are you the author of Io Research Design?

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

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

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

Download with Pro
Files
SKILL.md
---
name: io-research-design
description: Use when defending the research design of an International Organization (IO) manuscript on international-level questions — causal identification with dyadic/TSCS/network data, case selection and process tracing for international cases, survey/conjoint experiments on foreign-policy attitudes, or formal-empirical linkage. IO judges each IR tradition on its own terms and verifies results and proofs before final acceptance. Strengthens the design; it does not write code.
---

# Research Design (io-research-design)

IO accepts quantitative, formal, and qualitative IR work but is demanding about each. The design must
credibly connect the **IR theory** (`io-theory-building`) to evidence at or across the **international
level**, and rule out the strongest rival international explanation. This skill is mode-aware: pick the
section that matches your work.

## When to trigger

- Specifying identification, case selection, or experimental design for an IR question
- A reviewer questioned causal claims, the level of analysis, generalization, or a confound
- Preparing a pre-analysis plan for a foreign-policy experiment
- Justifying why the design adjudicates the rival IR account from `io-literature-positioning`

## Quantitative / causal inference (often dyadic, TSCS, or network)
- **Get the level of analysis right.** State the unit (state-year, dyad-year, IGO, directed dyad,
  sub-state, transnational) and why it matches the theory. Many IR mistakes are unit/level mistakes.
- **Identification first.** State the estimand and the assumptions that license a causal reading
  (ignorability, parallel trends, exclusion, continuity); defend them, don't assert them.
- **IR-specific inference traps**: non-independence in **dyadic data** (cluster on both members /
  multiway, or use AME/network models); spatial and temporal dependence in TSCS; selection into
  alliances/treaties/conflict; reverse causation (does the institution cause the behavior or vice versa).
- **Designs**: natural experiments and DID/event study (modern staggered estimators, not naive TWFE),
  IV with credible exclusion at the international level, RDD where thresholds exist, matching/weighting
  with balance + sensitivity, gravity/PPML for trade flows.
- **Sensitivity**: how strong must an unobserved confounder be to overturn the result?

## Qualitative / case-based (international cases)
- **Case selection** justified by design logic (typical, deviant, most/least-likely, paired comparison
  across dyads or institutions) — say what the case is a case *of* in IR terms.
- **Process tracing** with explicit tests (hoop, smoking-gun, straw-in-the-wind); state what evidence
  would have **disconfirmed** the international mechanism.
- **Source transparency**: archives, diplomatic records, elite interviews — plan documentation and
  citation now (QDR; see `io-transparency-and-data-policy`).

## Experiments (survey / conjoint / lab on foreign-policy attitudes)
- Preregister design and primary analyses; report power/MDE; pre-specify subgroups.
- Be explicit about **external validity**: from public-opinion or elite-survey results to actual
  state behavior is a real inferential leap — caveat it.

## Formal-empirical linkage (a core IO design)
- 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 rival IR theories.
- Plan the **proof appendix** the IO editorial staff will verify before final acceptance.

## The adjudication test (IO-specific)

For the **single strongest rival international explanation**, write one sentence: *"If the rival were
true rather than my argument, the international data/cases would look like ___; instead they look like
___."* If you cannot, the design does not yet identify the IR contribution.

## Anti-patterns

- Ignoring dyadic non-independence; clustering at the wrong level; naive TWFE on staggered treatment
- A domestic-level design used to support an international-level claim (level mismatch)
- "Causal" language on a design that only supports association across states
- Convenience case selection dressed up as theory-driven
- Over-generalizing survey-experiment attitudes to real state behavior with no caveat

## Output format

```
【Mode】quant-causal / qualitative / experiment / formal-empirical
【Level of analysis】unit + why it matches the IR theory
【Estimand or claim】what is being identified/shown
【Key assumption(s)】and how each is defended (incl. dyadic/TSCS dependence)
【Rival ruled out】the adjudication sentence
【Robustness/sensitivity / proof appendix】planned
【Next】io-data-analysis
```

## Supplementary resources

- [`../../resources/external_tools.md`](../../resources/external_tools.md) — dyadic/network/gravity packages and CAQDAS for qualitative IR
- [`../../resources/official-source-map.md`](../../resources/official-source-map.md) — formal-proof and quantitative-result verification 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".

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.

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 →