/newproject
Scaffold a new research project with standard directory structure, CLAUDE.md template, and documented README. Use this at the start of every new project to ensure consistent organization.
$ npx -y skills add brycewang-stanford/Auto-Empirical-Research-Skills --skill newproject --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
/newproject
Context preview
The summary Claude sees to decide when to auto-load this skill.
Scaffold a new research project with standard directory structure, CLAUDE.md template, and documented README. Use this at the start of every new project to ensure consistent organization.
SKILL.md
newproject.SKILL.mdname: newproject
description: Scaffold a new research project with standard directory structure, CLAUDE.md template, and documented README. Use this at the start of every new project to ensure consistent organization.
allowed-tools: Bash(mkdir*), Bash(cp*), Bash(ls*), Write, Read
argument-hint: "[project-name]"
New Project Scaffold
Create a new research project folder with Scott's standard structure. This skill is invoked at the start of every project.
What Gets Created
[project-name]/
├── CLAUDE.md # Permanent research rules (copied from template)
├── README.md # Project-specific overview (auto-generated)
├── code/
│ ├── R/
│ ├── python/
│ └── stata/
├── data/
│ ├── raw/ # Original source data (never modify)
│ └── clean/ # Cleaned/merged datasets
├── output/
│ ├── tables/
│ └── figures/
├── documents/ # Outside PDFs, papers (use /split-pdf on these)
├── decks/ # Beamer presentations (rhetoric of decks)
├── notes/ # Scratch notes, random ideas, misc
└── progress_logs/ # Session continuity across Claude conversations
Execution
1. **Get the project name** from the argument. If none provided, ask.
- Convert spaces to hyphens, lowercase
2. **Determine location** — default is current working directory. Confirm if unclear.
3. **Create all directories:**
mkdir -p [project-name]/{code/{R,stata,python},data/{raw,clean},output/{figures,tables},documents,decks,notes,progress_logs}4. **Copy CLAUDE.md** from `~/mixtapetools/claude/CLAUDE.md`:
- Replace `[Your Name]` with `Scott`
- Update project name in the overview section
5. **Generate README.md** with:
- Project title
- Visual directory tree in a fenced code block (monospace)
- Explanation of each folder's purpose
- Note that CLAUDE.md is copied from a permanent template and edited per-project
- Note that README.md is for project-specific documentation
- Note that progress_logs/ maintains continuity across Claude sessions
- Placeholder sections: Overview, Collaborators, Status, Key Files
The README must include this tree block:
[project-name]/ ├── CLAUDE.md # Research rules & estimation philosophy (permanent) ├── README.md # This file — project-specific notes ├── code/ │ ├── R/ # R scripts │ ├── python/ # Python scripts │ └── stata/ # Stata do-files ├── data/ │ ├── raw/ # Original source data (never modify these) │ └── clean/ # Cleaned and merged datasets ├── output/ │ ├── tables/ # Generated tables (LaTeX, CSV) │ └── figures/ # Generated figures (PDF, PNG) ├── documents/ # Outside papers and PDFs (split with /split-pdf) ├── decks/ # Beamer presentations (rhetoric of decks philosophy) ├── notes/ # Scratch notes, ideas, miscellaneous └── progress_logs/ # Session logs for continuity across Claude conversations
````
6. **Create initial progress log** at `progress_logs/YYYY-MM-DD_setup.md`:
- Record the creation date
- List next steps as a checklist
7. **Report success** — show structure with `ls`, remind user to update CLAUDE.md.
Read more
name: newproject description: Scaffold a new research project with standard directory structure, CLAUDE.md template, and documented README. Use this at the start of every new project to ensure consistent organization. allowed-tools: Bash(mkdir*), Bash(cp*), Bash(ls*), Write, Read argument-hint: "[project-name]"
New Project Scaffold
Create a new research project folder with Scott's standard structure. This skill is invoked at the start of every project.
What Gets Created
[project-name]/ ├── CLAUDE.md # Permanent research rules (copied from template) ├── README.md # Project-specific overview (auto-generated) ├── code/ │ ├── R/ │ ├── python/ │ └── stata/ ├── data/ │ ├── raw/ # Original source data (never modify) │ └── clean/ # Cleaned/merged datasets ├── output/ │ ├── tables/ │ └── figures/ ├── documents/ # Outside PDFs, papers (use /split-pdf on these) ├── decks/ # Beamer presentations (rhetoric of decks) ├── notes/ # Scratch notes, random ideas, misc └── progress_logs/ # Session continuity across Claude conversations
Execution
1. **Get the project name** from the argument. If none provided, ask.
- Convert spaces to hyphens, lowercase
2. **Determine location** — default is current working directory. Confirm if unclear.
3. **Create all directories:**
mkdir -p [project-name]/{code/{R,stata,python},data/{raw,clean},output/{figures,tables},documents,decks,notes,progress_logs}4. **Copy CLAUDE.md** from `~/mixtapetools/claude/CLAUDE.md`:
- Replace `[Your Name]` with `Scott`
- Update project name in the overview section
5. **Generate README.md** with:
- Project title
- Visual directory tree in a fenced code block (monospace)
- Explanation of each folder's purpose
- Note that CLAUDE.md is copied from a permanent template and edited per-project
- Note that README.md is for project-specific documentation
- Note that progress_logs/ maintains continuity across Claude sessions
- Placeholder sections: Overview, Collaborators, Status, Key Files
The README must include this tree block:
[project-name]/ ├── CLAUDE.md # Research rules & estimation philosophy (permanent) ├── README.md # This file — project-specific notes ├── code/ │ ├── R/ # R scripts │ ├── python/ # Python scripts │ └── stata/ # Stata do-files ├── data/ │ ├── raw/ # Original source data (never modify these) │ └── clean/ # Cleaned and merged datasets ├── output/ │ ├── tables/ # Generated tables (LaTeX, CSV) │ └── figures/ # Generated figures (PDF, PNG) ├── documents/ # Outside papers and PDFs (split with /split-pdf) ├── decks/ # Beamer presentations (rhetoric of decks philosophy) ├── notes/ # Scratch notes, ideas, miscellaneous └── progress_logs/ # Session logs for continuity across Claude conversations
```` 6. **Create initial progress log** at `progress_logs/YYYY-MM-DD_setup.md`: - Record the creation date - List next steps as a checklist 7. **Report success** — show structure with `ls`, remind user to update CLAUDE.md.
📌 文档结构(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

