メニュー
Guides creation of Monte Carlo monitors via MCP tools, producing monitors-as-code YAML for CI/CD deployment.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/phoroth/AGENTIC --skill monte-carlo-monitor-creationコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
Development skill from AGENTIC (https://github.com/phoroth/AGENTIC)
Development skill from AGENTIC (https://github.com/phoroth/AGENTIC)
Generate clean, human-sounding, SEO-optimized WordPress blog posts with optional Yoast metadata, JSON-LD schema markup, and image SEO planning. Supports modular batch output.
SOC 職業分類に基づく
SKILL.md を表示中
| 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"] |
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:
references/metric-monitor.md (relative to this file)references/validation-monitor.md (relative to this file)references/custom-sql-monitor.md (relative to this file)references/comparison-monitor.md (relative to this file)references/table-monitor.md (relative to this file)Activate when the user:
Do not activate when the user is:
getMonitors directly)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) |
| 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. |
Follow these steps in order. Do NOT skip steps.
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.
Ask yourself:
If the user's intent is unclear, ask a focused question before proceeding.
If you don't have the table MCON:
search with the table name and include_fields: ["field_names"] to find the MCON and get column names.database:schema.table, search for it.getTable with include_fields: true and include_table_capabilities: true to verify capabilities and get domain info.If you already have the MCON:
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.
Monitors must be assigned to a domain that contains the table being monitored. The getTable response includes a domains list with uuid and name.
domains is empty: skip domain assignment.domains has exactly one entry: default domain_id to that domain's UUID.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.
Only enter this phase after the validation phase is complete with real data from MCP tools.
Based on the monitor type, read the detailed reference for parameter guidance:
references/metric-monitor.md (relative to this file)references/validation-monitor.md (relative to this file)references/custom-sql-monitor.md (relative to this file)references/comparison-monitor.md (relative to this file)references/table-monitor.md (relative to this file)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:
interval_minutes (30, 60, 90, 120, 360, 720, 1440, etc.)Schedule format in MaC YAML:
schedule: { type: fixed, interval_minutes: <N> }schedule: { type: dynamic }schedule: { type: loose, start_time: "00:00" }Before calling the creation tool, present the monitor configuration in plain language:
Ask: "Does this look correct? I'll generate the monitor configuration."
NEVER call the creation tool without user confirmation.
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.
CRITICAL: Always include the YAML in your response. The user needs copy-pasteable YAML.
The YAML returned by creation tools is the monitor definition. It must be wrapped in the standard MaC structure to be applied:
montecarlo:
<monitor_type>:
- <returned yaml>
For example, a metric monitor would look like:
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:
.yml file (e.g. monitors/<table_name>.yml or in their dbt schema)montecarlo monitors apply --namespace <namespace>getTable.aggregate_time_field MUST be a real timestamp column from the table.domains BEFORE calling any creation tool.