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

Demog Research Design

ASecurity

Use when defending the research design of a Demography (PAA / Duke University Press) manuscript — choosing among demographic methods (life tables, decomposition, event-history/survival, age-period-cohort, multistate, microsimulation, projections) and, where the question is causal, defending identification. Demography judges each method 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-agents

Security Analysis

A100/100

Scanned 6/5/2026

Install to Claude Code

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

Installs into .claude/skills of the current project.

Are you the author of Demog Research Design?

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

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

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

Download with Pro
Files
SKILL.md
---
name: demog-research-design
description: Use when defending the research design of a Demography (PAA / Duke University Press) manuscript — choosing among demographic methods (life tables, decomposition, event-history/survival, age-period-cohort, multistate, microsimulation, projections) and, where the question is causal, defending identification. Demography judges each method on its own terms. Strengthens the design; it does not write code.
---

# Research Design (demog-research-design)

Demography accepts a wide variety of methodological approaches but is demanding about each. The design
must credibly connect the argument (`demog-theory-building`) to the demographic evidence. This skill is
method-aware: pick the section that matches your question and defend it against the strongest rival
explanation.

## When to trigger

- Choosing the demographic method that actually answers the question
- A reviewer questioned the rate construction, the identification, or the projection assumptions
- Specifying an age-period-cohort, multistate, or microsimulation design
- Justifying why your design adjudicates the rival account from `demog-literature-positioning`

## Match the method to the question

- **Life tables** — for survival, life expectancy, and exposure: period vs. cohort, abridged vs.
  complete; multiple-decrement (cause-specific) and multistate (healthy/disabled) where relevant.
- **Decomposition** — to attribute a difference or change in a rate to components: Kitagawa
  (rate vs. composition), Arriaga (age contributions to e0), Horiuchi continuous, Das Gupta
  (multi-factor). Say exactly **what each component means**.
- **Event-history / survival** — for timing and transitions: Cox, parametric, discrete-time, with
  **competing risks** and **multistate** models when several destinations matter; check the
  proportional-hazards assumption.
- **Age-period-cohort** — confront the **identification problem head-on**: APC effects are linearly
  dependent, so state the constraint or modeling assumption (and its substantive justification) you
  rely on; do not present a single "identified" APC partition as if it were assumption-free.
- **Multistate / projections / microsimulation** — make transition rates, the base population, and the
  assumptions (closed/open, period/cohort) explicit; report sensitivity to key assumptions.

## When the question is causal
- **Identification first.** State the estimand and the assumptions licensing a causal reading
  (ignorability, parallel trends, exclusion, continuity); defend them, don't assert them.
- **Selection and exposure** are demographic hazards: mortality selection, migration selection, and
  differential exposure can masquerade as effects — address them explicitly.
- **Inference.** Cluster at the right level (e.g., household, region, cohort); use survey weights and
  design for complex samples; report uncertainty for derived demographic quantities.
- **Sensitivity.** How strong must an unobserved confounder (or a violated rate assumption) be to
  overturn the result?

## The adjudication test (Demography-specific)

For the **single strongest rival explanation** (e.g., compositional change, selection, tempo
distortion), write one sentence: *"If the rival were true rather than my account, the age/cohort
pattern would look like ___; instead it looks like ___."* If you cannot, the design does not yet
identify the contribution.

## Anti-patterns

- Running a regression when the question calls for a life table, a decomposition, or an event-history model
- Presenting an APC decomposition without naming the identifying constraint
- Period rates read as cohort experience (or vice versa) without justification
- Ignoring mortality/migration selection in a survival or panel design
- Projections whose assumptions are buried instead of varied and reported

## Output format

```
【Method】life table / decomposition / event history / APC / multistate / microsim / projection / causal
【Quantity / estimand】what is being measured or identified
【Key assumption(s)】and how each is defended (name the APC constraint if used)
【Rival ruled out】the adjudication sentence
【Robustness/sensitivity】planned checks
【Next】demog-data-analysis
```

## Supplementary resources

- [`../../resources/external_tools.md`](../../resources/external_tools.md) — life-table, decomposition, survival, APC, and microsimulation packages
- [`../../resources/official-source-map.md`](../../resources/official-source-map.md) — Demography 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.

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 →