| name | stata-research-workbench |
| description | Plan, review, and package Stata empirical research workflows: .do files, data audit, logs, graph export, table building, replication, linting, and referee-response updates. Use when a user works in Stata or asks for .do/.dta research workflows. |
Stata Research Workbench
Source adaptation: BioRouter-original synthesis inspired by Auto-Empirical Research Skills capability clusters, rewritten under Apache-2.0. This is native BioRouter guidance and does not copy upstream text.
When to Use
Use this skill when the user asks about Stata .do/.dta empirical research, logs, tables, graph export, replication, or Stata-specific workflow review. If the task is biomedical, clinical, or omics-specific, combine this with the appropriate BioSkills category and extension instead of treating the methods in isolation.
Intake
Collect:
- Research question, estimand, and audience.
- Dataset/source, file formats, licenses, access constraints, and identifiers.
- Unit of analysis, time period, sample design, and outcome/treatment definitions.
- Software stack and expected artifact: code, table, figure, memo, manuscript, appendix, or review response.
- Whether the work is exploratory, confirmatory, replication, submission, or referee-response.
Method Gates
Before writing conclusions:
- State the design and estimand before the model.
- Preserve provenance for every dataset, variable, citation, and transformation.
- Match inference to the sampling/assignment structure.
- Identify weights, clusters, panels, repeated measures, or dependence before estimating.
- Check robustness against the actual design threat, not decorative alternative models.
- Keep code/table/figure outputs reproducible from a clean entry point.
BioRouter Routing
- Use
empirical-research-router for full workflow staging.
- Use
causal-identification-gates before causal language.
- Use
econometrics-toolkit, statistical-modeling-bayes, or financial-accounting-econometrics for adjacent method detail.
- Use
citation-temporal-integrity, claim-evidence-integrity, and replication-package-audit for publication-facing outputs.
Output Pattern
Return a compact plan with:
- Primary route and why.
- Required data/design evidence.
- Minimal next command or artifact.
- Failure modes.
- Verification checklist before final claims.
