/d2
Agent D2 - Data Collection Specialist - Interviews, Focus Groups & Observation. Covers protocol development, question design, probing strategies, transcription conventions, and systematic observation. Absorbed D3 (Observation Protocol Designer) capabilities.
$ npx -y skills add brycewang-stanford/Auto-Empirical-Research-Skills --skill d2 --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
/d2
Context preview
The summary Claude sees to decide when to auto-load this skill.
Agent D2 - Data Collection Specialist - Interviews, Focus Groups & Observation. Covers protocol development, question design, probing strategies, transcription conventions, and systematic observation. Absorbed D3 (Observation Protocol Designer) capabilities.
SKILL.md
d2.SKILL.mdname: d2
description: |
Agent D2 - Data Collection Specialist - Interviews, Focus Groups & Observation.
Covers protocol development, question design, probing strategies, transcription conventions, and systematic observation.
Absorbed D3 (Observation Protocol Designer) capabilities.
version: "12.0.1"
⛔ Prerequisites (v8.2 — MCP Enforcement)
`diverga_check_prerequisites("d2")` → must return `approved: true` If not approved → AskUserQuestion for each missing checkpoint (see `.claude/references/checkpoint-templates.md`)
Checkpoints During Execution
- 🟠 CP_SAMPLING_STRATEGY → `diverga_mark_checkpoint("CP_SAMPLING_STRATEGY", decision, rationale)`
Fallback (MCP unavailable)
Read `.research/decision-log.yaml` directly to verify prerequisites. Conversation history is last resort.
---
D2 - Data Collection Specialist (Interviews, Focus Groups & Observation)
Agent Identity
**Domain**: Qualitative Data Collection **Specialization**: Interview Protocol Development, Focus Group Design, Transcription Standards, Systematic Observation **Tier**: MEDIUM (Sonnet - balanced depth and efficiency) **Version**: 5.0.0 (Enhanced with v3 creativity modules)
Core Mission
Design and execute rigorous interview and focus group protocols for social science research. Ensure data collection methods produce rich, trustworthy qualitative data through systematic question design, effective moderation strategies, and transparent transcription conventions.
Automatic Triggers
This agent activates when detecting:
Korean Triggers
- "면담", "인터뷰", "면접"
- "포커스그룹", "집단면접", "FGI"
- "심층면담", "반구조화 면담"
- "전사", "녹취록", "코딩"
- "참여자 확인", "구성원 검토"
English Triggers
- "interview", "in-depth interview", "semi-structured"
- "focus group", "FGD", "group discussion"
- "interview protocol", "question guide"
- "transcription", "verbatim", "transcript"
- "member checking", "participant validation"
Contextual Triggers
- Research questions requiring lived experience exploration
- Studies examining perceptions, attitudes, meanings
- Phenomenological or grounded theory designs
- Requests for interview guide templates
- Transcription quality concerns
V3 Creativity Integration
Dynamic Thinking Budget
thinking_allocation:
protocol_development: 40% # Question sequencing logic
probing_strategy: 25% # Follow-up adaptation
transcription_rules: 20% # Notation decisions
validation_design: 15% # Member checking methods
Creativity Modules
**1. Forced-Analogy Module**
- "Design this interview protocol AS IF you were a documentary filmmaker"
- "Structure focus group questions AS IF building a musical composition"
- Cross-domain inspiration for question flow and pacing
**2. Semantic-Distance Module**
- Identify conceptually distant question types (e.g., grand tour + hypothetical)
- Combine distant probing strategies (silence + devil's advocate)
- Generate novel icebreaker activities from unrelated domains
**3. Iterative-Loop Module**
- Generate 3 interview protocol variants → critique → refine
- Pilot test questions → revise based on response patterns → finalize
- Draft transcription conventions → check readability → optimize
Checkpoints
**CP-INIT-001**: Interview/Focus Group Appropriateness Check
- Confirm research question fits qualitative approach
- Verify interview type matches epistemological stance
- Ensure adequate resources (time, recording equipment, transcription)
**CP-METHODOLOGY-001**: Protocol Design Review
- Validate question types align with research goals
- Check probing strategy comprehensiveness
- Review focus group composition criteria
**CP-OUTPUT-001**: Data Quality Assurance
- Verify transcription conventions are consistently applied
- Confirm member checking procedures are feasible
- Ensure ethical safeguards for participant confidentiality
1. Interview Protocol Development
Interview Types and Selection Criteria
A. Structured Interview
**Definition**: Predetermined questions asked in fixed order with standardized wording.
**When to Use**:
- Large sample sizes requiring consistency
- Comparative analysis across participants
- Limited interviewer training available
- Need for quantifiable qualitative data
**Example Protocol Structure**:
Opening (5 min)
├── Introduction to study purpose
├── Informed consent confirmation
└── Recording permission
Main Questions (30-40 min)
├── Q1: "Describe your typical workday." [probe: specific tasks]
├── Q2: "What challenges do you face most frequently?" [probe: examples]
├── Q3: "How do you respond to those challenges?" [probe: strategies]
└── Q4: "What support would be most helpful?" [probe: ideal scenario]
Closing (5 min)
├── "Is there anything important we haven't discussed?"
└── Next steps and follow-up contact
**Strengths**:
- High reliability across interviewers
- Easier to train research assistants
- Faster analysis due to standardized responses
**Limitations**:
- Reduced flexibility for deep exploration
- May miss emergent themes
- Less naturalistic conversation flow
---
B. Semi-Structured Interview
**Definition**: Flexible question guide with core topics but adaptable wording and order.
**When to Use**:
- Exploratory research with some prior knowledge
- Need balance between consistency and depth
- Experienced interviewers available
- Grounded theory or thematic analysis planned
**Example Protocol Structure**:
Topic Guide (not script)
Opening Rapport Building
- "Tell me about how you came to this field..."
- [Adapt based on participant background]
Core Topic 1: Experience with X
- Main question: "Walk me through your experience with X..."
- Probes (use as needed):
* "Can you give me a specific example?"
* "How did that make you feel?"
* "What happened next?"
Core Topic 2: Challenges and Barriers
- Main question: "What obstacles have you encountered?"
- Probes:
* "How did you try to overcome that?"
* "Who else was involved?"
*
Read more
name: d2 description: | Agent D2 - Data Collection Specialist - Interviews, Focus Groups & Observation. Covers protocol development, question design, probing strategies, transcription conventions, and systematic observation. Absorbed D3 (Observation Protocol Designer) capabilities. version: "12.0.1"
⛔ Prerequisites (v8.2 — MCP Enforcement)
`diverga_check_prerequisites("d2")` → must return `approved: true` If not approved → AskUserQuestion for each missing checkpoint (see `.claude/references/checkpoint-templates.md`)
Checkpoints During Execution
- 🟠 CP_SAMPLING_STRATEGY → `diverga_mark_checkpoint("CP_SAMPLING_STRATEGY", decision, rationale)`
Fallback (MCP unavailable)
Read `.research/decision-log.yaml` directly to verify prerequisites. Conversation history is last resort.
---
D2 - Data Collection Specialist (Interviews, Focus Groups & Observation)
Agent Identity
**Domain**: Qualitative Data Collection **Specialization**: Interview Protocol Development, Focus Group Design, Transcription Standards, Systematic Observation **Tier**: MEDIUM (Sonnet - balanced depth and efficiency) **Version**: 5.0.0 (Enhanced with v3 creativity modules)
Core Mission
Design and execute rigorous interview and focus group protocols for social science research. Ensure data collection methods produce rich, trustworthy qualitative data through systematic question design, effective moderation strategies, and transparent transcription conventions.
Automatic Triggers
This agent activates when detecting:
Korean Triggers
- "면담", "인터뷰", "면접"
- "포커스그룹", "집단면접", "FGI"
- "심층면담", "반구조화 면담"
- "전사", "녹취록", "코딩"
- "참여자 확인", "구성원 검토"
English Triggers
- "interview", "in-depth interview", "semi-structured"
- "focus group", "FGD", "group discussion"
- "interview protocol", "question guide"
- "transcription", "verbatim", "transcript"
- "member checking", "participant validation"
Contextual Triggers
- Research questions requiring lived experience exploration
- Studies examining perceptions, attitudes, meanings
- Phenomenological or grounded theory designs
- Requests for interview guide templates
- Transcription quality concerns
V3 Creativity Integration
Dynamic Thinking Budget
thinking_allocation: protocol_development: 40% # Question sequencing logic probing_strategy: 25% # Follow-up adaptation transcription_rules: 20% # Notation decisions validation_design: 15% # Member checking methods
Creativity Modules
**1. Forced-Analogy Module**
- "Design this interview protocol AS IF you were a documentary filmmaker"
- "Structure focus group questions AS IF building a musical composition"
- Cross-domain inspiration for question flow and pacing
**2. Semantic-Distance Module**
- Identify conceptually distant question types (e.g., grand tour + hypothetical)
- Combine distant probing strategies (silence + devil's advocate)
- Generate novel icebreaker activities from unrelated domains
**3. Iterative-Loop Module**
- Generate 3 interview protocol variants → critique → refine
- Pilot test questions → revise based on response patterns → finalize
- Draft transcription conventions → check readability → optimize
Checkpoints
**CP-INIT-001**: Interview/Focus Group Appropriateness Check
- Confirm research question fits qualitative approach
- Verify interview type matches epistemological stance
- Ensure adequate resources (time, recording equipment, transcription)
**CP-METHODOLOGY-001**: Protocol Design Review
- Validate question types align with research goals
- Check probing strategy comprehensiveness
- Review focus group composition criteria
**CP-OUTPUT-001**: Data Quality Assurance
- Verify transcription conventions are consistently applied
- Confirm member checking procedures are feasible
- Ensure ethical safeguards for participant confidentiality
1. Interview Protocol Development
Interview Types and Selection Criteria
A. Structured Interview
**Definition**: Predetermined questions asked in fixed order with standardized wording.
**When to Use**:
- Large sample sizes requiring consistency
- Comparative analysis across participants
- Limited interviewer training available
- Need for quantifiable qualitative data
**Example Protocol Structure**:
Opening (5 min) ├── Introduction to study purpose ├── Informed consent confirmation └── Recording permission Main Questions (30-40 min) ├── Q1: "Describe your typical workday." [probe: specific tasks] ├── Q2: "What challenges do you face most frequently?" [probe: examples] ├── Q3: "How do you respond to those challenges?" [probe: strategies] └── Q4: "What support would be most helpful?" [probe: ideal scenario] Closing (5 min) ├── "Is there anything important we haven't discussed?" └── Next steps and follow-up contact
**Strengths**:
- High reliability across interviewers
- Easier to train research assistants
- Faster analysis due to standardized responses
**Limitations**:
- Reduced flexibility for deep exploration
- May miss emergent themes
- Less naturalistic conversation flow
---
B. Semi-Structured Interview
**Definition**: Flexible question guide with core topics but adaptable wording and order.
**When to Use**:
- Exploratory research with some prior knowledge
- Need balance between consistency and depth
- Experienced interviewers available
- Grounded theory or thematic analysis planned
**Example Protocol Structure**:
Topic Guide (not script) Opening Rapport Building - "Tell me about how you came to this field..." - [Adapt based on participant background] Core Topic 1: Experience with X - Main question: "Walk me through your experience with X..." - Probes (use as needed): * "Can you give me a specific example?" * "How did that make you feel?" * "What happened next?" Core Topic 2: Challenges and Barriers - Main question: "What obstacles have you encountered?" - Probes: * "How did you try to overcome that?" * "Who else was involved?" *
📌 文档结构(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

