agentsclimarketplace
Sign in

Stata setup

Skill brycewang-stanford/Auto-Empirical-Research-Skills/skills/64-tmonk-mcp-stata/skills/stata-setup

Install, configure, update, or verify mcp-stata across Claude Code, Codex, Gemini CLI, Cursor, Windsurf, and VS Code. Activate when users ask to set up the Stata toolkit or troubleshoot the installation.From its SKILL.md

Install
npx -y skills add brycewang-stanford/Auto-Empirical-Research-Skills --skill stata-setup

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.

SKILL.md

2.0 KB, 423 tokens by cl100k_base, as published. Nobody here has run it

Setup and Verification

Use the shared installer and verification flow instead of hand-writing per-agent config unless the user explicitly asks for manual steps.

Preferred Install Commands

Project-shared install:

bash plugin/install.sh --scope project

Personal install:

bash plugin/install.sh --scope user

Specific agent:

bash plugin/install.sh --agent codex

Pin a version if a lab wants to:

bash plugin/install.sh --version 2.5.1

Offline/local source:

bash plugin/install.sh --local-source /path/to/mcp-stata

Live verification:

bash plugin/install.sh --verify

What the Installer Does

  • Uses the canonical server id mcp-stata
  • Writes project-scoped configs where the client supports them
  • Falls back to user-scoped config where project scope is not first-class
  • Installs Codex skills into the Codex skills directory
  • Installs the Gemini extension from plugin/gemini-extension.json
  • Registers shared ~/.agents/skills/mcp-stata symlinks for compatible agents
  • Supports latest-by-default installs and explicit version pinning

Verification Standard

When the user asks whether setup is complete, verify more than “the file exists”:

  1. Stata discovery and edition
  2. uv / uvx availability
  3. package availability for reghdfe and gtools
  4. graph-export readiness
  5. log-path emission for command output
  6. startup/profile behavior

If live verification is not possible on the current machine, state exactly what remains unverified.

Troubleshooting

  • If Stata is not discovered, tell the user to set STATA_PATH.
  • If a user-managed machine blocks temp files, logs, or graph export, use the stata-environment-diagnose skill.
  • If project-wide configs are undesirable, re-run with --scope user.

What ships with it: 2 files

890 B alongside SKILL.md

agents/

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.