CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

84%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

67%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 instruction-only skill: concrete decision rules, a clear 8-step workflow, and a genuine one-level reference file. The main costs are token weight from re-teaching SLO basics Claude already knows (duplicating the reference file), inline time-sensitive vendor information, and the absence of an explicit post-configuration validation step or worked alert example.

Suggestions

Trim the 'SLOs and error budgets' section to the decision guidance (which SLO to pick, how to use budgets) and move the SLO definition, component breakdown, and nines-to-downtime table into references/slo-design-guide.md, which already covers that ground.

Move the Opsgenie end-of-sales/support dates into a short 'Deprecated vendors' subsection so time-sensitive information is quarantined from the routing guidance.

Add an explicit validation step after Step 6 (Configure routing), e.g., 'Fire a test alert through the paging system and confirm the on-call receives and acks it,' to close the workflow's validation gap.

DimensionReasoningScore

Conciseness

Most of the body is dense, opinionated guidance Claude would not generate on its own (thresholds, tiering rules, failure patterns), but the SLO section re-explains concepts Claude already knows — 'A Service Level Objective is the target for reliability', the nines-to-downtime table, 'The error budget is the inverse' — and time-sensitive version info (Opsgenie sales/support end dates) sits inline in Step 6 rather than in a deprecation section. More than minor trimming is needed, matching anchor 3 rather than the 'minor instances' of anchor 4.

3 / 5

Actionability

As an instruction-only skill the guidance is highly concrete: specific thresholds ('more than 2 consecutive failed checks', 'Error rate above 1% for 5 minutes', 'ack within 5-15 minutes'), a per-box check matrix, named routing tools, and a three-tier decision scheme. It falls short of anchor 5 only in that no worked tool-specific example (e.g., a sample alert rule or check configuration) is provided to cover the most common configuration cases.

4 / 5

Workflow Clarity

The 8-step workflow is clearly sequenced with a feedback loop (quarterly alert audit in Step 8) and explicit quality criteria for paging alerts, but there is no in-workflow validation checkpoint such as 'fire a test alert to verify routing and paging actually work' after Step 6. Clear sequence with a minor validation gap matches anchor 4; the destructive/batch cap does not apply to this design skill.

4 / 5

Progressive Disclosure

The body is well-sectioned with one well-signaled, one-level-deep reference (references/slo-design-guide.md, verified to exist and match its description). However, the body's SLO section duplicates the reference file's opening material (both explain what an SLO is and its components), so the split between overview and deep-dive could be cleaner — good structure with minor organization gaps, matching anchor 4 rather than the appropriately-split anchor 5.

4 / 5

Total

15

/

20

Passed

Description

96%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 exemplary description: concrete third-person capability statement, explicit 'Use this skill when' triggers with a rich keyword list including synonyms and a natural user question, and a clearly delimited niche. The only weakness is that 'dashboards' and 'observability' as trigger terms invite overlap with adjacent analytics/logging skills.

DimensionReasoningScore

Specificity

The description lists six concrete actions ('setting up uptime checks, defining SLOs, configuring error tracking, choosing what to alert on, designing on-call rotations, or fixing alert fatigue') that comprehensively cover the web-monitoring domain, in third-person voice. It matches the anchor-5 example's breadth without the minor coverage gaps that would place it at 4.

5 / 5

Completeness

It explicitly answers both what ('Design and run a monitoring system for a website or web app') and when ('Use this skill when...' plus 'Also triggers when an incident reveals a gap in monitoring') with concrete trigger phrases. Both clauses are explicit and specific, matching the anchor-5 example exactly; anchor 4 would require a merely adequate 'when' clause.

5 / 5

Trigger Term Quality

Trigger terms include natural keywords and their synonyms ('monitoring, alerts, uptime, SLO, SLA, error rate, on-call, pager, alert fatigue, observability, dashboards') plus a verbatim user question ('what should we monitor'). Coverage is comprehensive with synonym variants and colloquial terms, matching anchor 5 rather than the 'a few natural terms missing' of anchor 4.

5 / 5

Distinctiveness Conflict Risk

Monitoring/alerting is a clear niche with mostly distinct triggers, but 'dashboards' and 'observability' are broad terms with overlap risk against analytics and logging skills — indeed the body's 'When NOT to use' section has to disclaim analytics dashboards. Minor overlap risk with closely related skills matches anchor 4 rather than the minimal-conflict anchor 5.

4 / 5

Total

19

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

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

Reviewed

Table of Contents

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.