tracking-service-reliability

Define and track SLAs, SLIs, and SLOs for service reliability including availability, latency, and error rates. Use when establishing reliability targets or monitoring service health. Trigger with phrases like "define SLOs", "track SLI metrics", or "calculate error budget".

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

35%

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

The body is well-sectioned but largely conceptual: it pads with restated definitions, gives abstract instructions with no executable examples, and omits validation steps and links to the bundled scripts that already exist. Tightening prose and adding concrete, linked guidance would substantially improve it.

Suggestions

Replace the Overview/How It Works prose with lean directives and remove restatements of what SLIs/SLOs/SLAs are; assume Claude already knows these concepts.

Add concrete, executable guidance — show how to invoke the bundled scripts (e.g. `python scripts/generate_sla_report.py`) and reference the existing calculate_error_budget.py and monitor_sli.py rather than describing them abstractly.

Insert validation checkpoints into the workflow (e.g. verify SLI definitions are complete and validate collected metrics before computing error budgets) so each step has a pass/fail gate.

Dimension	Reasoning	Score
Conciseness	The Overview and How It Works sections restate the description and explain concepts Claude already knows ('SLIs such as availability, latency, error rate'), adding padding rather than lean instruction; not a full wall of condescension, so above the bottom anchor.	2 / 3
Actionability	The Instructions are abstract directives ('Define Service Level Indicators', 'Set Service Level Objectives') with no executable code or commands; it describes rather than instructs, matching the vague/abstract anchor.	1 / 3
Workflow Clarity	A six-step sequence is present (define → set → formalize → configure → calculate → track) but there are no validation checkpoints or feedback loops, fitting the 'steps listed but validation gaps' anchor.	2 / 3
Progressive Disclosure	The body is organized into sections but keeps all detail inline and never signals the existing bundle scripts (e.g. generate_sla_report.py), so references are present-but-not-linked rather than well-signaled.	2 / 3
	Total	7 / 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 strong across the board: it states concrete capabilities, gives explicit 'Use when' guidance plus natural trigger phrases, uses third person, and occupies a distinct niche. No meaningful gaps to address.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ('Define and track SLAs, SLIs, and SLOs') across specific metrics ('availability, latency, and error rates'), matching the anchor for listing several specific concrete actions.	3 / 3
Completeness	Explicitly answers both what ('Define and track SLAs, SLIs, and SLOs...') and when ('Use when establishing reliability targets or monitoring service health') with explicit triggers, satisfying the top anchor.	3 / 3
Trigger Term Quality	Provides natural trigger phrases a user would actually say ('define SLOs', 'track SLI metrics', 'calculate error budget'), giving good coverage rather than jargon.	3 / 3
Distinctiveness Conflict Risk	Targets a clear niche (SLA/SLI/SLO reliability tracking) with distinct triggers unlikely to conflict with other skills.	3 / 3
	Total	12 / 12 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
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
Commit: 3022dd3

Reviewed: 2 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.