Run arbitrary Stata code or a .do file and display the result.
Scanned 9/3/2026
Install to Claude Code
npx -y skills add brycewang-stanford/Auto-Empirical-Research-Skills --skill stata-run --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Stata Run?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/brycewang-stanford-stata-run)More formats (shields.io, HTML) on the badges page.
---
name: stata-run
description: Run arbitrary Stata code or a .do file and display the result.
---
The argument is the Stata code or absolute path to a `.do` file to execute.
1. If the argument ends in `.do` or `.ado`, call:
```
stata_run(code=<argument>, is_file=True, echo=True, as_json=True)
```
Otherwise call:
```
stata_run(code=<argument>, echo=True, as_json=True)
```
2. If `success` is `true`, display the `stdout` output. Note the output is truncated to 5,000 chars; if the response includes a `log_path`, offer to tail the full log with `/stata-log <log_path>`.
3. If `success` is `false`, display the error message and `rc` code. Suggest using `/stata-lint <path>` for syntax issues or `/stata-help <command>` for documentation.
4. If the command produces graphs, note that `/stata-graph` can export them.
**If using background mode** (`background=True`): you may do other work or fire parallel tasks, but you MUST call `stata_task_status(task_id=<id>, wait=True, timeout=<N>, tail_lines=<M>)` for every task before returning to the user. Set `timeout` to match expected runtime; set `tail_lines` to how much output you want inline vs. reading separately via `stata_read_log`. Loop on timeout until `status` is `'done'` or `'failed'`.
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!