monitoring-and-alerting

Design and run a monitoring system for a website or web app. Use this skill when setting up uptime checks, defining SLOs, configuring error tracking, choosing what to alert on, designing on-call rotations, or fixing alert fatigue. Triggers on monitoring, alerts, uptime, SLO, SLA, error rate, on-call, pager, alert fatigue, observability, dashboards, what should we monitor. Also triggers when an incident reveals a gap in monitoring.

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

81%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A strong, well-structured body: clear 4-layer mental model, an 8-step workflow with audit/validation checkpoints, a rich failure-patterns section, and a sanctioned 'state the gap' fallback. Slightly verbose in places that restate common knowledge, and progressive disclosure could offload more detail to the existing reference file.

Suggestions

Trim definitional asides Claude already knows (e.g., 'The error budget is the inverse', explanatory restatement of Core Web Vitals) to raise conciseness.

Move the SLO downtime table and per-box layer-mapping table into references/slo-design-guide.md to deepen progressive disclosure and keep the body as an overview.

Add one or two concrete tool-config snippets (e.g., a sample PagerDuty/Slack routing rule or a synthetic-check definition) to lift actionability from mostly- to fully-executable.

Dimension	Reasoning	Score
Conciseness	Largely lean and assumes Claude's competence, but several passages restate widely-known concepts (e.g., explaining what an SLO is, what 'the error budget is the inverse', the meaning of Core Web Vitals) that could be trimmed to tighten token use.	4 / 5
Actionability	Concrete, specific guidance throughout — thresholds ('5xx rate above 1% for 5 minutes'), concrete check types, a per-box layer table, and tiered routing rules — with only minor gaps such as no copy-paste config snippets for specific tools.	4 / 5
Workflow Clarity	An explicit 8-step workflow with clear sequencing and validation checkpoints — Step 8's quarterly alert audit functions as a feedback/validation loop, and the 'If required data is unavailable' section sanctions stating gaps rather than fabricating.	5 / 5
Progressive Disclosure	Well-organized sections with one clearly signaled one-level-deep reference (references/slo-design-guide.md, confirmed present), but most supporting detail (SLO table, per-box check table) is inlined rather than split into separate files; structure is good but could push more to references.	4 / 5
	Total	17 / 20 Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

An excellent description: concrete actions, comprehensive natural trigger terms, explicit what-and-when guidance, and a distinct niche that minimizes conflict risk. It is in third person throughout, satisfying the voice requirement.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'setting up uptime checks, defining SLOs, configuring error tracking, choosing what to alert on, designing on-call rotations, or fixing alert fatigue' — giving comprehensive coverage of the skill's capabilities.	5 / 5
Completeness	Clearly states what it does ('Design and run a monitoring system...') and when to use it via explicit 'Use this skill when...' and 'Triggers on...' clauses with concrete trigger phrases.	5 / 5
Trigger Term Quality	Comprehensive natural trigger terms including synonyms and abbreviations: 'monitoring, alerts, uptime, SLO, SLA, error rate, on-call, pager, alert fatigue, observability, dashboards' — all phrases a user would naturally say.	5 / 5
Distinctiveness Conflict Risk	Clear niche (web monitoring/SLOs/on-call) with distinct triggers; minimal conflict risk — the domain-specific terms (SLO, on-call, pager, alert fatigue) distinguish it from incident-response or analytics skills.	5 / 5
	Total	20 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: rampstackco/claude-skills
Path: skills/monitoring-and-alerting/SKILL.md
Commit: 0479242

Reviewed: 14 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.