/new-project
Start a new research project by conducting a structured interview to formalize a research idea, then generates research questions with identification strategies and a project spec. Make sure to use this skill whenever the user wants to develop or document a new research idea —
$ npx -y skills add brycewang-stanford/Auto-Empirical-Research-Skills --skill new-project --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/new-project
Context preview
The summary Claude sees to decide when to auto-load this skill.
Start a new research project by conducting a structured interview to formalize a research idea, then generates research questions with identification strategies and a project spec. Make sure to use this skill whenever the user wants to develop or document a new research idea —
SKILL.md
new-project.SKILL.mdname: new-project
description: >-
Start a new research project by conducting a structured interview to formalize a research idea, then generates research questions with identification strategies and a project spec. Make sure to use this skill whenever the user wants to develop or document a new research idea — not to search for literature or data. Triggers include: "new project", "start research", "I have an idea", "help me develop this", "I want to study X", "help me formalize this idea", "what's my research question", "what identification strategy should I use", "write up my project idea", or when the user describes a topic they want to turn into a paper.
argument-hint: "[brief topic or 'start fresh']"
allowed-tools: ["Read", "Grep", "Glob", "Write"]
New Research Project
Formalize a research idea into a concrete project specification with testable hypotheses and empirical strategies.
**Input:** `$ARGUMENTS` — a topic, phenomenon, dataset, or "start fresh" for open-ended exploration.
This skill runs in **three phases**. Phase 1 is conversational — ask one or two questions at a time and wait for responses. Phases 2 and 3 run automatically after the interview.
---
Phase 1: Research Interview
**Goal:** Draw out the researcher's thinking and establish a clear research question.
Ask questions **one or two at a time**. Build on each answer before moving to the next phase. Do NOT use AskUserQuestion — ask directly in your response. A good interview runs 4–6 exchanges.
Question Bank (select and adapt based on context)
**The Puzzle (start here):**
- "What phenomenon or puzzle are you trying to understand?"
- "What do you observe in the data / world that doesn't fit the standard explanation?"
**Why It Matters:**
- "Why does this matter? Who should care about the answer?"
- "Is there a policy lever here, or is this more about understanding a mechanism?"
**Theoretical Motivation:**
- "What's your intuition for why X happens — what's the mechanism?"
- "What would standard theory predict? Do you expect to find something different, and why?"
**Data and Setting:**
- "Do you have data in mind, or are you open on the data source?"
- "Is there a specific context, time period, country, or institutional setting you're focused on?"
**Identification:**
- "Is there a natural experiment, policy change, or discontinuity you could exploit?"
- "What's the biggest threat to a causal interpretation — what would a skeptic say?"
**Expected Results + Contribution:**
- "What would you expect to find? What would genuinely surprise you?"
- "What existing papers are closest to this? What gap does yours fill?"
When to Stop Interviewing
Move to Phase 2 when you have:
- A clear research question (one sentence)
- At least one plausible identification strategy
- Some sense of what data exists or is needed
- The motivation / contribution
If after 3 exchanges the user keeps giving vague answers, move to Phase 2 anyway and flag the open questions.
---
Phase 2: Research Ideation
**Goal:** Generate 3–5 structured research questions covering the full range from descriptive to causal.
Announce the transition: *"Great — I have enough to generate a structured set of research questions. Let me build that out now."*
Then generate **3–5 research questions** ordered by type:
| Type | What It Asks | |------|-------------| | **Descriptive** | What are the patterns? How has X evolved? | | **Correlational** | What factors are associated with X, controlling for Z? | | **Causal** | What is the causal effect of X on Y? | | **Mechanism** | Through what channel does X affect Y? | | **Policy** | Would intervention X improve outcome Y? |
**For each RQ, develop:**
- **Hypothesis** — testable prediction with expected direction/magnitude
- **Identification Strategy:**
- Method (DiD, RDD, IV, synthetic control, etc.)
- Treatment (what varies, when, where)
- Control group (comparison units)
- Key assumption (parallel trends, exclusion restriction, etc.)
- Main robustness checks (pre-trends test, placebo, etc.)
- **Data requirements** — what variables, time period, geography, unit of observation
- **Key pitfalls** — 2 main threats to identification + mitigations
- **Related work** — 2-3 papers using similar approaches (name only, no fabrication)
**Rank the questions** by feasibility × contribution:
| RQ | Feasibility | Contribution | Priority | |----|-------------|-------------|----------| | 1 | High | High | ★★★ | | 2 | High | Medium | ★★ | | ... | ... | ... | ... |
---
Phase 3: Save Project Spec
Produce the unified project spec document and save it.
**Save to:** `quality_reports/project_spec_[sanitized_topic].md`
# Research Project: [Working Title]
**Date:** [YYYY-MM-DD]
**Researcher:** [from CLAUDE.md if available]
---
## Research Question
[Single clear sentence]
## Motivation
[2–3 paragraphs: why this matters, theoretical context, policy relevance, what the answer would change]
## Research Questions
### RQ1: [Question] — Priority: ★★★ (Feasibility: High / Contribution: High)
**Type:** Causal
**Hypothesis:** [Testable prediction with expected sign]
**Identification Strategy:**
- **Method:** [e.g., Staggered DiD with Sun–Abraham estimator]
- **Treatment:** [What varies and when]
- **Control group:** [Comparison units]
- **Key assumption:** [e.g., Parallel pre-trends conditional on controls]
- **Robustness:** [Pre-trends test, placebo outcomes, alternative control groups]
**Data Requirements:**
- [Dataset or data type needed]
- [Key variables: treatment proxy, outcome, controls]
- [Time period and geography]
**Key Pitfalls:**
1. [Threat + mitigation]
2. [Threat + mitigation]
**Related Work:** [Author (Year)], [Author (Year)]
---
[Repeat for RQ2–RQ5]
---
## Priority Empirical Strategy
[1 paragraph recommending the single highest-priority RQ and why, with the specific identification approach]
## Open Questions
[Issues raised in the interview that need fur
Read more
name: new-project description: >- Start a new research project by conducting a structured interview to formalize a research idea, then generates research questions with identification strategies and a project spec. Make sure to use this skill whenever the user wants to develop or document a new research idea — not to search for literature or data. Triggers include: "new project", "start research", "I have an idea", "help me develop this", "I want to study X", "help me formalize this idea", "what's my research question", "what identification strategy should I use", "write up my project idea", or when the user describes a topic they want to turn into a paper. argument-hint: "[brief topic or 'start fresh']" allowed-tools: ["Read", "Grep", "Glob", "Write"]
New Research Project
Formalize a research idea into a concrete project specification with testable hypotheses and empirical strategies.
**Input:** `$ARGUMENTS` — a topic, phenomenon, dataset, or "start fresh" for open-ended exploration.
This skill runs in **three phases**. Phase 1 is conversational — ask one or two questions at a time and wait for responses. Phases 2 and 3 run automatically after the interview.
---
Phase 1: Research Interview
**Goal:** Draw out the researcher's thinking and establish a clear research question.
Ask questions **one or two at a time**. Build on each answer before moving to the next phase. Do NOT use AskUserQuestion — ask directly in your response. A good interview runs 4–6 exchanges.
Question Bank (select and adapt based on context)
**The Puzzle (start here):**
- "What phenomenon or puzzle are you trying to understand?"
- "What do you observe in the data / world that doesn't fit the standard explanation?"
**Why It Matters:**
- "Why does this matter? Who should care about the answer?"
- "Is there a policy lever here, or is this more about understanding a mechanism?"
**Theoretical Motivation:**
- "What's your intuition for why X happens — what's the mechanism?"
- "What would standard theory predict? Do you expect to find something different, and why?"
**Data and Setting:**
- "Do you have data in mind, or are you open on the data source?"
- "Is there a specific context, time period, country, or institutional setting you're focused on?"
**Identification:**
- "Is there a natural experiment, policy change, or discontinuity you could exploit?"
- "What's the biggest threat to a causal interpretation — what would a skeptic say?"
**Expected Results + Contribution:**
- "What would you expect to find? What would genuinely surprise you?"
- "What existing papers are closest to this? What gap does yours fill?"
When to Stop Interviewing
Move to Phase 2 when you have:
- A clear research question (one sentence)
- At least one plausible identification strategy
- Some sense of what data exists or is needed
- The motivation / contribution
If after 3 exchanges the user keeps giving vague answers, move to Phase 2 anyway and flag the open questions.
---
Phase 2: Research Ideation
**Goal:** Generate 3–5 structured research questions covering the full range from descriptive to causal.
Announce the transition: *"Great — I have enough to generate a structured set of research questions. Let me build that out now."*
Then generate **3–5 research questions** ordered by type:
| Type | What It Asks | |------|-------------| | **Descriptive** | What are the patterns? How has X evolved? | | **Correlational** | What factors are associated with X, controlling for Z? | | **Causal** | What is the causal effect of X on Y? | | **Mechanism** | Through what channel does X affect Y? | | **Policy** | Would intervention X improve outcome Y? |
**For each RQ, develop:**
- **Hypothesis** — testable prediction with expected direction/magnitude
- **Identification Strategy:**
- Method (DiD, RDD, IV, synthetic control, etc.)
- Treatment (what varies, when, where)
- Control group (comparison units)
- Key assumption (parallel trends, exclusion restriction, etc.)
- Main robustness checks (pre-trends test, placebo, etc.)
- **Data requirements** — what variables, time period, geography, unit of observation
- **Key pitfalls** — 2 main threats to identification + mitigations
- **Related work** — 2-3 papers using similar approaches (name only, no fabrication)
**Rank the questions** by feasibility × contribution:
| RQ | Feasibility | Contribution | Priority | |----|-------------|-------------|----------| | 1 | High | High | ★★★ | | 2 | High | Medium | ★★ | | ... | ... | ... | ... |
---
Phase 3: Save Project Spec
Produce the unified project spec document and save it.
**Save to:** `quality_reports/project_spec_[sanitized_topic].md`
# Research Project: [Working Title] **Date:** [YYYY-MM-DD] **Researcher:** [from CLAUDE.md if available] --- ## Research Question [Single clear sentence] ## Motivation [2–3 paragraphs: why this matters, theoretical context, policy relevance, what the answer would change] ## Research Questions ### RQ1: [Question] — Priority: ★★★ (Feasibility: High / Contribution: High) **Type:** Causal **Hypothesis:** [Testable prediction with expected sign] **Identification Strategy:** - **Method:** [e.g., Staggered DiD with Sun–Abraham estimator] - **Treatment:** [What varies and when] - **Control group:** [Comparison units] - **Key assumption:** [e.g., Parallel pre-trends conditional on controls] - **Robustness:** [Pre-trends test, placebo outcomes, alternative control groups] **Data Requirements:** - [Dataset or data type needed] - [Key variables: treatment proxy, outcome, controls] - [Time period and geography] **Key Pitfalls:** 1. [Threat + mitigation] 2. [Threat + mitigation] **Related Work:** [Author (Year)], [Author (Year)] --- [Repeat for RQ2–RQ5] --- ## Priority Empirical Strategy [1 paragraph recommending the single highest-priority RQ and why, with the specific identification approach] ## Open Questions [Issues raised in the interview that need fur
📌 文档结构(2026-07-22 起): 本文件是中文默认入口 —— banner + badges + 信任面 + 9 阶段流水线速览 + 76 行合集总表。 每个合集的完整描述、按用途分组、精确数字、验证方法在 docs/CONTENT_ZH.md(扩展正文,总表行内的 → 直接跳转到对应锚点)。 English version: README-en.md · 中文扩展正文:docs/CONTENT_ZH.md · README-zh-CN.md 已弃用(重定向占位) 🌐 语言: English |
Other skills on auto-empirical-research-skills.
- /pipeline
Classical end-to-end empirical analysis workflow in the traditional Python econometric stack — pandas + numpy + scipy + statsmodels + linearmodels + pyfixest + rdrobust + econml + causalml + matplotlib/seaborn. **Defaults to economics empirical-paper style** (AER / QJE / AEJ) —
Open skill - /pipeline
Classical end-to-end empirical analysis workflow in the modern tidyverse + econometrics R ecosystem — dplyr + tidyr + haven + fixest + sandwich + lmtest + clubSandwich + AER + ivreg + did + bacondecomp + HonestDiD + eventstudyr + rdrobust + rddensity + Synth + gsynth + synthdid
Open skill - /pipeline
Classical end-to-end empirical analysis workflow in the traditional Stata ecosystem — native Stata + reghdfe + ivreg2 + csdid + did_imputation + eventstudyinteract + sdid + rdrobust + rddensity + synth + synth_runner + psmatch2 + teffects + ebalance + coefplot + esttab + asdoc +
Open skill - /00-Full-empirical-analysis-skill_StatsPAI
Use when the user asks to run a full empirical / causal analysis in Python — by default in the style of an applied economics paper (AER / QJE / JPE / ReStud / AEJ) with DID / RD / IV / SCM / DML / matching, written-out estimating equation + identifying assumption, Table 1 /
Open skill - /00.1-Full-empirical-analysis-skill_Python
Classical end-to-end empirical analysis workflow in the traditional Python econometric stack — pandas + numpy + scipy + statsmodels + linearmodels + pyfixest + rdrobust + econml + causalml + matplotlib/seaborn. **Defaults to economics empirical-paper style** (AER / QJE / AEJ) —
Open skill - /00.2-Full-empirical-analysis-skill_Stata
Classical end-to-end empirical analysis workflow in the traditional Stata ecosystem — native Stata + reghdfe + ivreg2 + csdid + did_imputation + eventstudyinteract + sdid + rdrobust + rddensity + synth + synth_runner + psmatch2 + teffects + ebalance + coefplot + esttab + asdoc +
Open skill

