CtrlK
BlogDocsLog inGet started
Tessl Logo

monitoring-apis

Build real-time API monitoring dashboards with metrics, alerts, and health checks. Use when tracking API health and performance metrics. Trigger with phrases like "monitor the API", "add API metrics", or "setup API monitoring".

74

Quality

93%

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

87%Weight 40%Scale 1-3

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

A well-crafted, dense, and actionable skill body that leverages progressive disclosure effectively via real reference files. Its main weakness is the lack of explicit validation/verification checkpoints within the build workflow.

Suggestions

Add an explicit verification step to the Instructions (e.g., 'Verify Prometheus is scraping `http_request_duration_seconds` and the Grafana dashboard shows data before defining alerts') to introduce a validate-then-proceed checkpoint.

Insert a feedback loop after alert rule creation (e.g., 'Fire a test alert to confirm PagerDuty/Slack routing works before relying on it in production') to raise workflow clarity from 2 to 3.

Consider one short executable snippet in the body (e.g., the minimal prom-client middleware) so the core deliverable is copy-paste ready without opening references.

DimensionReasoningScore

Conciseness

Lean and specific throughout — it lists exact metric names, histogram bucket arrays, and alert thresholds without explaining concepts Claude already knows (e.g., what Prometheus or a histogram is), so every token earns its place.

3 / 3

Actionability

Provides highly concrete, actionable guidance — specific metric names (`http_request_duration_seconds` with method/path/status labels), bucket values, alert thresholds, `/health` and `/ready` endpoint contracts, and concrete file outputs — rather than abstract descriptions; per the scoring notes, actionable instruction guidance is not penalized for lacking code blocks.

3 / 3

Workflow Clarity

The nine instructions are clearly sequenced (examine → instrument → endpoints → buckets → dashboards → alerts → synthetic → SLO), but there are no explicit inline validation checkpoints or verify-then-proceed feedback loops, matching the score-2 anchor where the sequence is present but checkpoints are missing or implicit.

2 / 3

Progressive Disclosure

The body is a concise overview that well-signals one-level-deep references to real files (implementation.md, errors.md, examples.md, all present in references/), keeping detail appropriately split for easy navigation.

3 / 3

Total

11

/

12

Passed

Description

100%Weight 40%Scale 1-3

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

A strong, well-formed description that clearly states capabilities, provides natural trigger phrases, and answers both 'what' and 'when' in third person. No first/second-person voice or vague fluff to penalize.

DimensionReasoningScore

Specificity

Names multiple concrete actions — 'Build real-time API monitoring dashboards with metrics, alerts, and health checks' — matching the score-3 anchor that lists several specific actions rather than vague language.

3 / 3

Completeness

Explicitly answers both what (build monitoring dashboards/metrics/alerts/health checks) and when ('Use when tracking API health and performance metrics' plus explicit trigger phrases), satisfying the score-3 anchor.

3 / 3

Trigger Term Quality

Provides natural trigger phrases a user would actually say ('monitor the API', 'add API metrics', 'setup API monitoring'), giving good coverage of common phrasings.

3 / 3

Distinctiveness Conflict Risk

API monitoring is a clear, specific niche with distinct triggers, making it unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

14

/

16

Passed

Repository
jeremylongshore/claude-code-plugins-plus-skills
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.