opencode-skills-collection 2.0.0 → 2.0.3

package/bundled-skills/.antigravity-install-manifest.json

@@ -1,6 +1,6 @@
 {
   "schemaVersion": 1,
-  "updatedAt": "2026-04-09T17:09:01.460Z",
+  "updatedAt": "2026-04-09T19:52:06.364Z",
   "entries": [
     "00-andruia-consultant",
     "007",
@@ -815,6 +815,7 @@
     "makepad-splash",
     "makepad-widgets",
     "malware-analyst",
+    "manage-skills",
     "manifest",
     "market-sizing-analysis",
     "marketing-ideas",
@@ -849,6 +850,10 @@
     "monetization",
     "monorepo-architect",
     "monorepo-management",
+    "monte-carlo-monitor-creation",
+    "monte-carlo-prevent",
+    "monte-carlo-push-ingestion",
+    "monte-carlo-validation-notebook",
     "moodle-external-api-development",
     "moyu",
     "mtls-configuration",

package/bundled-skills/docs/integrations/jetski-cortex.md

@@ -1,9 +1,9 @@
 ---
 title: Jetski/Cortex + Gemini Integration Guide
-description: "Use antigravity-awesome-skills with Jetski/Cortex without hitting context-window overflow with 1.392+ skills."
+description: "Use antigravity-awesome-skills with Jetski/Cortex without hitting context-window overflow with 1.397+ skills."
 ---
 
-# Jetski/Cortex + Gemini: safe integration with 1,1.392+ skills
+# Jetski/Cortex + Gemini: safe integration with 1,1.397+ skills
 
 This guide shows how to integrate the `antigravity-awesome-skills` repository with an agent based on **Jetski/Cortex + Gemini** (or similar frameworks) **without exceeding the model context window**.
 
@@ -23,7 +23,7 @@ Never do:
 - concatenate all `SKILL.md` content into a single system prompt;
 - re-inject the entire library for **every** request.
 
-With over 1,1.392 skills, this approach fills the context window before user messages are even added, causing truncation.
+With over 1,1.397 skills, this approach fills the context window before user messages are even added, causing truncation.
 
 ---
 

package/bundled-skills/docs/integrations/jetski-gemini-loader/README.md

@@ -20,7 +20,7 @@ This example shows one way to integrate **antigravity-awesome-skills** with a Je
 - How to enforce a **maximum number of skills per turn** via `maxSkillsPerTurn`.
 - How to choose whether to **truncate or error** when too many skills are requested via `overflowBehavior`.
 
-This pattern avoids context overflow when you have 1,392+ skills installed.
+This pattern avoids context overflow when you have 1,397+ skills installed.
 
 ---
 

package/bundled-skills/docs/maintainers/repo-growth-seo.md

@@ -6,7 +6,7 @@ This document keeps the repository's GitHub-facing discovery copy aligned with t
 
 Preferred positioning:
 
-> Installable GitHub library of 1,392+ agentic skills for Claude Code, Cursor, Codex CLI, Gemini CLI, Antigravity, and other AI coding assistants.
+> Installable GitHub library of 1,397+ agentic skills for Claude Code, Cursor, Codex CLI, Gemini CLI, Antigravity, and other AI coding assistants.
 
 Key framing:
 
@@ -20,7 +20,7 @@ Key framing:
 
 Preferred description:
 
-> Installable GitHub library of 1,392+ agentic skills for Claude Code, Cursor, Codex CLI, Gemini CLI, Antigravity, and more. Includes installer CLI, bundles, workflows, and official/community skill collections.
+> Installable GitHub library of 1,397+ agentic skills for Claude Code, Cursor, Codex CLI, Gemini CLI, Antigravity, and more. Includes installer CLI, bundles, workflows, and official/community skill collections.
 
 Preferred homepage:
 
@@ -28,7 +28,7 @@ Preferred homepage:
 
 Preferred social preview:
 
-- use a clean preview image that says `1,392+ Agentic Skills`;
+- use a clean preview image that says `1,397+ Agentic Skills`;
 - mention Claude Code, Cursor, Codex CLI, and Gemini CLI;
 - avoid dense text and tiny logos that disappear in social cards.
 

package/bundled-skills/docs/maintainers/skills-update-guide.md

@@ -69,7 +69,7 @@ For manual updates, you need:
 The update process refreshes:
 - Skills index (`skills_index.json`)
 - Web app skills data (`apps\web-app\public\skills.json`)
-- All 1,392+ skills from the skills directory
+- All 1,397+ skills from the skills directory
 
 ## When to Update
 

package/bundled-skills/docs/users/bundles.md

@@ -673,4 +673,4 @@ Found a skill that should be in a bundle? Or want to create a new bundle? [Open
 
 ---
 
-_Last updated: March 2026 | Total Skills: 1,392+ | Total Bundles: 37_
+_Last updated: March 2026 | Total Skills: 1,397+ | Total Bundles: 37_

package/bundled-skills/docs/users/claude-code-skills.md

@@ -12,7 +12,7 @@ Install the library into Claude Code, then invoke focused skills directly in the
 
 ## Why use this repo for Claude Code
 
-- It includes 1,392+ skills instead of a narrow single-domain starter pack.
+- It includes 1,397+ skills instead of a narrow single-domain starter pack.
 - It supports the standard `.claude/skills/` path and the Claude Code plugin marketplace flow.
 - It also ships generated bundle plugins so teams can install focused packs like `Essentials` or `Security Developer` from the marketplace metadata.
 - It includes onboarding docs, bundles, and workflows so new users do not need to guess where to begin.

package/bundled-skills/docs/users/gemini-cli-skills.md

@@ -12,7 +12,7 @@ Install into the Gemini skills path, then ask Gemini to apply one skill at a tim
 
 - It installs directly into the expected Gemini skills path.
 - It includes both core software engineering skills and deeper agent/LLM-oriented skills.
-- It helps new users get started with bundles and workflows rather than forcing a cold start from 1,392+ files.
+- It helps new users get started with bundles and workflows rather than forcing a cold start from 1,397+ files.
 - It is useful whether you want a broad internal skill library or a single repo to test many workflows quickly.
 
 ## Install Gemini CLI Skills

package/bundled-skills/docs/users/getting-started.md

@@ -1,4 +1,4 @@
-# Getting Started with Antigravity Awesome Skills (V9.10.0)
+# Getting Started with Antigravity Awesome Skills (V9.11.0)
 
 **New here? This guide will help you supercharge your AI Agent in 5 minutes.**
 

package/bundled-skills/docs/users/kiro-integration.md

@@ -18,7 +18,7 @@ Kiro is AWS's agentic AI IDE that combines:
 
 Kiro's agentic capabilities are enhanced by skills that provide:
 
-- **Domain expertise** across 1,392+ specialized areas
+- **Domain expertise** across 1,397+ specialized areas
 - **Best practices** from Anthropic, OpenAI, Google, Microsoft, and AWS
 - **Workflow automation** for common development tasks
 - **AWS-specific patterns** for serverless, infrastructure, and cloud architecture

package/bundled-skills/docs/users/usage.md

@@ -14,7 +14,7 @@ If you came in through a **Claude Code** or **Codex** plugin instead of a full l
 
 When you ran `npx antigravity-awesome-skills` or cloned the repository, you:
 
-✅ **Downloaded 1,392+ skill files** to your computer (default: `~/.gemini/antigravity/skills/`; or a custom path like `~/.agent/skills/` if you used `--path`)  
+✅ **Downloaded 1,397+ skill files** to your computer (default: `~/.gemini/antigravity/skills/`; or a custom path like `~/.agent/skills/` if you used `--path`)  
 ✅ **Made them available** to your AI assistant  
 ❌ **Did NOT enable them all automatically** (they're just sitting there, waiting)
 
@@ -34,7 +34,7 @@ Bundles are **curated groups** of skills organized by role. They help you decide
 
 **Analogy:**
 
-- You installed a toolbox with 1,392+ tools (✅ done)
+- You installed a toolbox with 1,397+ tools (✅ done)
 - Bundles are like **labeled organizer trays** saying: "If you're a carpenter, start with these 10 tools"
 - You can either **pick skills from the tray** or install that tray as a focused marketplace bundle plugin
 
@@ -212,7 +212,7 @@ Let's actually use a skill right now. Follow these steps:
 
 ## Step 5: Picking Your First Skills (Practical Advice)
 
-Don't try to use all 1,392+ skills at once. Here's a sensible approach:
+Don't try to use all 1,397+ skills at once. Here's a sensible approach:
 
 If you want a tool-specific starting point before choosing skills, use:
 
@@ -343,7 +343,7 @@ Usually no, but if your AI doesn't recognize a skill:
 
 ### "Can I load all skills into the model at once?"
 
-No. Even though you have 1,392+ skills installed locally, you should **not** concatenate every `SKILL.md` into a single system prompt or context block.
+No. Even though you have 1,397+ skills installed locally, you should **not** concatenate every `SKILL.md` into a single system prompt or context block.
 
 The intended pattern is:
 

package/bundled-skills/docs/users/visual-guide.md

@@ -34,7 +34,7 @@ antigravity-awesome-skills/
 ├── 📄 CONTRIBUTING.md                  ← Contributor workflow
 ├── 📄 CATALOG.md                       ← Full generated catalog
 │
-├── 📁 skills/                          ← 1,392+ skills live here
+├── 📁 skills/                          ← 1,397+ skills live here
 │   │
 │   ├── 📁 brainstorming/
 │   │   └── 📄 SKILL.md                 ← Skill definition
@@ -47,7 +47,7 @@ antigravity-awesome-skills/
 │   │   └── 📁 2d-games/
 │   │       └── 📄 SKILL.md             ← Nested skills also supported
 │   │
-│   └── ... (1,392+ total)
+│   └── ... (1,397+ total)
 │
 ├── 📁 apps/
 │   └── 📁 web-app/                     ← Interactive browser
@@ -100,7 +100,7 @@ antigravity-awesome-skills/
 
 ```
                     ┌─────────────────────────┐
-                    │  1,392+ SKILLS          │
+                    │  1,397+ SKILLS          │
                     └────────────┬────────────┘
                                  │
         ┌────────────────────────┼────────────────────────┐
@@ -201,7 +201,7 @@ If you want a workspace-style manual install instead, cloning into `.agent/skill
 │   ├── 📁 brainstorming/                 │
 │   ├── 📁 stripe-integration/            │
 │   ├── 📁 react-best-practices/          │
-│   └── ... (1,392+ total)                │
+│   └── ... (1,397+ total)                │
 └─────────────────────────────────────────┘
 ```
 

package/bundled-skills/manage-skills/SKILL.md

@@ -0,0 +1,187 @@
+---
+name: manage-skills
+description: Discover, list, create, edit, toggle, copy, move, and delete AI agent skills across 11 tools (Cursor, Claude, Agents, Windsurf, Copilot, Codex, Cline, Aider, Continue, Roo Code, Augment)
+---
+
+# Manage AI Agent Skills
+
+You can manage skills and rules for all major AI coding tools directly from the terminal. This skill teaches you the directory layout, file format, and operations for each tool.
+
+## Supported Tools & Paths
+
+### Directory-based tools (multiple skills)
+
+Each skill lives in its own subdirectory with a `SKILL.md` file containing YAML frontmatter.
+
+| Tool | Global Path | Project Path |
+|------|------------|--------------|
+| Agents | `~/.agents/skills/<name>/SKILL.md` | `.agents/skills/<name>/SKILL.md` |
+| Cursor | `~/.cursor/skills/<name>/SKILL.md` | `.cursor/skills/<name>/SKILL.md` |
+| Claude | `~/.claude/skills/<name>/SKILL.md` | `.claude/skills/<name>/SKILL.md` |
+| Windsurf | `~/.windsurf/rules/<name>/<name>.md` | `.windsurf/rules/<name>/<name>.md` |
+| Cline | `~/.cline/rules/<name>/<name>.md` | `.cline/rules/<name>/<name>.md` |
+| Continue | `~/.continue/rules/<name>/<name>.md` | `.continue/rules/<name>/<name>.md` |
+| Roo Code | `~/.roo/rules/<name>/<name>.md` | `.roo/rules/<name>/<name>.md` |
+
+### Single-file tools (one config file)
+
+| Tool | Global Path | Project Path |
+|------|------------|--------------|
+| Copilot | `~/.github/copilot-instructions.md` | `.github/copilot-instructions.md` |
+| Codex | `~/.codex/AGENTS.md` | `.codex/AGENTS.md` |
+| Aider | `~/.aider.conf.yml` | `.aider.conf.yml` |
+| Augment | `~/augment-guidelines.md` | `augment-guidelines.md` |
+
+### Cursor plugins (read-only)
+
+Plugin skills are cached at `~/.cursor/plugins/cache/<org>/<plugin>/<version>/skills/<name>/SKILL.md`. These are managed by Cursor and should not be edited directly.
+
+## Skill File Format
+
+For directory-based tools (Agents, Cursor, Claude), skills use YAML frontmatter:
+
+```markdown
+---
+name: skill-name
+description: Brief description of what this skill does
+---
+
+# Skill Name
+
+Skill instructions go here. The AI agent reads this content
+when the skill is activated.
+```
+
+For Windsurf, Cline, Continue, and Roo Code, skills are plain `.md` files (frontmatter optional).
+
+## Operations
+
+### List all skills
+
+```bash
+# List skills for a specific tool
+ls ~/.agents/skills/
+ls ~/.cursor/skills/
+ls ~/.claude/skills/
+ls ~/.windsurf/rules/
+ls ~/.cline/rules/
+ls ~/.continue/rules/
+ls ~/.roo/rules/
+
+# Count total skills across all tools
+echo "Agents: $(ls ~/.agents/skills/ 2>/dev/null | wc -l | tr -d ' ')"
+echo "Cursor: $(ls ~/.cursor/skills/ 2>/dev/null | wc -l | tr -d ' ')"
+echo "Claude: $(ls ~/.claude/skills/ 2>/dev/null | wc -l | tr -d ' ')"
+echo "Windsurf: $(ls ~/.windsurf/rules/ 2>/dev/null | wc -l | tr -d ' ')"
+echo "Cline: $(ls ~/.cline/rules/ 2>/dev/null | wc -l | tr -d ' ')"
+echo "Continue: $(ls ~/.continue/rules/ 2>/dev/null | wc -l | tr -d ' ')"
+echo "Roo: $(ls ~/.roo/rules/ 2>/dev/null | wc -l | tr -d ' ')"
+
+# Check single-file tools
+test -f ~/.github/copilot-instructions.md && echo "Copilot: exists" || echo "Copilot: not found"
+test -f ~/.codex/AGENTS.md && echo "Codex: exists" || echo "Codex: not found"
+test -f ~/.aider.conf.yml && echo "Aider: exists" || echo "Aider: not found"
+test -f ~/augment-guidelines.md && echo "Augment: exists" || echo "Augment: not found"
+```
+
+### Read a skill
+
+```bash
+cat ~/.cursor/skills/my-skill/SKILL.md
+```
+
+### Create a new skill
+
+```bash
+# For Agents/Cursor/Claude (SKILL.md format)
+mkdir -p ~/.agents/skills/my-new-skill
+cat > ~/.agents/skills/my-new-skill/SKILL.md << 'EOF'
+---
+name: my-new-skill
+description: What this skill does
+---
+
+# My New Skill
+
+Instructions for the agent go here.
+EOF
+
+# For Windsurf/Cline/Continue/Roo (plain .md format)
+mkdir -p ~/.windsurf/rules/my-new-rule
+cat > ~/.windsurf/rules/my-new-rule/my-new-rule.md << 'EOF'
+# My New Rule
+
+Instructions go here.
+EOF
+
+# For single-file tools
+cat > .github/copilot-instructions.md << 'EOF'
+Instructions for Copilot go here.
+EOF
+```
+
+### Enable / Disable a skill
+
+Disabling renames the file to `.disabled` so the tool ignores it but the content is preserved:
+
+```bash
+# Disable
+mv ~/.cursor/skills/my-skill/SKILL.md ~/.cursor/skills/my-skill/SKILL.md.disabled
+
+# Enable
+mv ~/.cursor/skills/my-skill/SKILL.md.disabled ~/.cursor/skills/my-skill/SKILL.md
+```
+
+### Copy a skill between tools
+
+```bash
+# Copy from Cursor to Claude
+cp -r ~/.cursor/skills/my-skill ~/.claude/skills/my-skill
+
+# Copy from Agents to Windsurf (adapt format)
+mkdir -p ~/.windsurf/rules/my-skill
+cp ~/.agents/skills/my-skill/SKILL.md ~/.windsurf/rules/my-skill/my-skill.md
+```
+
+### Move a skill
+
+```bash
+mv ~/.cursor/skills/my-skill ~/.agents/skills/my-skill
+```
+
+### Delete a skill
+
+```bash
+rm -rf ~/.cursor/skills/my-skill
+```
+
+### Copy a skill from global to project scope
+
+```bash
+cp -r ~/.cursor/skills/my-skill .cursor/skills/my-skill
+```
+
+### Search across all skills
+
+```bash
+# Search by name
+find ~/.agents/skills ~/.cursor/skills ~/.claude/skills ~/.windsurf/rules ~/.cline/rules ~/.continue/rules ~/.roo/rules -maxdepth 1 -type d 2>/dev/null | sort
+
+# Search by content
+grep -rl "search term" ~/.agents/skills/ ~/.cursor/skills/ ~/.claude/skills/ 2>/dev/null
+```
+
+### Find disabled skills
+
+```bash
+find ~/.agents/skills ~/.cursor/skills ~/.claude/skills -name "*.disabled" 2>/dev/null
+```
+
+## Guidelines
+
+- When the user asks to "manage skills", "list my skills", "create a skill", "copy a skill to X", or similar, use the paths and formats above.
+- Always confirm before deleting skills.
+- When copying between tools with different formats (e.g., Cursor SKILL.md to Windsurf plain .md), adapt the file naming accordingly.
+- Project-scoped skills override global skills of the same name.
+- For single-file tools (Copilot, Codex, Aider, Augment), editing means replacing the entire file content.
+- When creating skills, use kebab-case for directory names (e.g., `my-new-skill`).

package/bundled-skills/monte-carlo-monitor-creation/SKILL.md

@@ -0,0 +1,222 @@
+---
+name: monte-carlo-monitor-creation
+description: "Guides creation of Monte Carlo monitors via MCP tools, producing monitors-as-code YAML for CI/CD deployment."
+category: data
+risk: safe
+source: community
+source_repo: monte-carlo-data/mc-agent-toolkit
+source_type: community
+date_added: "2026-04-08"
+author: monte-carlo-data
+tags: [data-observability, monitoring, monte-carlo, monitors-as-code]
+tools: [claude, cursor, codex]
+---
+
+# Monte Carlo Monitor Creation Skill
+
+This skill teaches you to create Monte Carlo monitors correctly via MCP. Every creation tool runs in **dry-run mode** and returns monitors-as-code (MaC) YAML. No monitors are created directly -- the user applies the YAML via the Monte Carlo CLI or CI/CD.
+
+Reference files live next to this skill file. **Use the Read tool** (not MCP resources) to access them:
+
+- Metric monitor details: `references/metric-monitor.md` (relative to this file)
+- Validation monitor details: `references/validation-monitor.md` (relative to this file)
+- Custom SQL monitor details: `references/custom-sql-monitor.md` (relative to this file)
+- Comparison monitor details: `references/comparison-monitor.md` (relative to this file)
+- Table monitor details: `references/table-monitor.md` (relative to this file)
+
+## When to activate this skill
+
+Activate when the user:
+
+- Asks to create, add, or set up a monitor (e.g. "add a monitor for...", "create a freshness check on...", "set up validation for...")
+- Mentions monitoring a specific table, field, or metric
+- Wants to check data quality rules or enforce data contracts
+- Asks about monitoring options for a table or dataset
+- Requests monitors-as-code YAML generation
+- Wants to add monitoring after new transformation logic (when the prevent skill is not active)
+
+## When NOT to activate this skill
+
+Do not activate when the user is:
+
+- Just querying data or exploring table contents
+- Triaging or responding to active alerts (use the prevent skill's Workflow 3)
+- Running impact assessments before code changes (use the prevent skill's Workflow 4)
+- Asking about existing monitor configuration (use `getMonitors` directly)
+- Editing or deleting existing monitors
+
+---
+
+## Available MCP tools
+
+All tools are available via the `monte-carlo` MCP server.
+
+| Tool                         | Purpose                                                    |
+| ---------------------------- | ---------------------------------------------------------- |
+| `testConnection`             | Verify auth and connectivity before starting               |
+| `search`                     | Find tables/assets by name; use `include_fields` for columns |
+| `getTable`                   | Schema, stats, metadata, domain membership, capabilities   |
+| `getValidationPredicates`    | List available validation rule types for a warehouse       |
+| `getDomains`                 | List MC domains (only needed if table has no domain info)  |
+| `createMetricMonitorMac`     | Generate metric monitor YAML (dry-run)                     |
+| `createValidationMonitorMac` | Generate validation monitor YAML (dry-run)                 |
+| `createComparisonMonitorMac` | Generate comparison monitor YAML (dry-run)                 |
+| `createCustomSqlMonitorMac`  | Generate custom SQL monitor YAML (dry-run)                 |
+| `createTableMonitorMac`      | Generate table monitor YAML (dry-run)                      |
+
+---
+
+## Monitor types
+
+| Type           | Tool                         | Use When                                                                                                                                |
+| -------------- | ---------------------------- | --------------------------------------------------------------------------------------------------------------------------------------- |
+| **Metric**     | `createMetricMonitorMac`     | Track statistical metrics on fields (null rates, unique counts, numeric stats) or row count changes over time. Requires a timestamp field for aggregation. |
+| **Validation** | `createValidationMonitorMac` | Row-level data quality checks with conditions (e.g. "field X is never null", "status is in allowed set"). Alerts on INVALID data.       |
+| **Custom SQL** | `createCustomSqlMonitorMac`  | Run arbitrary SQL returning a single number and alert on thresholds. Most flexible; use when other types don't fit.                     |
+| **Comparison** | `createComparisonMonitorMac` | Compare metrics between two tables (e.g. dev vs prod, source vs target).                                                               |
+| **Table**      | `createTableMonitorMac`      | Monitor groups of tables for freshness, schema changes, and volume. Uses asset selection at database/schema level.                      |
+
+---
+
+## Procedure
+
+Follow these steps in order. Do NOT skip steps.
+
+### Validation Phase (Steps 1-3) -- MUST complete before any creation tool is called
+
+The number one error pattern is agents skipping validation and calling a creation tool with guessed or incomplete parameters. **Every field in the creation call must be grounded in data retrieved during this phase.** Do not proceed to Step 4 until Steps 1-3 are fully satisfied.
+
+#### Step 1: Understand the request
+
+Ask yourself:
+- What does the user want to monitor? (a specific table, a metric, a data quality rule, cross-table consistency, freshness/volume at schema level)
+- Which monitor type fits? Use the monitor types table above.
+- Does the user have all the details, or do they need guidance?
+
+If the user's intent is unclear, ask a focused question before proceeding.
+
+#### Step 2: Identify the table(s) and columns
+
+If you don't have the table MCON:
+1. Use `search` with the table name and `include_fields: ["field_names"]` to find the MCON and get column names.
+2. If the user provided a full table ID like `database:schema.table`, search for it.
+3. Once you have the MCON, call `getTable` with `include_fields: true` and `include_table_capabilities: true` to verify capabilities and get domain info.
+
+If you already have the MCON:
+1. Call `getTable` with the MCON, `include_fields: true`, and `include_table_capabilities: true`.
+
+**CRITICAL: You need the actual column names from `getTable` results. NEVER guess or hallucinate column names.** This is the most common source of monitor creation failures.
+
+For monitor types that require a timestamp column (metric monitors), review the column names and identify likely timestamp candidates. Present them to the user if ambiguous.
+
+#### Step 3: Handle domain assignment
+
+Monitors must be assigned to a domain that contains the table being monitored. The `getTable` response includes a `domains` list with `uuid` and `name`.
+
+1. If `domains` is empty: skip domain assignment.
+2. If `domains` has exactly one entry: default `domain_id` to that domain's UUID.
+3. If `domains` has multiple entries: present only those domains and ask the user to pick.
+
+Do NOT present all account domains as options -- only domains that contain the table are valid.
+
+**ALWAYS check the table's `domains` BEFORE calling any creation tool.**
+
+---
+
+### Creation Phase (Steps 4-8)
+
+Only enter this phase after the validation phase is complete with real data from MCP tools.
+
+#### Step 4: Load the sub-skill reference
+
+Based on the monitor type, read the detailed reference for parameter guidance:
+
+- **Metric** -- Read the detailed reference: `references/metric-monitor.md` (relative to this file)
+- **Validation** -- Read the detailed reference: `references/validation-monitor.md` (relative to this file)
+- **Custom SQL** -- Read the detailed reference: `references/custom-sql-monitor.md` (relative to this file)
+- **Comparison** -- Read the detailed reference: `references/comparison-monitor.md` (relative to this file)
+- **Table** -- Read the detailed reference: `references/table-monitor.md` (relative to this file)
+
+#### Step 5: Ask about scheduling
+
+**Skip this step for table monitors.** Table monitors do not support the `schedule` field in MaC YAML — adding it will cause a validation error on `montecarlo monitors apply`. Table monitor scheduling is managed automatically by Monte Carlo.
+
+For all other monitor types, the creation tools default to a fixed schedule running every 60 minutes. Present these options:
+
+1. **Fixed interval** -- any integer for `interval_minutes` (30, 60, 90, 120, 360, 720, 1440, etc.)
+2. **Dynamic** -- MC auto-determines when to run based on table update patterns.
+3. **Loose** -- runs once per day.
+
+Schedule format in MaC YAML:
+- Fixed: `schedule: { type: fixed, interval_minutes: <N> }`
+- Dynamic: `schedule: { type: dynamic }`
+- Loose: `schedule: { type: loose, start_time: "00:00" }`
+
+#### Step 6: Confirm with the user
+
+Before calling the creation tool, present the monitor configuration in plain language:
+- Monitor type
+- Target table (and columns if applicable)
+- What it checks / what triggers an alert
+- Domain assignment
+- Schedule
+
+Ask: "Does this look correct? I'll generate the monitor configuration."
+
+**NEVER call the creation tool without user confirmation.**
+
+#### Step 7: Create the monitor
+
+Call the appropriate creation tool with the parameters built in previous steps. Always pass an MCON when possible. If only table name is available, also pass warehouse.
+
+#### Step 8: Present results
+
+**CRITICAL: Always include the YAML in your response.** The user needs copy-pasteable YAML.
+
+1. If a non-default schedule was chosen, modify the schedule section in the YAML before presenting.
+2. Wrap the YAML in the full MaC structure (see "MaC YAML format" section below).
+3. ALWAYS present the full YAML in a ```yaml code block.
+4. Explain where to put it and how to apply it (see below).
+5. ALWAYS use ISO 8601 format for datetime values.
+6. NEVER reformat YAML values returned by creation tools.
+
+---
+
+## MaC YAML format
+
+The YAML returned by creation tools is the monitor definition. It must be wrapped in the standard MaC structure to be applied:
+
+```yaml
+montecarlo:
+  <monitor_type>:
+    - <returned yaml>
+```
+
+For example, a metric monitor would look like:
+
+```yaml
+montecarlo:
+  metric:
+    - <yaml returned by createMetricMonitorMac>
+```
+
+**Important:** `montecarlo.yml` (without a directory path) is a separate Monte Carlo project configuration file -- it is NOT the same as a monitor definition file. Monitor definitions go in their own `.yml` files, typically in a `monitors/` directory or alongside dbt model schema files.
+
+Tell the user:
+- Save the YAML to a `.yml` file (e.g. `monitors/<table_name>.yml` or in their dbt schema)
+- Apply via the Monte Carlo CLI: `montecarlo monitors apply --namespace <namespace>`
+- Or integrate into CI/CD for automatic deployment on merge
+
+---
+
+## Common mistakes to avoid
+
+- **NEVER guess column names.** Always get them from `getTable`.
+- **NEVER skip the confirmation step** (Step 6).
+- For metric monitors, `aggregate_time_field` MUST be a real timestamp column from the table.
+- For validation monitors, conditions match INVALID data, not valid data.
+- Always pass an MCON when possible. If only table name is available, also pass warehouse.
+- **ALWAYS check table's `domains` BEFORE calling any creation tool.**
+- ALWAYS use ISO 8601 format for datetime values.
+- NEVER reformat YAML values returned by creation tools.
+- Do not call creation tools before the validation phase is complete.