monte-carlo-analyze-root-cause
Investigate data incidents and find root causes using Monte Carlo's observability data. Guides the agent through systematic investigation: alert lookup, lineage tracing, ETL checks, query analysis, and data profiling. Activates when a user asks about data issues, incidents, alerts, or...
Profile →npx skills add sickn33/agentic-awesome-skills --skill monte-carlo-analyze-root-cause --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Monte Carlo Root Cause Analysis Skill This skill helps investigate data incidents — freshness delays, volume anomalies, schema changes, field metric drift, and ETL failures — by guiding the agent through a systematic investigation using Monte Carlo's MCP tools. It combines observability metadata with optional direct data querying to find the root cause. > **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: - Investigation playbooks by issue type: `references/<type>-investigation.md` - Data exploration patterns: `references/data-exploration.md` - Intake when no incident ID: `references/intake-no-in
- When to activate this skill
- When NOT to activate this skill
- Prerequisites
- MCP Tools Used
- From Monte Carlo MCP server
- Optional external MCP tools
- Workflow
- Step 1: Understand the problem (intake)
- Step 1.5: Auto-invoke TSA (when applicable)
- Step 2: Map the blast radius
- Step 3: Investigate based on issue type
- Step 4: Check for upstream causes
- Step 5: Profile data (if database MCP is available)
- Step 6: Check for code changes
What does the monte-carlo-analyze-root-cause skill do?
Investigate data incidents and find root causes using Monte Carlo's observability data. Guides the agent through systematic investigation: alert lookup, lineage tracing, ETL checks, query analysis, and data profiling. Activates when a user asks about data issues, incidents, alerts, or...
How do I install it?
Run `npx skills add sickn33/agentic-awesome-skills --skill monte-carlo-analyze-root-cause --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From sickn33/agentic-awesome-skills, a repository with 44,414 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.