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

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

87%

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

The body is concise, highly actionable, and well-structured with appropriate progressive disclosure to real reference files. The main gap is the absence of explicit validation checkpoints within the build workflow.

Suggestions

Add an explicit validation/verification step to the Instructions workflow (e.g., 'Verify metrics are scraped: curl /metrics and confirm http_requests_total appears') and a validate->fix->retry loop after instrumentation.

Reconcile references/implementation.md and references/errors.md with the skill topic: implementation.md describes general API design/build steps and errors.md lists generic API errors (auth, rate limiting, schema validation) rather than monitoring-specific patterns, so the body's references point to partly off-topic material.

DimensionReasoningScore

Conciseness

The body is dense and lean, assuming Claude's competence (no explanations of what Prometheus, Grafana, or SLOs are); every line carries specific configuration detail rather than padding.

3 / 3

Actionability

Concrete, specific guidance throughout: exact metric names (http_request_duration_seconds, http_requests_total, http_requests_in_flight), label sets, histogram bucket arrays [0.01..10], alert thresholds, and /health and /ready endpoint shapes, with full executable code delegated one level deep to references/examples.md.

3 / 3

Workflow Clarity

The nine-step Instructions sequence is clearly ordered, but there are no explicit validation checkpoints or validate->fix->retry feedback loops embedded in the build workflow, which the rubric requires for a score of 3.

2 / 3

Progressive Disclosure

The body is a well-organized overview (Overview, Prerequisites, Instructions, Output, Error Handling, Examples, Resources) with clearly signaled, one-level-deep references (references/implementation.md, references/errors.md, references/examples.md) that exist as real files and are easy to navigate.

3 / 3

Total

11

/

12

Passed

Description

100%

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

The description is concise, specific, and uses appropriate third-person voice with explicit trigger guidance. It clearly conveys both capability and invocation conditions without fluff.

DimensionReasoningScore

Specificity

"Build real-time API monitoring dashboards with metrics, alerts, and health checks" lists multiple concrete actions (build dashboards, collect metrics, configure alerts, add health checks), matching the anchor for listing several specific actions.

3 / 3

Completeness

It clearly states what the skill does and includes an explicit "Use when tracking API health and performance metrics" trigger clause plus concrete trigger phrases, answering both what and when.

3 / 3

Trigger Term Quality

Phrases "monitor the API", "add API metrics", "setup API monitoring", and "tracking API health and performance metrics" give good coverage of natural terms a user would actually say, beyond technical jargon.

3 / 3

Distinctiveness Conflict Risk

The API monitoring dashboard niche with metric/alert/health-check triggers is clearly distinguishable and 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.