Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →brycewang-stanford/stata-run
Run arbitrary Stata code or a .do file and display the result.
Passed 8 of 14 test cases with the skill, and 4 of 14 without it.
and 5 more in the full report
6 fixed7 passed either way10 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 6 test cases the skill fixed. Same model, same prompt, with and without the skill.
A script at `/scripts/plot_hist.do` finishes execution and creates a scatter plot. What command should be mentioned for retrieving the plot?
| Checked | Without skill | With skill |
|---|---|---|
| Mentions that /stata-graph can export the figure. | Missed | Passed |
The instructions your model reads when the skill loads.
The argument is the Stata code or absolute path to a .do file to execute.
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)
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>.
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.
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'.
test cases passed, vs 4 / 14 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.