CtrlK
BlogDocsLog inGet started
Tessl Logo

sre-engineer

Defines service level objectives, creates error budget policies, designs incident response procedures, develops capacity models, and produces monitoring configurations and automation scripts for production systems. Use when defining SLIs/SLOs, managing error budgets, building reliable systems at scale, incident management, chaos engineering, toil reduction, or capacity planning.

77

Quality

96%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Failed to scan

The risk profile of this skill

SKILL.md
Quality
Evals
Security

Quality

Content

92%Weight 40%Scale 1-5

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

A well-structured SRE skill body that pairs an actionable, checkpointed workflow with executable Prometheus, PromQL, and Python examples, and cleanly offloads deeper detail to five clearly-signaled reference files. The only weakness is minor verbosity in the worked calculation example and inline comments.

Suggestions

Trim the arithmetic commentary in the SLO error-budget calculation block (e.g., the step-by-step downtime/error-budget derivation) to the essential formula and result, trusting Claude to do the math.

Reduce or remove the module docstring and inline restating comments in the Python automation example so the code is leaner while still executable.

DimensionReasoningScore

Conciseness

Mostly efficient and assumes Claude's competence (no padding about what SRE or Prometheus is), but the worked SLO calculation block and inline script docstrings spell out arithmetic and basics that could be trimmed.

4 / 5

Actionability

Fully executable, copy-paste-ready artifacts: a multiwindow Prometheus SLO alerting rule, PromQL golden-signal queries, and a complete Python auto-remediation script with real logic.

5 / 5

Workflow Clarity

A six-step sequenced workflow with explicit validation checkpoints ('Confirm SLO targets reflect user expectations before proceeding', 'verify recovery meets RTO/RPO targets before marking complete', 'validate recovery behavior end-to-end').

5 / 5

Progressive Disclosure

Clear overview with a Reference Guide table pointing to five real one-level-deep reference files (verified present in references/), each with a 'Load When' navigation column, keeping concrete examples inline appropriately.

5 / 5

Total

19

/

20

Passed

Description

100%Weight 40%Scale 1-5

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 description that concisely states concrete capabilities and provides explicit, comprehensive 'Use when' trigger guidance in third-person voice. It is specific, complete, and well-distinguished from adjacent skills.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ('Defines service level objectives, creates error budget policies, designs incident response procedures, develops capacity models, and produces monitoring configurations and automation scripts') covering the SRE domain comprehensively.

5 / 5

Completeness

Explicitly answers both 'what' (defines SLOs, error budget policies, incident response, capacity models, monitoring, automation) and 'when' ('Use when defining SLIs/SLOs, managing error budgets...') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Comprehensive natural trigger terms users actually say: 'SLIs/SLOs, error budgets, building reliable systems at scale, incident management, chaos engineering, toil reduction, capacity planning', including common synonyms.

5 / 5

Distinctiveness Conflict Risk

Clear SRE niche with distinct triggers (SLOs, error budgets, chaos engineering, toil) and only minor overlap risk with related devops skills.

5 / 5

Total

20

/

20

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
jeffallan/claude-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.