slo-management
Use this skill when working with Elastic SLOs (Service Level Objectives). Activate when the user asks about SLO status, burn rates, error budgets, or needs to create and manage SLO definitions.
65
77%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./packages/opencode/src/elastic/skills/slo-management/SKILL.mdQuality
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.
The description is well-structured with explicit 'when to use' guidance and strong domain-specific trigger terms that make it highly distinguishable. Its main weakness is that the capability listing could be more specific—enumerating concrete actions beyond 'create and manage' would strengthen it. The use of second person ('Use this skill when') is borderline but functions as instructional voice rather than conversational second person.
Suggestions
Expand the specific capabilities beyond 'create and manage SLO definitions'—list concrete actions like 'query SLO summaries, check remaining error budget, configure burn rate alerts, update SLO targets' to improve specificity.
Rephrase to third person voice (e.g., 'Manages Elastic SLOs including checking status, burn rates, and error budgets. Creates and configures SLO definitions. Use when...').
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain (Elastic SLOs) and mentions some actions like 'create and manage SLO definitions' and checking 'SLO status, burn rates, error budgets,' but doesn't list multiple concrete specific actions comprehensively (e.g., no mention of editing, deleting, querying, alerting, or specific API operations). | 2 / 3 |
Completeness | Clearly answers both 'what' (working with Elastic SLOs, SLO status, burn rates, error budgets, creating and managing SLO definitions) and 'when' (explicit 'Use this skill when...' and 'Activate when...' clauses with specific trigger scenarios). | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms that users would actually say: 'SLO status', 'burn rates', 'error budgets', 'SLO definitions', 'Service Level Objectives', and 'Elastic SLOs'. These cover the key vocabulary a user working with Elastic SLOs would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | The description is clearly scoped to Elastic SLOs specifically, with domain-specific terms like 'burn rates', 'error budgets', and 'SLO definitions' that are unlikely to conflict with other skills. The 'Elastic' qualifier further narrows the niche. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill provides good actionable commands and a useful ES|QL query, but is weighed down by explanatory content about concepts Claude already understands (SLI, error budgets, burn rates). The workflow could be improved by connecting the individual commands into a coherent investigation sequence. The best practices section is generic SRE advice that doesn't add tool-specific value.
Suggestions
Remove or drastically shorten the 'Key Concepts' section — Claude already knows what SLIs, error budgets, and burn rates are.
Remove or condense the 'Best Practices for SREs' section, which is generic advice not specific to the Elastic CLI tooling.
Add a sequenced investigation workflow: e.g., 1) List SLOs → 2) Identify breached/degraded → 3) Query rollup data for that SLO → 4) Drill into root cause, with specific commands at each step.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The 'Key Concepts' section explains SLI, SLO target, error budget, and burn rate — concepts Claude already knows well. The 'Best Practices for SREs' section is generic advice that doesn't add skill-specific value. The commands and ES|QL query are efficient, but the surrounding explanatory content could be trimmed significantly. | 2 / 3 |
Actionability | Provides concrete, copy-paste ready CLI commands (`elastic slos list`, `elastic slos list-definitions`) and a fully executable ES|QL query with specific index patterns and field names. The status interpretation table gives clear, actionable guidance for each state. | 3 / 3 |
Workflow Clarity | The skill presents individual commands clearly but lacks a sequenced workflow connecting them. There's no guidance on what to do after identifying a breached SLO (e.g., drill down with ES|QL query, then investigate specific services). The best practices section mentions alerting on burn rates but doesn't show how to set that up. No validation or feedback loops are present. | 2 / 3 |
Progressive Disclosure | Content is reasonably organized with clear section headers, but everything is inline in a single file. The best practices and key concepts sections add bulk that could be separated or omitted. With no bundle files, there are no references to external resources, but the skill is short enough that this is borderline acceptable — however the explanatory sections inflate it beyond what's needed inline. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- elastic/elastic-ramen
- Commit
2e200ec
- 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.