Agent skill · Databases

monte-carlo-prevent

Surfaces Monte Carlo data observability context (table health, alerts, lineage, blast radius) before SQL/dbt edits.

Nick44,086★ · +407/wk · 1 repos on radarProfile →
claude-codecodexcursorMIT
Install
npx skills add sickn33/agentic-awesome-skills --skill monte-carlo-prevent --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 4
SKILL.md size: 13 KB
Bundled scripts: none
Declared author: monte-carlo-data
Path: skills/monte-carlo-prevent/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 44,414 · +328 this week
Language: Python
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# 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. 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 **Do not wait to be asked.** Run the appropriate workflow automatically whenever the user: - References or opens a `.sql` file or dbt model (files in `models/`) → run Workflow 1 - Mentions a table name, dataset, or dbt model name in passing → run Workflow 1 - Describes a planned change to a model (new column, join update, filter change, refactor) → **STOP — run Workflow 4 before writing any code** - - Adds a new column, metric, or output expression to an existing model → run Workflow 4 first, then ALWAYS offer Workflow 2 regardless

What's inside
Steps it walks through
  1. When to activate this skill
  2. When NOT to activate this skill
  3. Macros and snapshots — gate edits, skip auto-context
  4. REQUIRED: Change impact assessment before any SQL edit
  5. Pre-edit gate — check before modifying any file
  6. Available MCP tools
  7. Core workflows
  8. 1. Table health check
  9. 2. Add a monitor
  10. 3. Alert triage
  11. 4. Change impact assessment — REQUIRED before modifying a model
  12. 5. Change validation queries
  13. Post-synthesis confirmation rules
  14. Session markers
Ships with 3 files
  • references/TROUBLESHOOTING.md
  • references/parameters.md
  • references/workflows.md
More from agentic-awesome-skills
All skills →
About this skill
What does the monte-carlo-prevent skill do?

Surfaces Monte Carlo data observability context (table health, alerts, lineage, blast radius) before SQL/dbt edits.

How do I install it?

Run `npx skills add sickn33/agentic-awesome-skills --skill monte-carlo-prevent --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.

Keep going