Skip to content

SepineTam/mcp-for-stata / plugins/stata-toolbox/skills/stata-skill

stata-skill

Flagged

A packaged Stata Runner skill via official MCP-for-Stata server including stata_do, ado_package_install, help, read_log and get_data_info tools. Use it when (1) need to execute Stata do-file; (2) missing ado-packages; (3) find code error caused by syntax in Stata; (4) want to read smcl and text format log file with rich text output; (5) first encounter a data file and want to understand its structure and content.

examples/graph-export-guidance.md

View on GitHub
# Graph Export Guidance

Read this before writing any code that saves a Stata graph. The default export
path below applies whenever the user has not specified a format.

## Defaults

```stata
* General purpose / slides / quick sharing — high-resolution PNG:
graph export "output/figures/wage_by_educ.png", width(2000) replace

* Paper (LaTeX manuscript) — vector PDF:
graph export "output/figures/wage_by_educ.pdf", replace
```

- **PNG** is the default. Always pass `width(2000)` — Stata's default pixel
  size is too small for documents — and `replace`.
- **PDF** only when the target is a LaTeX paper (vector, scales cleanly).
  `width()` does not apply to PDF.
- Never export both formats unless asked; pick one per the destination rule.
- Never use `graph save` as the final output — a `.gph` file is an
  intermediate, not a deliverable.

## Naming and Location

- Descriptive lowercase names with underscores: `wage_by_educ.png`,
  `event_study_coefs.pdf` — not `graph1.png`.
- Save into a dedicated output directory (`output/figures/` or the project's
  existing figures folder), never next to raw data.

## Before Exporting

- Give the graph a title and axis titles — an untitled graph is not finished:

```stata
twoway (scatter wage educ) (lfit wage educ), ///
    title("Wage by education") ///
    xtitle("Years of education") ytitle("Annual wage") ///
    legend(off)
graph export "output/figures/wage_by_educ.png", width(2000) replace
```

- If the project uses a scheme (`set scheme ...`), keep it consistent across
  all graphs in the same project. Do not install schemes inside the do-file —
  missing packages go through `ado_package_install`.

## Verification

After the do-file runs, confirm the file exists and is non-empty (Bash
`ls -l` or Glob). A `graph export` that silently failed (no graph in memory,
wrong path) produces no file and no `r()` code in some Stata versions — the
file check is the real verification, not the log alone.
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall