pipeline
Classical end-to-end empirical analysis workflow in the traditional Python econometric stack — pandas + numpy + scipy + statsmodels + linearmodels + pyfixest +…
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.
/devils-advocateContext 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.
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"]
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."
---
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
---
Generate 5-7 challenges from these categories:
> "Could students understand this better if we showed X before Y?"
> "Do students have the background for this notation at this point?"
> "Should we include an intuitive example before this formal proof?"
> "Here are 2 other ways to visualize/present this concept."
> "This symbol conflicts with earlier lecture usage."
> "This slide has too many new symbols. Can we split?"
> "If this becomes a book chapter, does this section stand alone?"
---
# 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]
---
📌 文档结构(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 |
Classical end-to-end empirical analysis workflow in the traditional Python econometric stack — pandas + numpy + scipy + statsmodels + linearmodels + pyfixest +…
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 /…
Classical end-to-end empirical analysis workflow in the traditional Python econometric stack — pandas + numpy + scipy + statsmodels + linearmodels + pyfixest +…
Classical end-to-end empirical analysis workflow in the traditional Stata ecosystem — native Stata + reghdfe + ivreg2 + csdid + did_imputation +…
Classical end-to-end empirical analysis workflow in the modern tidyverse + econometrics R ecosystem — dplyr + tidyr + haven + fixest + sandwich + lmtest +…
Systematic writing framework for philosophy and interdisciplinary academic papers from optimized outline to submission-ready manuscript. Use when users want…