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.
Scanned 9/3/2026
Install to Claude Code
npx -y skills add brycewang-stanford/Auto-Empirical-Research-Skills --skill stata-environment-diagnose --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Stata Environment Diagnose?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/brycewang-stanford-stata-environment-diagnose)More formats (shields.io, HTML) on the badges page.
---
name: stata-environment-diagnose
description: 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.
---
# Environment Diagnose
Use this skill for setup and platform troubleshooting.
1. Verify detection with `stata_manage_session(action="detect")`.
2. Reproduce the smallest failing command.
3. Use logs, package checks, and environment reporting before suggesting a fix.
4. Separate root cause, evidence, remediation, and verification.
Read `references/troubleshooting.md` for the diagnosis flow and use `scripts/report_environment.py` for a deterministic environment summary.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!