Convert an empirical design into a Stata execution plan or optional do-file skeleton covering merge, variable construction, regressions, robustness, and exports
Scanned 9/7/2026
Install to Claude Code
Skills Directorynpx -y skills add Lambenthan/empiricalwiki --skill stata-plan --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Stata Plan?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/lambenthan-stata-plan-empiricalwiki)More formats (shields.io, HTML) on the badges page.
---
description: Convert an empirical design into a Stata execution plan or optional do-file skeleton covering merge, variable construction, regressions, robustness, and exports
argument-hint: "<empirical-design-path-or-topic> [--write-do]"
---
# /stata-plan
Read the selected empirical design, `wiki/variables/*.md`, `wiki/datasets/*.md`, `wiki/models/*.md`, robustness and heterogeneity pages, plus local `.do`, `.dta`, `.xlsx`, dictionaries, and READMEs.
By default, create `wiki/outputs/stata-plan-{slug}-{YYYY-MM-DD}.md` with:
1. Input data
2. Merge keys and merge order
3. Sample filters
4. Variable construction
5. Winsorization and missing-value handling
6. Descriptive statistics
7. Correlations
8. Baseline regressions
9. Mechanism tests
10. Heterogeneity tests
11. Robustness checks
12. Table exports
13. Verification checklist
Only when the user passes `--write-do`, also create `wiki/outputs/stata-plan-{slug}-{YYYY-MM-DD}.do`.
Constraints:
- Never overwrite existing user `.do` files.
- Do not invent final variable names; use placeholders and mark `needs confirmation` when names are uncertain.
- Include checks for sample size, merge results, missingness, and variable distributions.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Designs system architecture, component specifications, and technical integration strategy. Use when: designing solutions, system architecture, technology stack, or integration approaches.
Generate a comprehensive VC investment assessment report for a company
Structured persuasion for tech leads, PMs, and founders—not activity logs. Five scenarios (kickoff, status update, wrap-up, investor pitch, solution selling) on one 5-part framework (Hook→Context→Proposal→Evidence→Ask). AI prompts for missing materials and audience context; pre-submit checklist. Claude Code plugin; Cursor, Codex, and chat via prompts.
Manage Globalize translation resources using the CLI. Use this skill when the user asks to create a translation project, add or remove languages, connect a GitHub or GitLab repository, manage glossaries or style guides, invite team members, manage API keys, or perform any Globalize platform operation. Also use when the user mentions managing translations, translation workflow, or wants to "set up translations for this repo." This skill assumes the CLI is already installed and authenticated — ...
Create and maintain agent-authored Paperclip status cards, or compile a prose interest prompt into bounded CompanySearchQuery objects and write the first summary from the assigned Summarizer run.
