Name: slo-architect
Rating: 75.2 (1 reviews)
Author: alirezarezvani

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.

Quality

94%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

The canonical home for this skill is slo-architect in alirezarezvani/claude-skills

Quality

Content

88%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-organized, highly actionable body with executable tooling and clear validation-gated workflows. The main weakness is that the referenced references/ and assets/ files are not present in the bundle, breaking the progressive-disclosure navigation, alongside minor redundancy in SLI-type listing.

Suggestions

Ship the referenced bundle files (references/slo_principles.md, sli_design.md, error_budget.md, composition.md and assets/slo_template.yaml, error_budget_policy.md) so the inline navigation links resolve.

De-duplicate the SLI-type catalog: keep it in either the slo_designer.py section or the SLI selection cheatsheet, not both.

Trim the motivational opener ('Most SLOs in the wild are arbitrary numbers...') to tighten token efficiency without losing the 'enforce discipline' framing.

Dimension	Reasoning	Score
Conciseness	Largely efficient and actionable, but includes minor over-explanation that could be trimmed — the motivational opener ('Most "SLOs" in the wild are arbitrary numbers no one believes') and SLI types listed redundantly in both the slo_designer section and the cheatsheet table.	4 / 5
Actionability	Provides fully executable, copy-paste-ready commands with concrete flags throughout — quick-start invocations, per-tool usage with --service/--sli-type/--target/--window-days, and PromQL-shaped alert output — covering the common cases.	5 / 5
Workflow Clarity	Three clearly sequenced workflows with explicit validation checkpoints, notably Workflow 1 step 9 ('Run slo_review.py — must pass before the SLO is "live"') and Workflow 2's fix-FAIL feedback loop, satisfying the validation requirement for these operations.	5 / 5
Progressive Disclosure	Well-structured with a clear overview and explicitly signaled one-level-deep references (References section plus inline 'See references/sli_design.md' pointers), but the referenced bundle files (references/.md, assets/.yaml) do not exist in the bundle, so the navigation the body promises is partially broken — a minor organization gap rather than a structural one.	4 / 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, third-person description that explicitly states both capability and trigger conditions, with rich natural-language trigger phrases and an explicit boundary against generic observability. Minor verbosity in the trailing '4 references on...' sentence but no over-claims.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete capabilities — '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)' — giving comprehensive coverage of what the skill ships.	5 / 5
Completeness	Explicitly answers both what ('Ships SLO designer, error-budget calculator... and SLO reviewer') and when ('Use when defining, reviewing, or operating SLOs/SLIs/error budgets... or any reliability-target question') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Enumerates natural trigger phrases users would actually say — 'define an SLO', 'what should our SLO be', 'error budget', 'burn rate', 'SLI', 'service level objective', 'Google SRE workbook', 'multi-window burn-rate alert' — covering synonyms and the specific technical vocabulary of the domain.	5 / 5
Distinctiveness Conflict Risk	Carves a clear niche and actively disambiguates — 'NOT a generic observability skill — specifically the SLO discipline' — with distinct triggers that minimize overlap with adjacent observability skills.	5 / 5
	Total	20 / 20 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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
referenced_paths_exist	Referenced path issues: 11 missing	Warning

	Total	14 / 16 Passed

Repository: alirezarezvani/claude-skills
Path: .gemini/skills/slo-architect/SKILL.md
Commit: 19392f7

Reviewed: ~5 hours 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.