CtrlK
BlogDocsLog inGet started
Tessl Logo

slo-architect

Use when defining, reviewing, or operating SLOs/SLIs/error budgets. Triggers on "define an SLO", "what should our SLO be", "error budget", "burn rate", "SLI", "service level objective", "Google SRE workbook", "multi-window burn-rate alert", or any reliability-target question. Ships SLO designer, error-budget calculator with multi-window burn-rate thresholds, and SLO reviewer that catches the common bugs (target too aggressive, window too short, conflicting SLOs, no SLI definition). 4 references on SLO principles + SLI design + error budget math + composition with feature-flags-architect/chaos-engineering/kubernetes-operator. NOT a generic observability skill — specifically the SLO discipline.

74

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

The risk profile of this skill

SKILL.md
Quality
Evals
Security

Quality

Content

85%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 highly actionable, well-structured body with executable commands, explicit validation checkpoints, and clean one-level-deep references. The main weakness is mild redundancy where the cardinal mistakes and burn-rate math are restated across sections.

Suggestions

Consolidate the four cardinal mistakes and the Anti-patterns list into a single section to remove overlap, or have the Anti-patterns list cross-reference the Core principle section instead of restating it.

Remove the standalone 'Error budget math' section or fold its worked example into the error_budget_calculator.py description, since the math is already covered there.

The 'Quick start' examples duplicate the per-tool command blocks below them; consider keeping only one canonical invocation per tool to trim tokens.

DimensionReasoningScore

Conciseness

Mostly efficient and assumes Claude's knowledge, but the cardinal mistakes reappear as the Anti-patterns list, and the burn-rate math is restated in both the tool description and its own 'Error budget math' section, so it could be tightened.

3 / 5

Actionability

Fully executable copy-paste commands with concrete flags, exact multi-window burn-rate thresholds, worked numeric formulas, and PromQL-shaped alert output covering the common cases.

5 / 5

Workflow Clarity

Three numbered workflows with clear sequencing and an explicit validation checkpoint in Workflow 1 ('Run slo_review.py — must pass before the SLO is live'), plus a feedback loop in Workflow 2 (fix FAIL findings before committing revised SLOs).

5 / 5

Progressive Disclosure

Clear overview in the body with well-signaled, one-level-deep references to verified real files under references/, assets/, and scripts/; each reference is annotated with its purpose and navigation is easy.

5 / 5

Total

18

/

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, specific description that clearly states what the skill ships, when to trigger it via natural phrases, and how it differs from adjacent observability skills. It uses correct third-person voice and avoids vague fluff.

DimensionReasoningScore

Specificity

Names multiple concrete actions and tools — 'Ships SLO designer, error-budget calculator with multi-window burn-rate thresholds, and SLO reviewer that catches the common bugs (target too aggressive, window too short, conflicting SLOs, no SLI definition)' — comprehensive coverage of what each does.

5 / 5

Completeness

Explicitly answers both what (three named tools and the bugs they catch) and when ('Use when defining, reviewing, or operating SLOs/SLIs/error budgets') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Comprehensive natural triggers including synonyms and phrasings users actually say — 'define an SLO', 'what should our SLO be', 'error budget', 'burn rate', 'SLI', 'service level objective', 'multi-window burn-rate alert'.

5 / 5

Distinctiveness Conflict Risk

Clear niche with an explicit boundary statement ('NOT a generic observability skill — specifically the SLO discipline') and distinct, domain-specific triggers that minimize overlap risk.

5 / 5

Total

20

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
alirezarezvani/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.