monte-carlo-prevent

# Monte Carlo Prevent Skill This skill brings Monte Carlo's data observability context directly into your editor. When you're modifying a dbt model or SQL pipeline, use it to surface table health, lineage, active alerts, and to generate monitors-as-code without leaving Claude Code. > **Monte Carlo tool routing (required):** Always call Monte Carlo MCP tools through this plugin's > bundled server, whose fully-qualified tool names are > `mcp__plugin_mc-agent-toolkit_monte-carlo-mcp__<tool>` (e.g. > `mcp__plugin_mc-agent-toolkit_monte-carlo-mcp__get_alerts`). Bare tool names used in this skill > (`get_alerts`, `search`, `get_table`, …) refer to that bundled server. If the session also has a > separately-configured `monte-carlo-mcp` server, do **not** route to it — it may point at a > different endpoint or credentials. Reference files live next to this skill file. **Use the Read tool** (not MCP resources) to access them: - Full workflow step-by-step instructions: `references/workflows.md` (relative to this file) - MCP parameter details: `references/parameters.md` (relative to this file) - Troubleshooting: `references/TROUBLESHOOTING.md` (relative to this file) ## When to activate this skill **Prevent is the edit-lifecycle skill.** Activate only when the user expresses intent to change a dbt model. Bare file mentions, table-name mentions in passing, or general health questions are **not** prevent's territory — those belong to `monte-carlo-asset-health` and will activate that...