Install any skill in seconds. Free to start, no credit card required.
Get Started Free →brycewang-stanford/stata-lint
Run static analysis on a Stata .do or .ado file and report style and best-practice issues.
Passed 7 of 15 test cases with the skill, and 7 of 15 without it.
and 1 more in the full report
3 fixed8 passed either way10 still failing4 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 3 test cases the skill fixed. Same model, same prompt, with and without the skill.
Can you run the Stata linter on my current script? I want to make sure I am following clean coding practices.
| Checked | Without skill | With skill |
|---|---|---|
| Requests an absolute file path from the user | Missed | Passed |
| Specifies that the path must point to a .do or .ado file | Missed | Passed |
The instructions your model reads when the skill loads.
The argument is the absolute path to a .do or .ado file.
Call stata_inspect_data(action="lint", path=<argument>).
Display the lint results, grouping issues by severity or type:
cd, preserve/restore, #delimit, hardcoded paths, long lines, missing version statementFor each category of issue found, briefly explain the modern alternative (refer to the stata-modernize skill for details).
If the file is clean, confirm: "No issues found in <filename>."
If the path argument is missing, tell the user to provide an absolute path to a .do or .ado file.
test cases passed, vs 7 / 15 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.