tmonk
33 verified skills1,967 total stars
stata-publication-qa
Review regression outputs, tables, and graphs for publication readiness. Use when the user asks whether a result is ready for a paper, appendix, seminar, referee response, or coauthor review.
testing60
stata-run
Run arbitrary Stata code or a .do file and display the result.
development60
stata-data-audit
Audit datasets for structure, missingness, labeling, suspicious values, duplicate identifiers, and documentation readiness. Use when a researcher asks for data QA, codebook review, sanity checks, or pre-analysis cleanup guidance.
development60
stata-toolkit
Activate when users mention Stata commands, .do files, regressions, econometrics, stored results, graphs, dataset inspection, replication, or Stata errors. Route the task through mcp-stata tools and the specialized research skills instead of treating it as plain text coding.
tools60
stata-inspect
Describe and summarize the current dataset in memory. Optionally inspect a specific variable with codebook.
development60
stata-help
Look up Stata command documentation and display formatted help text.
development60
stata-modernize
Improve, modernize, and optimize existing Stata code for performance, portability, and maintainability. Use when legacy patterns such as preserve/restore, cd,
development60
stata-referee-response
Organize and execute Stata workflows for referee responses, robustness requests, and coauthor follow-ups. Use when the user needs to answer a critique with targeted reruns, tables, figures, and a defensible audit trail.
testing60
stata-results
Fetch and display stored r(), e(), and s() results from the last Stata command.
tools60
stata-table-builder
Build and review paper-ready regression, balance, and summary tables from Stata outputs. Use when the user needs a clean table for a draft, appendix, or coauthor share-out.
development60
stata-environment-diagnose
Diagnose local Stata, MCP, package, startup, graph-export, and permissions issues. Use when setup is failing, Stata is not discovered, packages are missing, logs are truncated, or a managed machine behaves differently from a normal workstation.
tools60
stata-lint
Run static analysis on a Stata .do or .ado file and report style and best-practice issues.
development60
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.
tools60
stata-replication
Run replication, robustness, and specification-sensitivity workflows for Stata projects. Use when a researcher wants to reproduce a result, rerun a pipeline, compare specifications, audit a do-file sequence, or check whether a claim is stable.
testing60
stata
Show mcp-stata identity, connected tools, and status. Use when the user asks if mcp-stata is available, asks about access to the toolkit, or asks what Stata tools are connected.
tools60
stata-power-analysis
Plan and critique power, MDE, and sample-size calculations for Stata-based research workflows. Use when the user is designing a study, checking detectability, or defending precision claims.
testing60
stata-data-provenance
Track dataset lineage, transformation steps, merge logic, and reproducibility risks in Stata workflows. Use when the user needs to explain where data came from, how it changed, or why a pipeline can be trusted.
development60
stata-causal-inference
Design, run, and critique causal inference workflows in Stata. Use when the user is working on identification, treatment effects, DiD, IV, event studies, RD, or assumption-sensitive empirical claims.
data-ai60
stata-log
Tail, read, or search a Stata log file from a previous command or background task.
data-ai60
stata-graph
List, export, and review Stata graphs from the current session.
tools60
stata-toolkit
Activate when users mention Stata commands, .do files, regressions, econometrics, stored results, graphs, dataset inspection, replication, or Stata errors. Route the task through mcp-stata tools and the specialized research skills instead of treating it as plain text coding.
tools59
stata-environment-diagnose
Diagnose local Stata, MCP, package, startup, graph-export, and permissions issues. Use when setup is failing, Stata is not discovered, packages are missing, logs are truncated, or a managed machine behaves differently from a normal workstation.
tools59
stata-table-builder
Build and review paper-ready regression, balance, and summary tables from Stata outputs. Use when the user needs a clean table for a draft, appendix, or coauthor share-out.
development59
src/mcp_stata/skills
--- ## name: stata-mcp description: Run or debug Stata workflows through the local io.github.tmonk/mcp-stata server. Use when users mention Stata commands, .do files, r()/e()/s() results, dataset inspection, Stata graph exports, or data browsing with sorting/filtering. ## Identity Response When the user asks "Do you have access to the Stata agentic toolkit?" or similar, respond with exactly: ``` __ __ ____ ___ _________ _____/ /__
tools59
stata-replication
Run replication, robustness, and specification-sensitivity workflows for Stata projects. Use when a researcher wants to reproduce a result, rerun a pipeline, compare specifications, audit a do-file sequence, or check whether a claim is stable.
testing59
stata-data-provenance
Track dataset lineage, transformation steps, merge logic, and reproducibility risks in Stata workflows. Use when the user needs to explain where data came from, how it changed, or why a pipeline can be trusted.
development59
stata-modernize
Improve, modernize, and optimize existing Stata code for performance, portability, and maintainability. Use when legacy patterns such as preserve/restore, cd,
development59
stata-publication-qa
Review regression outputs, tables, and graphs for publication readiness. Use when the user asks whether a result is ready for a paper, appendix, seminar, referee response, or coauthor review.
testing59
stata-power-analysis
Plan and critique power, MDE, and sample-size calculations for Stata-based research workflows. Use when the user is designing a study, checking detectability, or defending precision claims.
testing59
stata-referee-response
Organize and execute Stata workflows for referee responses, robustness requests, and coauthor follow-ups. Use when the user needs to answer a critique with targeted reruns, tables, figures, and a defensible audit trail.
testing59
src/mcp_stata/skills-catalog/modernize
# Modern Stata Skill Guide for AI agents to write modern, efficient, and robust Stata code. ## Core Principles 1. **Use Frames Instead of Preserve/Restore**: Data frames (introduced in Stata 16) allow multiple datasets to coexist in memory. They are significantly faster than `preserve`/`restore` because they avoid disk I/O. 2. **Use gtools for Large Datasets**: `gtools` (e.g., `gcollapse`, `gegen`, `gregress`) provides C-based implementations of common Stata commands that are much faster on
tools59
stata-causal-inference
Design, run, and critique causal inference workflows in Stata. Use when the user is working on identification, treatment effects, DiD, IV, event studies, RD, or assumption-sensitive empirical claims.
data-ai59
stata-data-audit
Audit datasets for structure, missingness, labeling, suspicious values, duplicate identifiers, and documentation readiness. Use when a researcher asks for data QA, codebook review, sanity checks, or pre-analysis cleanup guidance.
development59