tracking-service-reliability
This skill enables Claude to define and track Service Level Agreements (SLAs), Service Level Indicators (SLIs), and Service Level Objectives (SLOs) for improved service reliability. It is triggered when the user needs to establish, monitor, or analyze service performance metrics. Use this skill when the user mentions "SLA", "SLI", "SLO", "error budget", "service reliability", or "track service performance". The skill helps to define key metrics, set targets, and monitor performance against those targets.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill tracking-service-reliability56
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a well-structured skill description with excellent trigger term coverage and clear 'when to use' guidance. The main weakness is that the capability descriptions are somewhat generic ('define', 'track', 'monitor') rather than listing specific concrete actions like 'calculate error budgets', 'generate SLO compliance reports', or 'alert on SLA breaches'.
Suggestions
Add more specific concrete actions such as 'calculate error budgets', 'generate compliance reports', 'set up alerting thresholds', or 'analyze burn rate' to improve specificity
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (SLAs/SLIs/SLOs) and mentions actions like 'define', 'track', 'monitor', 'analyze', but these are somewhat generic. The phrase 'define key metrics, set targets, and monitor performance' adds some specificity but lacks concrete examples of what those metrics or targets look like. | 2 / 3 |
Completeness | Clearly answers both what ('define and track SLAs, SLIs, SLOs', 'define key metrics, set targets, monitor performance') and when ('Use this skill when the user mentions...' with explicit trigger terms). Has an explicit 'Use when' clause. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms including 'SLA', 'SLI', 'SLO', 'error budget', 'service reliability', and 'track service performance'. These are terms users would naturally use when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | The focus on SLA/SLI/SLO terminology and error budgets creates a clear niche. These are specific reliability engineering concepts that wouldn't overlap with general monitoring or metrics skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
20%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill content reads like a marketing description rather than actionable guidance. It explains what SLAs/SLIs/SLOs are and describes what the skill 'will do' without providing any concrete templates, formulas, code examples, or specific implementation steps that Claude could actually execute.
Suggestions
Replace abstract descriptions with concrete templates (e.g., a YAML/JSON schema for defining SLIs and SLOs with example values)
Add executable code or commands for calculating error budgets (e.g., `error_budget = 1 - slo_target` with a worked example)
Provide a specific SLO definition template with real values instead of describing what the skill 'will prompt' the user for
Remove explanatory content about what SLAs/SLIs/SLOs are - Claude already knows these concepts
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is verbose and explains concepts Claude already knows (what SLAs, SLIs, SLOs are). Phrases like 'which are essential for ensuring service reliability' and 'enabling proactive identification and resolution of potential issues' add no actionable value. | 1 / 3 |
Actionability | The skill provides no concrete code, commands, or executable guidance. It describes what the skill 'will do' abstractly (e.g., 'guide the user', 'assist in setting') rather than providing actual templates, formulas, or implementation details. | 1 / 3 |
Workflow Clarity | Steps are listed (SLI Definition → SLO Target Setting → SLA Establishment) but lack concrete validation checkpoints or specific actions. The examples describe outcomes without showing how to actually achieve them. | 2 / 3 |
Progressive Disclosure | Content is organized into sections but everything is inline with no references to detailed materials. The 'Integration' section mentions monitoring tools but provides no links or specific guidance. | 2 / 3 |
Total | 6 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 13 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
body_output_format | No obvious output/return/format terms detected; consider specifying expected outputs | Warning |
Total | 13 / 16 Passed | |
- 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.