/devils-advocate
Challenge slide design with 5-7 pedagogical questions. Checks ordering, prerequisites, and cognitive load.
$ npx -y skills add brycewang-stanford/Auto-Empirical-Research-Skills --skill devils-advocate --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
/devils-advocate
Context preview
The summary Claude sees to decide when to auto-load this skill.
Challenge slide design with 5-7 pedagogical questions. Checks ordering, prerequisites, and cognitive load.
SKILL.md
devils-advocate.SKILL.mdname: devils-advocate
description: Challenge slide design with 5-7 pedagogical questions. Checks ordering, prerequisites, and cognitive load.
argument-hint: "[Lecture filename]"
allowed-tools: ["Read", "Grep", "Glob"]
Devil's Advocate Review
Critically examine a slide deck and challenge its design with 5-7 specific pedagogical questions.
**Philosophy:** "We arrive at the best possible presentation through active dialogue."
---
Setup
1. **Read the target file** (the lecture being challenged) 2. **Read the knowledge base** in `.claude/rules/` for notation conventions and narrative arc 3. If applicable, **read adjacent lectures** for narrative continuity
---
Challenge Categories
Generate 5-7 challenges from these categories:
1. Ordering Challenges
> "Could students understand this better if we showed X before Y?"
2. Prerequisite Challenges
> "Do students have the background for this notation at this point?"
3. Gap Challenges
> "Should we include an intuitive example before this formal proof?"
4. Alternative Presentation Challenges
> "Here are 2 other ways to visualize/present this concept."
5. Notation Conflict Challenges
> "This symbol conflicts with earlier lecture usage."
6. Cognitive Load Challenges
> "This slide has too many new symbols. Can we split?"
7. Book Vision Challenges
> "If this becomes a book chapter, does this section stand alone?"
---
Output Format
# Devil's Advocate: [Lecture Title]
## Challenges
### Challenge 1: [Category] — [Short title]
**Question:** [The specific pedagogical question]
**Why it matters:** [What could go wrong]
**Suggested resolution:** [Specific action]
**Slides affected:** [Numbers or titles]
**Severity:** [High / Medium / Low]
[Repeat for 5-7 challenges]
## Summary Verdict
**Strengths:** [2-3 things done well]
**Critical changes:** [0-2 changes before teaching]
**Suggested improvements:** [2-3 nice-to-have changes]
---
Principles
- **Be specific:** Reference exact slides and notation
- **Be constructive:** Every challenge has a suggested resolution
- **Be honest:** If the deck is good, say so
- **Prioritize:** Notation conflicts > missed metaphors
- **Think like a student:** Where do they get lost?
Read more
name: devils-advocate description: Challenge slide design with 5-7 pedagogical questions. Checks ordering, prerequisites, and cognitive load. argument-hint: "[Lecture filename]" allowed-tools: ["Read", "Grep", "Glob"]
Devil's Advocate Review
Critically examine a slide deck and challenge its design with 5-7 specific pedagogical questions.
**Philosophy:** "We arrive at the best possible presentation through active dialogue."
---
Setup
1. **Read the target file** (the lecture being challenged) 2. **Read the knowledge base** in `.claude/rules/` for notation conventions and narrative arc 3. If applicable, **read adjacent lectures** for narrative continuity
---
Challenge Categories
Generate 5-7 challenges from these categories:
1. Ordering Challenges
> "Could students understand this better if we showed X before Y?"
2. Prerequisite Challenges
> "Do students have the background for this notation at this point?"
3. Gap Challenges
> "Should we include an intuitive example before this formal proof?"
4. Alternative Presentation Challenges
> "Here are 2 other ways to visualize/present this concept."
5. Notation Conflict Challenges
> "This symbol conflicts with earlier lecture usage."
6. Cognitive Load Challenges
> "This slide has too many new symbols. Can we split?"
7. Book Vision Challenges
> "If this becomes a book chapter, does this section stand alone?"
---
Output Format
# Devil's Advocate: [Lecture Title] ## Challenges ### Challenge 1: [Category] — [Short title] **Question:** [The specific pedagogical question] **Why it matters:** [What could go wrong] **Suggested resolution:** [Specific action] **Slides affected:** [Numbers or titles] **Severity:** [High / Medium / Low] [Repeat for 5-7 challenges] ## Summary Verdict **Strengths:** [2-3 things done well] **Critical changes:** [0-2 changes before teaching] **Suggested improvements:** [2-3 nice-to-have changes]
---
Principles
- **Be specific:** Reference exact slides and notation
- **Be constructive:** Every challenge has a suggested resolution
- **Be honest:** If the deck is good, say so
- **Prioritize:** Notation conflicts > missed metaphors
- **Think like a student:** Where do they get lost?
📌 文档结构(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

