[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M74GDGKACC6KNKMM3B0M7GBT":3,"skill-same:01M74GDGKACC6KNKMM3B0M7GBT":44},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":29,"install":30,"resources":43},"01M74GDGKACC6KNKMM3B0M7GBT","author-monitor",null,"Author a Datadog monitor — query, threshold, evaluation window, no-data behavior, notification routing; pair with polymath-sre:slo-design for SLO burn-rate monitors.","MohammadBafkar\u002Fpolymath","MohammadBafkar","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F34940462?v=4","01M74G540TQFZWK6KVAPKFVGNR","Mohammad Bafkar","01M74G541HG19QP9V5DQCJVKYE",0,"MIT","https:\u002F\u002Fgithub.com\u002FMohammadBafkar\u002Fpolymath\u002Fblob\u002Fmain\u002Fplugins\u002Fpolymath-observability\u002Fskills\u002Fauthor-monitor\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: author-monitor\ndescription: Author a Datadog monitor — query, threshold, evaluation window, no-data behavior, notification routing; pair with polymath-sre:slo-design for SLO burn-rate monitors.\n---\n\n# author-monitor\n\n> Write one Datadog monitor and create it via the MCP server. Output is the monitor JSON + the rationale.\n\n**Mode:** analytical — judgment inside a fixed frame. Keep the output shape; every verdict cites its evidence; unknowns are marked `[TBD]` or `[VERIFY]`, never filled in.\n\n> **MCP binding (read before any tool call):** if your host has a `datadog` MCP server, use its tools for this skill's data access. Check your own tool list — it may be registered under another name (a Claude Code connector appears as `mcp__claude_ai_\u003CName>__*`). Tool names differ between servers: use the closest match, and say so when the server is read-only. Never install or start a second copy. If there is none, work without MCP tool calls (give the user the queries or steps to run) and ask before suggesting an install.\n\n## When to use\n\n- A new service needs alerting before going live.\n- An existing alert is too noisy or too quiet; we want to tune it.\n\n## Inputs\n\n- The metric or log query.\n- The SLO target (if pair with `polymath-sre:slo-design`).\n- The destination (Slack channel, PagerDuty service, email list).\n\n## Procedure\n\nIf the host's Datadog server is read-only (no create tool — the default for the hosted server), do steps 1-8, validate, then output the monitor JSON for the user to apply instead of creating it. Say so up front. When a create tool exists, still show the final JSON and get explicit approval before creating — a new monitor can page people at 3am.\n\n1. **Decide the monitor type**:\n   - **metric alert** — Prometheus\u002FDatadog metric exceeds a threshold.\n   - **anomaly** — significant deviation from history. Use only when threshold-based is genuinely impossible.\n   - **log alert** — count of matching log lines.\n   - **service check** — uptime \u002F synthetic.\n   - **composite** — `(monitorA && monitorB) || monitorC`.\n   - **SLO burn rate** (`slo alert`) — alerts on how fast an SLO's error budget is burning; the right type for SLO paging (see `polymath-sre:slo-design` for the windows).\n2. **Query** — write the metric or log query using metric names you have confirmed exist (search\u002Flist metrics first; never guess a name). Validate it before automating; the MCP creates monitors but it doesn't validate semantics. If the server offers a validation tool (`validate_monitor_definition`), run it on the finished definition.\n3. **Threshold** — derive from the SLO or from a documented baseline. **Never** \"pick a round number that looks right\".\n4. **Evaluation window** — match the response expectation:\n   - Page (sev2): 5-15 min window with a short critical threshold.\n   - Ticket: 6h+ window.\n5. **No-data behavior** — explicit. For revenue-impacting paths: `notify_no_data: true`, `no_data_timeframe: 10`. For things that legitimately go quiet (low traffic at night): `notify_no_data: false` with a comment explaining why.\n6. **Notification message** — Markdown, with sections: what's broken, why it matters, link to runbook, link to dashboard. Use `{{value}}` and `{{#is_alert}}` Datadog template syntax.\n7. **Routing** — `@pagerduty-\u003Cservice>` for pages; `@slack-\u003Cchannel>` for tickets. Tag the team owner.\n8. **Tags** — `team:`, `service:`, `severity:`, `slo:` so monitors can be filtered.\n\n## Output\n\n```text\nMonitor: refund-p99-500ms\n\nType: metric alert\nQuery: avg(last_5m):p99:trace.http.request{service:refund-service} > 0.5\n\nThresholds:\n  critical: 0.5     (500ms, matches SLO threshold)\n  warning:  0.4\n\nEvaluation window: 5 minutes (fast symptom alert; the SLO burn-rate pages\nlive in separate `slo alert` monitors).\n\nNo-data: notify_no_data=true, no_data_timeframe=10 (refund is a hot path).\n\nMessage:\n  @pagerduty-payments\n  ## Refund p99 latency above SLO\n  p99 latency on refund-service is {{value}}s (threshold 0.5s, the\n  latency SLO's target). Check the SLO burn-rate monitor for budget impact.\n\n  Runbook: \u003Clink>\n  Dashboard: \u003Clink>\n\nTags: team:payments, service:refund-service, severity:sev2, slo:refund-latency\n```\n\n## Quality bar\n\n- Threshold derived from an SLO or a baseline number, with the source named.\n- Nothing created without approval of the final JSON.\n- `notify_no_data` explicitly set, not defaulted.\n- Notification routes via `@pagerduty-\u003Cservice>` (not a person), tagged with team owner.\n- Runbook + dashboard links in the message.\n\n## Anti-patterns to avoid\n\n- Anomaly monitors as the first alert — usually too noisy without a strong baseline.\n- \"Composite\" monitors that fan out across teams. Pick a clear owner.\n- Notification messages that contain the threshold as a literal but no link to context.\n\n","# author-monitor\n\n> Write one Datadog monitor and create it via the MCP server. Output is the monitor JSON + the rationale.\n\n**Mode:** analytical — judgment inside a fixed frame. Keep the output shape; every verdict cites its evidence; unknowns are marked `[TBD]` or `[VERIFY]`, never filled in.\n\n> **MCP binding (read before any tool call):** if your host has a `datadog` MCP server, use its tools for this skill's data access. Check your own tool list — it may be registered under another name (a Claude Code connector appears as `mcp__claude_ai_\u003CName>__*`). Tool names differ between servers: use the closest match, and say so when the server is read-only. Never install or start a second copy. If there is none, work without MCP tool calls (give the user the queries or steps to run) and ask before suggesting an install.\n\n## When to use\n\n- A new service needs alerting before going live.\n- An existing alert is too noisy or too quiet; we want to tune it.\n\n## Inputs\n\n- The metric or log query.\n- The SLO target (if pair with `polymath-sre:slo-design`).\n- The destination (Slack channel, PagerDuty service, email list).\n\n## Procedure\n\nIf the host's Datadog server is read-only (no create tool — the default for the hosted server), do steps 1-8, validate, then output the monitor JSON for the user to apply instead of creating it. Say so up front. When a create tool exists, still show the final JSON and get explicit approval before creating — a new monitor can page people at 3am.\n\n1. **Decide the monitor type**:\n   - **metric alert** — Prometheus\u002FDatadog metric exceeds a threshold.\n   - **anomaly** — significant deviation from history. Use only when threshold-based is genuinely impossible.\n   - **log alert** — count of matching log lines.\n   - **service check** — uptime \u002F synthetic.\n   - **composite** — `(monitorA && monitorB) || monitorC`.\n   - **SLO burn rate** (`slo alert`) — alerts on how fast an SLO's error budget is burning; the right type for SLO paging (see `polymath-sre:slo-design` for the windows).\n2. **Query** — write the metric or log query using metric names you have confirmed exist (search\u002Flist metrics first; never guess a name). Validate it before automating; the MCP creates monitors but it doesn't validate semantics. If the server offers a validation tool (`validate_monitor_definition`), run it on the finished definition.\n3. **Threshold** — derive from the SLO or from a documented baseline. **Never** \"pick a round number that looks right\".\n4. **Evaluation window** — match the response expectation:\n   - Page (sev2): 5-15 min window with a short critical threshold.\n   - Ticket: 6h+ window.\n5. **No-data behavior** — explicit. For revenue-impacting paths: `notify_no_data: true`, `no_data_timeframe: 10`. For things that legitimately go quiet (low traffic at night): `notify_no_data: false` with a comment explaining why.\n6. **Notification message** — Markdown, with sections: what's broken, why it matters, link to runbook, link to dashboard. Use `{{value}}` and `{{#is_alert}}` Datadog template syntax.\n7. **Routing** — `@pagerduty-\u003Cservice>` for pages; `@slack-\u003Cchannel>` for tickets. Tag the team owner.\n8. **Tags** — `team:`, `service:`, `severity:`, `slo:` so monitors can be filtered.\n\n## Output\n\n```text\nMonitor: refund-p99-500ms\n\nType: metric alert\nQuery: avg(last_5m):p99:trace.http.request{service:refund-service} > 0.5\n\nThresholds:\n  critical: 0.5     (500ms, matches SLO threshold)\n  warning:  0.4\n\nEvaluation window: 5 minutes (fast symptom alert; the SLO burn-rate pages\nlive in separate `slo alert` monitors).\n\nNo-data: notify_no_data=true, no_data_timeframe=10 (refund is a hot path).\n\nMessage:\n  @pagerduty-payments\n  ## Refund p99 latency above SLO\n  p99 latency on refund-service is {{value}}s (threshold 0.5s, the\n  latency SLO's target). Check the SLO burn-rate monitor for budget impact.\n\n  Runbook: \u003Clink>\n  Dashboard: \u003Clink>\n\nTags: team:payments, service:refund-service, severity:sev2, slo:refund-latency\n```\n\n## Quality bar\n\n- Threshold derived from an SLO or a baseline number, with the source named.\n- Nothing created without approval of the final JSON.\n- `notify_no_data` explicitly set, not defaulted.\n- Notification routes via `@pagerduty-\u003Cservice>` (not a person), tagged with team owner.\n- Runbook + dashboard links in the message.\n\n## Anti-patterns to avoid\n\n- Anomaly monitors as the first alert — usually too noisy without a strong baseline.\n- \"Composite\" monitors that fan out across teams. Pick a clear owner.\n- Notification messages that contain the threshold as a literal but no link to context.\n\n",{"name":5,"description":7},"main","23f6e21841a39580c9da2b5ec941f39dda17cd86","plugins\u002Fpolymath-observability\u002Fskills\u002Fauthor-monitor","https:\u002F\u002Fgithub.com\u002FMohammadBafkar\u002Fpolymath","https:\u002F\u002Fgithub.com\u002FMohammadBafkar","2026-10-29 18:34:59",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add MohammadBafkar\u002Fpolymath --skill author-monitor",{"tool":36,"command":37},"bunx","bunx skills add MohammadBafkar\u002Fpolymath --skill author-monitor",{"tool":39,"command":40},"pnpm","pnpm dlx skills add MohammadBafkar\u002Fpolymath --skill author-monitor","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FMohammadBafkar\u002Fpolymath\u002Fblob\u002Fmain\u002Fplugins\u002Fpolymath-observability\u002Fskills\u002Fauthor-monitor\u002FSKILL.md",true,[],[45,52,59,66,73,80],{"skillNo":46,"name":47,"nameZh":6,"description":48,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":49,"categories":50,"keywords":51,"publishedAt":19},"01M74GN87EBRHM9N87M7AP1HDD","runbook","Write or refresh an operational runbook for an alert\u002Fsymptom; structured as TL;DR + Pre-checks + Steps + Verification + Rollback + Escalation.","https:\u002F\u002Fgithub.com\u002FMohammadBafkar\u002Fpolymath\u002Fblob\u002Fmain\u002Fplugins\u002Fpolymath-writing\u002Fskills\u002Frunbook\u002FSKILL.md",[],[],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":19},"01M74GN5GPKEC1JEKP2DFQNEQJ","rfc","Draft a lightweight design RFC to docs\u002Frfcs\u002F\u003Cslug>.md; Summary, Motivation, Detailed design, Drawbacks, Alternatives, Unresolved questions. A proposal to debate, not a recorded decision (adr).","https:\u002F\u002Fgithub.com\u002FMohammadBafkar\u002Fpolymath\u002Fblob\u002Fmain\u002Fplugins\u002Fpolymath-writing\u002Fskills\u002Frfc\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M74GN2F4CWPMV4X09TG4E304","editorial-pass","Review and tighten prose in a Markdown artifact for a target tone (terse, formal, friendly) without dropping information; preserve quotations and load-bearing constraints.","https:\u002F\u002Fgithub.com\u002FMohammadBafkar\u002Fpolymath\u002Fblob\u002Fmain\u002Fplugins\u002Fpolymath-writing\u002Fskills\u002Feditorial-pass\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M74GMZWGYMZ37C4DYGT6P23G","architecture-review-facilitation","Run an architecture review as a process — entry criteria, reviewer checklist, decision log, and follow-up actions — pairing the design artifact with a red-team pass.","https:\u002F\u002Fgithub.com\u002FMohammadBafkar\u002Fpolymath\u002Fblob\u002Fmain\u002Fplugins\u002Fpolymath-writing\u002Fskills\u002Farchitecture-review-facilitation\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M74GMXVX0YX3ETDXS527XDGM","architecture-doc","Write a C4-style architecture document; System Context + Containers (+ Components when interesting) with mermaid diagrams. Describes structure, not a decision (adr) or proposal (rfc).","https:\u002F\u002Fgithub.com\u002FMohammadBafkar\u002Fpolymath\u002Fblob\u002Fmain\u002Fplugins\u002Fpolymath-writing\u002Fskills\u002Farchitecture-doc\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M74GMVG1WSMCK066S3KE6V5K","adr","Write an Architecture Decision Record (Michael Nygard format) to docs\u002Fadrs\u002FNNNN-\u003Cslug>.md; frontmatter validated by the ADR artifact schema. Records a made decision, not a proposal to debate (rfc).","https:\u002F\u002Fgithub.com\u002FMohammadBafkar\u002Fpolymath\u002Fblob\u002Fmain\u002Fplugins\u002Fpolymath-writing\u002Fskills\u002Fadr\u002FSKILL.md",[],[]]