[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6PZQ3VYZK54MBT6BZSVTCSH":3,"skill-same:01M6PZQ3VYZK54MBT6BZSVTCSH":71},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":22,"publishedAt":43,"linkOnly":44,"markdownContent":45,"markdownBody":46,"frontMatter":47,"refName":35,"commitSha":52,"skillDirectory":53,"forksCount":13,"repositoryHtmlUrl":54,"repositoryHomepageUrl":6,"ownerHtmlUrl":55,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":56,"install":57,"resources":70},"01M6PZQ3VYZK54MBT6BZSVTCSH","tune-monitor",null,"Analyze a Monte Carlo monitor and recommend config changes to reduce alert noise. Supports metric, custom SQL, validation, and table monitors. Fetches the report, identifies patterns, and suggests tuning.","duc-duy-1612\u002FOnline-Delivery-Systems-Web","duc-duy-1612","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F192231384?v=4","01M6NSDKQQDKVTHZ8DZMZ1VYY6","01M6NSDKW8DDVTQHBT1HBDDJPT",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Ftune-monitor\u002FSKILL.md",[17],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42],"monitor","tune monitor","tune","wed","metric","recommend","reduce","tree","mc","critical","patterns","config","main","community","table","analyze","tuning","data","license","sql","2026-11-10 10:12:30",false,"---\nname: tune-monitor\ndescription: Analyze a Monte Carlo monitor and recommend config changes to reduce alert noise. Supports metric, custom SQL, validation, and table monitors. Fetches the report, identifies patterns, and suggests tuning.\nrisk: critical\nsource: https:\u002F\u002Fgithub.com\u002Fmonte-carlo-data\u002Fmc-agent-toolkit\u002Ftree\u002Fmain\u002Fskills\u002Ftune-monitor\nsource_repo: monte-carlo-data\u002Fmc-agent-toolkit\nsource_type: community\ndate_added: 2026-07-01\nlicense: Apache-2.0\nlicense_source: https:\u002F\u002Fgithub.com\u002Fmonte-carlo-data\u002Fmc-agent-toolkit\u002Fblob\u002Fmain\u002FLICENSE\n---\n\n# Tune Monitor: Noise Reduction Analysis\n## When to Use\n\nUse this skill when you need analyze a Monte Carlo monitor and recommend config changes to reduce alert noise. Supports metric, custom SQL, validation, and table monitors. Fetches the report, identifies patterns, and suggests tuning.\n\n\nYou are a Monte Carlo monitor tuning agent. Your job is to fetch a monitor's report, dump it to\na file for reference, analyze the alert patterns, and recommend concrete configuration changes to\nreduce noise without sacrificing real signal.\n\n> **Monte Carlo tool routing (required):** Always call Monte Carlo MCP tools through this plugin's\n> bundled server, whose fully-qualified tool names are\n> `mcp__plugin_mc-agent-toolkit_monte-carlo-mcp__\u003Ctool>` (e.g.\n> `mcp__plugin_mc-agent-toolkit_monte-carlo-mcp__get_alerts`). Bare tool names used in this skill\n> (`get_alerts`, `search`, `get_table`, …) refer to that bundled server. If the session also has a\n> separately-configured `monte-carlo-mcp` server, do **not** route to it — it may point at a\n> different endpoint or credentials.\n\n**Arguments:** $ARGUMENTS\n\nReference files live next to this skill file. **Use the Read tool** (not MCP resources) to access\nthem:\n\n- Metric monitor tuning: `references\u002Fmetric-monitor.md` (relative to this file)\n- Custom SQL monitor tuning: `references\u002Fcustom-sql-monitor.md` (relative to this file)\n- Validation monitor tuning: `references\u002Fvalidation-monitor.md` (relative to this file)\n- Table monitor tuning: `references\u002Ftable-monitor.md` (relative to this file)\n\n---\n\n## Prerequisites\n\n- **Required:** Monte Carlo MCP server (`monte-carlo-mcp`) must be configured and authenticated\n\n---\n\n## Available MCP tools\n\n| Tool | Purpose |\n|---|---|\n| `get_monitor_report` | Fetch a monitor's alert history, incident details, and troubleshooting summaries |\n| `get_monitors` | Fetch monitor configuration (type, thresholds, schedule, segments) |\n| `create_or_update_metric_monitor` | Update a metric monitor in place (pass `monitor_uuid`; used in Phase 5) |\n| `create_or_update_sql_monitor` | Update a custom SQL monitor in place (pass `monitor_uuid`; used in Phase 5) |\n| `create_or_update_validation_monitor` | Update a validation monitor in place (pass `monitor_uuid`; used in Phase 5) |\n| `create_or_update_table_monitor_asset_rule` | Tune freshness \u002F volume change \u002F unchanged size for a single table; pick the per-metric variant via `rule_type` (`last_updated_on` \u002F `total_row_count` \u002F `total_row_count_last_changed_on`). One call per `(table, metric)` pair (used in Phase 5). |\n\nAll three `create_or_update_*_monitor` tools follow a **two-call preview-then-confirm pattern**: the first call (with the default `dry_run=True`) returns the rendered MaC YAML for review in `result.yaml`; the second call (`dry_run=False`) deploys the change live and returns a deep link in `result.instructions`. **Always pass `monitor_uuid=\u003Cuuid>`** on both calls so the tool updates the existing monitor in place rather than creating a new one.\n\n---\n\n## Phase 0: Validate Input\n\nExtract the monitor UUID from `$ARGUMENTS`. It must be a valid UUID (format:\n`xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx`).\n\nIf no UUID is provided or it doesn't look like a UUID, stop and tell the user:\n\n> Please provide a monitor UUID. Example: `\u002Ftune-monitor 94c2dd3a-ef49-40f8-b1c1-741ba057cabf`\n\n---\n\n## Phase 1: Fetch Monitor Report\n\nCall `get_monitor_report` with:\n- `monitor_uuid`: the UUID from `$ARGUMENTS`\n- `max_incidents`: 50\n\nIf the tool returns an error or empty result, tell the user the monitor was not found and stop.\n\nAlso fetch the monitor's full config via `get_monitors` with:\n- `monitor_ids`: [`{monitor_uuid}`]\n- `include_fields`: [`config`]\n\nRun both calls in parallel.\n\n---\n\n## Phase 1.5: Determine Monitor Type and Load Reference\n\nFrom the `get_monitors` config response, determine the monitor type:\n\n| Config indicator | Type | Reference file |\n|---|---|---|\n| Monitor type is a metric monitor variant (e.g., metric, field health) | Metric | `references\u002Fmetric-monitor.md` |\n| Monitor type is a custom SQL rule \u002F custom monitor | Custom SQL | `references\u002Fcustom-sql-monitor.md` |\n| Monitor type is a validation rule \u002F validation monitor | Validation | `references\u002Fvalidation-monitor.md` |\n| Monitor type is a table monitor (freshness, volume, schema across tables) | Table | `references\u002Ftable-monitor.md` |\n\n**Read** the appropriate reference file using the Read tool with the path relative to this skill\nfile. The reference contains type-specific config fields to extract, recommendation guidance, and\napply-changes instructions.\n\nIf the monitor type is not metric, custom SQL, validation, or table, stop and tell the user:\n\n> This skill supports tuning metric, custom SQL, validation, and table monitors. This monitor\n> is a {type} monitor, which is not supported.\n\n---\n\n## Phase 2: Analyze the Report\n\nAnalyze the monitor report and config together. Focus on:\n\n### 2a. Alert volume & frequency\n- How many incidents in the last 30 days? Last 7 days?\n- What is the firing cadence — multiple times per day? Daily? Sporadic?\n- Are incidents clustered in time (bursts) or spread evenly?\n\n### 2b. Anomaly patterns\n- Which segments (field values) are firing most? Are they the same segments repeatedly?\n- Are anomalies consistently marginal (just above threshold) or severe?\n- Are any anomalies from sparse\u002Fbursty event types that naturally spike?\n- Are anomalies caused by known operational events (deployments, batch jobs, bulk user actions)?\n- For validation monitors: how many invalid rows per incident? Is the count stable or growing?\n- For table monitors: which (table, metric) pairs are firing most? Are they the same repeatedly?\n\n### 2c. Current configuration\nExtract the current configuration. The specific fields to look for are documented in the per-type\nreference loaded in Phase 1.5. At minimum, extract:\n- Monitor type and what it measures\n- Schedule interval\n- Audiences \u002F notification channels\n- Whether the monitor uses ML thresholds or explicit thresholds\n\n### 2d. Troubleshooting analysis (if available)\nLook at any troubleshooting TL;DRs in the report. Note:\n- Are most anomalies assessed as \"likely normal data variation\"?\n- Are there recurring root causes?\n- Is there a blind spot (e.g., no upstream metadata)?\n\n---\n\n## Phase 3: Generate Recommendations\n\nBased on the analysis, produce a prioritized list of recommendations. For each recommendation:\n- State the **problem** it solves\n- Give the **specific config change** (use exact field names from the MC config schema)\n- Explain the **trade-off** (what signal might be lost)\n\n### General recommendations (all monitor types)\n\n#### Sensitivity tuning (ML thresholds only)\nThis applies to any monitor that uses ML thresholds — both metric monitors and custom SQL monitors.\nSkip this section for validation monitors (they don't use ML thresholds), for table monitors\n(they have their own per-metric sensitivity — see the table monitor reference), and for monitors\nwith explicit thresholds (for custom SQL monitors, see threshold adjustment in the per-type\nreference instead).\n\n- If anomalies are consistently marginal (observed value just barely above threshold) AND assessed\n  as normal variation → recommend lowering sensitivity one step:\n  - If current sensitivity is `HIGH` → recommend `\"sensitivity\": \"medium\"`\n  - If current sensitivity is `MEDIUM` or `AUTO` → recommend `\"sensitivity\": \"low\"`\n- If current sensitivity is already `LOW` and still noisy → note this isn't a sensitivity issue\n\n#### Schedule \u002F interval\n- If the monitor fires multiple times per day but anomalies always resolve within hours → recommend\n  increasing schedule interval (e.g., from 720 min to 1440 min) to reduce duplicate alerts\n- If anomalies are caused by data arriving late → recommend increasing `collection_lag`\n\n#### Snooze \u002F training period\n- If the monitor was recently created (\u003C30 days) and is still learning patterns → recommend\n  waiting for the model to stabilize before tuning\n\n#### Audience \u002F notification routing\n- If the monitor has no audiences configured and is generating noise → recommend adding audiences\n  only for high-severity anomalies, or removing notifications entirely for known-noisy monitors\n\n### Type-specific recommendations\n\nFor type-specific recommendations (WHERE conditions, segment exclusion, aggregation changes,\nthreshold adjustment, SQL modifications, alert condition modifications, per-table-metric\nsensitivity tuning), follow the guidance in the per-type reference loaded in Phase 1.5.\n\n---\n\n## Phase 4: Present the Report\n\nOutput a structured analysis. **This is the primary output — include it in full.**\n\n```markdown\n## Monitor Tune Report: {monitor_uuid}\n\n**Monitor:** {display_name or mac_name}\n**Type:** {monitor type — metric, custom SQL, validation, or table}\n**Table:** {table}\n**What it monitors:** {metric and segments, SQL query summary, validation conditions, or table\u002Fmetric coverage}\n**Current sensitivity:** {sensitivity or \"AUTO (default)\" or \"N\u002FA (explicit thresholds)\"}\n**Schedule:** every {interval_minutes \u002F 60}h\n\n### Alert Summary (last 30 days)\n- Total alerts: {count}\n- Firing frequency: {e.g., \"~twice daily\", \"daily\", \"sporadic\"}\n- Most noisy segments: {top 2-3 segment values by alert count, or N\u002FA for custom SQL\u002Fvalidation}\n- Most noisy (table, metric) pairs: {for table monitors: top pairs by anomaly count}\n\n### Root Cause Pattern\n{1-3 sentence summary of what the alerts represent — operational events, bursty data, model\nmiscalibration, genuine issues, etc.}\n\n### Recommendations\n\n#### 1. {Highest-impact change} [RECOMMENDED]\n**Problem:** ...\n**Change:**\n```yaml\n{specific config field}: {new value}\n```\n**Trade-off:** ...\n\n#### 2. {Second change} [OPTIONAL]\n...\n\n#### 3. {Third change} [OPTIONAL]\n...\n\n### What NOT to change\n{Any configurations that look correct and should be left alone — avoid over-tuning.}\n\n### If these changes are made\n{Predict the expected outcome: estimated alert reduction, what genuine anomalies would still fire.}\n```\n\n**Next step:** \"Want me to apply any of these changes to the monitor config, or explore the alert\nhistory further?\"\n\n---\n\n## Phase 5: Apply Changes (if user requests)\n\nTo apply changes, follow the apply-changes instructions in the per-type reference loaded in\nPhase 1.5. Each reference specifies the correct tool and constraints for that monitor type.\n\nGeneral rules for all types:\n1. **Always preview first** — show the user what will change before applying.\n2. **Get explicit confirmation** before applying any change.\n3. **Validate the preview YAML against the schema** — before presenting the preview YAML to the user, fetch the published MaC JSON Schema from `https:\u002F\u002Fclidocs.getmontecarlo.com\u002Fmac\u002Fschema.json` (WebFetch) and check the preview YAML against it. If any field in the YAML does not appear in the schema for the given monitor type, flag it and correct it. Note: the schema validates field names, types, and enum values only — cross-field semantic constraints are enforced by the backend at apply time, not by the schema.\n4. **MaC-managed monitors** — if `get_monitors` returns a `mac_name` or the user mentions the monitor is managed via a MaC YAML file, note this before applying: changes made via the API will be overwritten the next time `montecarlo monitors apply` runs. Offer to hand off to `\u002Fmanage-mac` (edit workflow) instead so the YAML file stays the source of truth.\n\n---\n\n## Guidelines\n\n- **Be specific.** Generic advice like \"reduce sensitivity\" is less useful than exact config changes.\n- **Prefer surgical changes.** A targeted WHERE condition beats a blunt sensitivity reduction.\n- **Preserve signal.** Always explain what genuine anomalies would still be caught after tuning.\n- **Cite evidence.** Reference specific incident dates, segment values, and counts from the report.\n- **Degrade gracefully.** If troubleshooting runs are missing, note the limited context and\n  reason from alert patterns alone.\n- **Add `$schema` when saving YAML to a file.** If the user asks to save the MaC YAML to a file, add `# yaml-language-server: $schema=https:\u002F\u002Fclidocs.getmontecarlo.com\u002Fmac\u002Fschema.json` as the first line of that file.\n\n## Limitations\n\n- Use this skill only when the task clearly matches its upstream source and local project context.\n- Verify commands, generated code, dependencies, credentials, and external service behavior before applying changes.\n- Do not treat examples as a substitute for environment-specific tests, security review, or user approval for destructive or costly actions.\n","# Tune Monitor: Noise Reduction Analysis\n## When to Use\n\nUse this skill when you need analyze a Monte Carlo monitor and recommend config changes to reduce alert noise. Supports metric, custom SQL, validation, and table monitors. Fetches the report, identifies patterns, and suggests tuning.\n\n\nYou are a Monte Carlo monitor tuning agent. Your job is to fetch a monitor's report, dump it to\na file for reference, analyze the alert patterns, and recommend concrete configuration changes to\nreduce noise without sacrificing real signal.\n\n> **Monte Carlo tool routing (required):** Always call Monte Carlo MCP tools through this plugin's\n> bundled server, whose fully-qualified tool names are\n> `mcp__plugin_mc-agent-toolkit_monte-carlo-mcp__\u003Ctool>` (e.g.\n> `mcp__plugin_mc-agent-toolkit_monte-carlo-mcp__get_alerts`). Bare tool names used in this skill\n> (`get_alerts`, `search`, `get_table`, …) refer to that bundled server. If the session also has a\n> separately-configured `monte-carlo-mcp` server, do **not** route to it — it may point at a\n> different endpoint or credentials.\n\n**Arguments:** $ARGUMENTS\n\nReference files live next to this skill file. **Use the Read tool** (not MCP resources) to access\nthem:\n\n- Metric monitor tuning: `references\u002Fmetric-monitor.md` (relative to this file)\n- Custom SQL monitor tuning: `references\u002Fcustom-sql-monitor.md` (relative to this file)\n- Validation monitor tuning: `references\u002Fvalidation-monitor.md` (relative to this file)\n- Table monitor tuning: `references\u002Ftable-monitor.md` (relative to this file)\n\n---\n\n## Prerequisites\n\n- **Required:** Monte Carlo MCP server (`monte-carlo-mcp`) must be configured and authenticated\n\n---\n\n## Available MCP tools\n\n| Tool | Purpose |\n|---|---|\n| `get_monitor_report` | Fetch a monitor's alert history, incident details, and troubleshooting summaries |\n| `get_monitors` | Fetch monitor configuration (type, thresholds, schedule, segments) |\n| `create_or_update_metric_monitor` | Update a metric monitor in place (pass `monitor_uuid`; used in Phase 5) |\n| `create_or_update_sql_monitor` | Update a custom SQL monitor in place (pass `monitor_uuid`; used in Phase 5) |\n| `create_or_update_validation_monitor` | Update a validation monitor in place (pass `monitor_uuid`; used in Phase 5) |\n| `create_or_update_table_monitor_asset_rule` | Tune freshness \u002F volume change \u002F unchanged size for a single table; pick the per-metric variant via `rule_type` (`last_updated_on` \u002F `total_row_count` \u002F `total_row_count_last_changed_on`). One call per `(table, metric)` pair (used in Phase 5). |\n\nAll three `create_or_update_*_monitor` tools follow a **two-call preview-then-confirm pattern**: the first call (with the default `dry_run=True`) returns the rendered MaC YAML for review in `result.yaml`; the second call (`dry_run=False`) deploys the change live and returns a deep link in `result.instructions`. **Always pass `monitor_uuid=\u003Cuuid>`** on both calls so the tool updates the existing monitor in place rather than creating a new one.\n\n---\n\n## Phase 0: Validate Input\n\nExtract the monitor UUID from `$ARGUMENTS`. It must be a valid UUID (format:\n`xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx`).\n\nIf no UUID is provided or it doesn't look like a UUID, stop and tell the user:\n\n> Please provide a monitor UUID. Example: `\u002Ftune-monitor 94c2dd3a-ef49-40f8-b1c1-741ba057cabf`\n\n---\n\n## Phase 1: Fetch Monitor Report\n\nCall `get_monitor_report` with:\n- `monitor_uuid`: the UUID from `$ARGUMENTS`\n- `max_incidents`: 50\n\nIf the tool returns an error or empty result, tell the user the monitor was not found and stop.\n\nAlso fetch the monitor's full config via `get_monitors` with:\n- `monitor_ids`: [`{monitor_uuid}`]\n- `include_fields`: [`config`]\n\nRun both calls in parallel.\n\n---\n\n## Phase 1.5: Determine Monitor Type and Load Reference\n\nFrom the `get_monitors` config response, determine the monitor type:\n\n| Config indicator | Type | Reference file |\n|---|---|---|\n| Monitor type is a metric monitor variant (e.g., metric, field health) | Metric | `references\u002Fmetric-monitor.md` |\n| Monitor type is a custom SQL rule \u002F custom monitor | Custom SQL | `references\u002Fcustom-sql-monitor.md` |\n| Monitor type is a validation rule \u002F validation monitor | Validation | `references\u002Fvalidation-monitor.md` |\n| Monitor type is a table monitor (freshness, volume, schema across tables) | Table | `references\u002Ftable-monitor.md` |\n\n**Read** the appropriate reference file using the Read tool with the path relative to this skill\nfile. The reference contains type-specific config fields to extract, recommendation guidance, and\napply-changes instructions.\n\nIf the monitor type is not metric, custom SQL, validation, or table, stop and tell the user:\n\n> This skill supports tuning metric, custom SQL, validation, and table monitors. This monitor\n> is a {type} monitor, which is not supported.\n\n---\n\n## Phase 2: Analyze the Report\n\nAnalyze the monitor report and config together. Focus on:\n\n### 2a. Alert volume & frequency\n- How many incidents in the last 30 days? Last 7 days?\n- What is the firing cadence — multiple times per day? Daily? Sporadic?\n- Are incidents clustered in time (bursts) or spread evenly?\n\n### 2b. Anomaly patterns\n- Which segments (field values) are firing most? Are they the same segments repeatedly?\n- Are anomalies consistently marginal (just above threshold) or severe?\n- Are any anomalies from sparse\u002Fbursty event types that naturally spike?\n- Are anomalies caused by known operational events (deployments, batch jobs, bulk user actions)?\n- For validation monitors: how many invalid rows per incident? Is the count stable or growing?\n- For table monitors: which (table, metric) pairs are firing most? Are they the same repeatedly?\n\n### 2c. Current configuration\nExtract the current configuration. The specific fields to look for are documented in the per-type\nreference loaded in Phase 1.5. At minimum, extract:\n- Monitor type and what it measures\n- Schedule interval\n- Audiences \u002F notification channels\n- Whether the monitor uses ML thresholds or explicit thresholds\n\n### 2d. Troubleshooting analysis (if available)\nLook at any troubleshooting TL;DRs in the report. Note:\n- Are most anomalies assessed as \"likely normal data variation\"?\n- Are there recurring root causes?\n- Is there a blind spot (e.g., no upstream metadata)?\n\n---\n\n## Phase 3: Generate Recommendations\n\nBased on the analysis, produce a prioritized list of recommendations. For each recommendation:\n- State the **problem** it solves\n- Give the **specific config change** (use exact field names from the MC config schema)\n- Explain the **trade-off** (what signal might be lost)\n\n### General recommendations (all monitor types)\n\n#### Sensitivity tuning (ML thresholds only)\nThis applies to any monitor that uses ML thresholds — both metric monitors and custom SQL monitors.\nSkip this section for validation monitors (they don't use ML thresholds), for table monitors\n(they have their own per-metric sensitivity — see the table monitor reference), and for monitors\nwith explicit thresholds (for custom SQL monitors, see threshold adjustment in the per-type\nreference instead).\n\n- If anomalies are consistently marginal (observed value just barely above threshold) AND assessed\n  as normal variation → recommend lowering sensitivity one step:\n  - If current sensitivity is `HIGH` → recommend `\"sensitivity\": \"medium\"`\n  - If current sensitivity is `MEDIUM` or `AUTO` → recommend `\"sensitivity\": \"low\"`\n- If current sensitivity is already `LOW` and still noisy → note this isn't a sensitivity issue\n\n#### Schedule \u002F interval\n- If the monitor fires multiple times per day but anomalies always resolve within hours → recommend\n  increasing schedule interval (e.g., from 720 min to 1440 min) to reduce duplicate alerts\n- If anomalies are caused by data arriving late → recommend increasing `collection_lag`\n\n#### Snooze \u002F training period\n- If the monitor was recently created (\u003C30 days) and is still learning patterns → recommend\n  waiting for the model to stabilize before tuning\n\n#### Audience \u002F notification routing\n- If the monitor has no audiences configured and is generating noise → recommend adding audiences\n  only for high-severity anomalies, or removing notifications entirely for known-noisy monitors\n\n### Type-specific recommendations\n\nFor type-specific recommendations (WHERE conditions, segment exclusion, aggregation changes,\nthreshold adjustment, SQL modifications, alert condition modifications, per-table-metric\nsensitivity tuning), follow the guidance in the per-type reference loaded in Phase 1.5.\n\n---\n\n## Phase 4: Present the Report\n\nOutput a structured analysis. **This is the primary output — include it in full.**\n\n```markdown\n## Monitor Tune Report: {monitor_uuid}\n\n**Monitor:** {display_name or mac_name}\n**Type:** {monitor type — metric, custom SQL, validation, or table}\n**Table:** {table}\n**What it monitors:** {metric and segments, SQL query summary, validation conditions, or table\u002Fmetric coverage}\n**Current sensitivity:** {sensitivity or \"AUTO (default)\" or \"N\u002FA (explicit thresholds)\"}\n**Schedule:** every {interval_minutes \u002F 60}h\n\n### Alert Summary (last 30 days)\n- Total alerts: {count}\n- Firing frequency: {e.g., \"~twice daily\", \"daily\", \"sporadic\"}\n- Most noisy segments: {top 2-3 segment values by alert count, or N\u002FA for custom SQL\u002Fvalidation}\n- Most noisy (table, metric) pairs: {for table monitors: top pairs by anomaly count}\n\n### Root Cause Pattern\n{1-3 sentence summary of what the alerts represent — operational events, bursty data, model\nmiscalibration, genuine issues, etc.}\n\n### Recommendations\n\n#### 1. {Highest-impact change} [RECOMMENDED]\n**Problem:** ...\n**Change:**\n```yaml\n{specific config field}: {new value}\n```\n**Trade-off:** ...\n\n#### 2. {Second change} [OPTIONAL]\n...\n\n#### 3. {Third change} [OPTIONAL]\n...\n\n### What NOT to change\n{Any configurations that look correct and should be left alone — avoid over-tuning.}\n\n### If these changes are made\n{Predict the expected outcome: estimated alert reduction, what genuine anomalies would still fire.}\n```\n\n**Next step:** \"Want me to apply any of these changes to the monitor config, or explore the alert\nhistory further?\"\n\n---\n\n## Phase 5: Apply Changes (if user requests)\n\nTo apply changes, follow the apply-changes instructions in the per-type reference loaded in\nPhase 1.5. Each reference specifies the correct tool and constraints for that monitor type.\n\nGeneral rules for all types:\n1. **Always preview first** — show the user what will change before applying.\n2. **Get explicit confirmation** before applying any change.\n3. **Validate the preview YAML against the schema** — before presenting the preview YAML to the user, fetch the published MaC JSON Schema from `https:\u002F\u002Fclidocs.getmontecarlo.com\u002Fmac\u002Fschema.json` (WebFetch) and check the preview YAML against it. If any field in the YAML does not appear in the schema for the given monitor type, flag it and correct it. Note: the schema validates field names, types, and enum values only — cross-field semantic constraints are enforced by the backend at apply time, not by the schema.\n4. **MaC-managed monitors** — if `get_monitors` returns a `mac_name` or the user mentions the monitor is managed via a MaC YAML file, note this before applying: changes made via the API will be overwritten the next time `montecarlo monitors apply` runs. Offer to hand off to `\u002Fmanage-mac` (edit workflow) instead so the YAML file stays the source of truth.\n\n---\n\n## Guidelines\n\n- **Be specific.** Generic advice like \"reduce sensitivity\" is less useful than exact config changes.\n- **Prefer surgical changes.** A targeted WHERE condition beats a blunt sensitivity reduction.\n- **Preserve signal.** Always explain what genuine anomalies would still be caught after tuning.\n- **Cite evidence.** Reference specific incident dates, segment values, and counts from the report.\n- **Degrade gracefully.** If troubleshooting runs are missing, note the limited context and\n  reason from alert patterns alone.\n- **Add `$schema` when saving YAML to a file.** If the user asks to save the MaC YAML to a file, add `# yaml-language-server: $schema=https:\u002F\u002Fclidocs.getmontecarlo.com\u002Fmac\u002Fschema.json` as the first line of that file.\n\n## Limitations\n\n- Use this skill only when the task clearly matches its upstream source and local project context.\n- Verify commands, generated code, dependencies, credentials, and external service behavior before applying changes.\n- Do not treat examples as a substitute for environment-specific tests, security review, or user approval for destructive or costly actions.\n",{"name":5,"risk":32,"source":48,"license":14,"date_added":49,"description":7,"source_repo":50,"source_type":36,"license_source":51},"https:\u002F\u002Fgithub.com\u002Fmonte-carlo-data\u002Fmc-agent-toolkit\u002Ftree\u002Fmain\u002Fskills\u002Ftune-monitor",1782864000000,"monte-carlo-data\u002Fmc-agent-toolkit","https:\u002F\u002Fgithub.com\u002Fmonte-carlo-data\u002Fmc-agent-toolkit\u002Fblob\u002Fmain\u002FLICENSE","f3312ba749561b6159f477dbfc9313c875d40a56",".agents\u002Fskills_archive\u002Ftune-monitor","https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web","https:\u002F\u002Fgithub.com\u002Fduc-duy-1612","2026-10-25 23:50:58",{"source":8,"skillName":5,"commands":58,"prompt":68,"zipAvailable":69},[59,62,65],{"tool":60,"command":61},"npx","npx skills add duc-duy-1612\u002FOnline-Delivery-Systems-Web --skill tune-monitor",{"tool":63,"command":64},"bunx","bunx skills add duc-duy-1612\u002FOnline-Delivery-Systems-Web --skill tune-monitor",{"tool":66,"command":67},"pnpm","pnpm dlx skills add duc-duy-1612\u002FOnline-Delivery-Systems-Web --skill tune-monitor","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Ftune-monitor\u002FSKILL.md",true,[],[72,99,123,147,175,199],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":76,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":82,"publishedAt":43},"01M6Q0FA5FZ410Z33Z3TFQ4DBA","zero-trust","Implement zero-trust network architecture. Configure identity-based access, micro-segmentation, and continuous verification. Use when implementing modern security architectures.","MIT","https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fzero-trust\u002FSKILL.md",[79],{"categoryNo":80,"categoryName":81,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000011","运维与部署",[83,84,85,86,87,88,74,89,90,91,92,93,36,35,94,32,95,96,97,98],"ZeRO","trust","zero trust","architecture","assessment","verification","segmentation","devops-security","access","configure","only","active","scope","scripts","relevant","implementing",{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":76,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":43},"01M6Q0F1YZJW3KX5FBKEVZ8CV4","zcode-delegate","Delegate coding tasks to the Z.AI ZCode CLI only when the user explicitly requests it, while the orchestrator retains review and landing responsibility.","https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fzcode-delegate\u002FSKILL.md",[],[106,107,108,109,110,111,112,113,114,115,116,117,118,93,119,36,120,121,32,122],"delegate","zcode","zcode delegate","review","cli","orchestration","tasks","run","Bash","model","node","read","orchestrator","files","desktop app","app","agent-orchestration",{"skillNo":124,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":76,"licenseFileUrl":6,"sourceHtmlUrl":127,"categories":128,"keywords":129,"publishedAt":43},"01M6Q0ETK41VGNMYEXW0T00AJN","youtube-transcript","Fetch YouTube transcripts through DeepAPI or local fallback tooling and save clean text output.","https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fyoutube-transcript\u002FSKILL.md",[],[130,131,132,133,134,135,136,41,137,138,139,140,141,36,35,142,143,144,145,146],"transcript","youtube transcript","youtube","safe","github","codex","research","https","text","fetch","tooling","clean","local","output","deepapi","youtube transcripts","blob",{"skillNo":148,"name":149,"nameZh":6,"description":150,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":76,"licenseFileUrl":6,"sourceHtmlUrl":151,"categories":152,"keywords":164,"publishedAt":43},"01M6Q0EPPH2PVMDW40017F8WX0","youtube-transcript-skills","Fetch YouTube video transcripts, search videos\u002Fchannels, browse channels, and extract playlists via the getyoutubetranscript.com API - free tier, no card required.","https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fyoutube-transcript-skills\u002FSKILL.md",[153,156,159],{"categoryNo":154,"categoryName":155,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":157,"categoryName":158,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":160,"categoryName":161,"taxonomyType":162,"taxonomyTypeDesc":163},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[130,131,132,165,133,166,134,135,41,167,168,169,170,139,171,36,35,172,173,174],"youtube transcript skills","gemini","search","api","Video","browse","api-integration","free","card","channels",{"skillNo":176,"name":177,"nameZh":6,"description":178,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":76,"licenseFileUrl":6,"sourceHtmlUrl":179,"categories":180,"keywords":185,"publishedAt":43},"01M6Q0EAB96PX83W5PTE8A0R8D","youtube-notetaker","Turn YouTube talks into local study notes with slides, transcripts, editable annotations, and a markdown-backed viewer.","https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fyoutube-notetaker\u002FSKILL.md",[181,184],{"categoryNo":182,"categoryName":183,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000003","演示文稿",{"categoryNo":157,"categoryName":158,"taxonomyType":20,"taxonomyTypeDesc":21},[132,186,187,110,133,188,189,190,191,41,169,192,193,194,195,35,196,142,197,198],"youtube notetaker","notetaker","workflow","official","notes","code","markdown","slides","annotations","README","study","dair-academy","viewer",{"skillNo":200,"name":201,"nameZh":6,"description":202,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":76,"licenseFileUrl":6,"sourceHtmlUrl":203,"categories":204,"keywords":206,"publishedAt":43},"01M6Q0E55F0GW5MX48V8HXS8B5","youtube-full","Fetch YouTube transcripts, search videos, browse channels, and extract playlists via TranscriptAPI — no yt-dlp, no Google API key, works from any cloud server.","https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fyoutube-full\u002FSKILL.md",[205],{"categoryNo":154,"categoryName":155,"taxonomyType":20,"taxonomyTypeDesc":21},[207,132,208,209,133,166,167,210,211,168,169,170,139,212,171,36,35,172,213,145],"youtube full","full","google","server","dlp","credits","automatic"]