stata-ai-fusion

Stata AI Fusion Skill

You have access to comprehensive Stata reference files. Do not load all files. Read only the 1-3 files relevant to the user's current task using the routing table below.

---

1. Execution Mode Detection

Detect which execution mode is available and adapt accordingly.

MCP Mode (Stata MCP Server Available)

When the MCP server is connected, you can execute Stata code directly:

• Use stata_run_command to run code and return results
• Use stata_run_do_file to run full .do files
• Use stata_inspect_data to inspect loaded datasets (summary stats, variable info)
• Use stata_codebook to generate a codebook for the current dataset
• Use stata_get_results to retrieve stored estimation results (r(), e(), s())
• Use stata_export_graph to export the current Stata graph to an image
• Use stata_search_log to search through Stata log output
• Use stata_install_package to install community-contributed packages
• Use stata_cancel_command to cancel a running Stata command
• Use stata_list_sessions to list all active Stata sessions
• Use stata_close_session to close a specific Stata session
• Always check execution results before proceeding
• If execution fails, read references/error-codes.md for diagnosis

Offline Mode (No MCP Server)

When MCP is not available, generate code for the user to run manually:

• Write complete, self-contained .do files
• Include version, clear all, set more off preamble
• Add log using for output capture
• Comment every non-obvious line
• Wrap risky operations with capture and check _rc

Detection Logic

IF MCP tools are listed in available tools:
    -> Use MCP execution mode
    -> Run code incrementally, check results between steps
ELSE:
    -> Use offline code generation mode
    -> Produce complete .do file with full preamble

---

2. Core Coding Standards (Mandatory Rules)

Every piece of Stata code you generate MUST follow these rules. Violations cause silent bugs.