mirror of https://github.com/alirezarezvani/claude-skills.git synced 2026-09-06 08:15:58 +00:00

History

Claude 028dc13b35 feat(tooling): JSON-output sample gate (G9) + --sample fixtures (#654 ) Implements issue #654 Option A (embedded-sample convention) plus the verification harness the issue asked for: - scripts/smoke_json_output.py — new advisory gate (G9) that discovers every tool whose --help advertises JSON output, runs <tool> --sample <json-flag>, and asserts the stdout parses as JSON. Tools advertising JSON without --sample are reported as 'uncovered' (a backlog, not a failure) so the gate can be adopted incrementally; --strict flips that to a hard failure once coverage is high. Wired into ci-quality-gate.yml alongside G8. - Added --sample embedded fixtures to the 5 tools named in #654: error_budget_calculator, slo_review, blast_radius_calculator, audit_log_analyzer, api_linter. Their required args are now optional when --sample is passed; missing-arg behavior is unchanged otherwise. - Fixed 4 tools the new gate surfaced (prompt_rater, coach_tip_classifier, cheat_code_filter, redaction_linter): their --sample path printed human text and ignored --json; it now honors the JSON flag. - Synced the 3 dual-published standalone copies (slo-architect x2, chaos-engineering) so the drift guard stays green. Gate now reports 16 tools covered, 16 verified, 0 failures. https://claude.ai/code/session_01CUWsrUNZP9jpxvAwq67UiT		2026-06-11 15:29:39 +00:00
..
.claude-plugin	chore(versioning,docs): normalize stale versions to 2.9.0 + refresh counts	2026-05-27 05:22:59 +00:00
skills/slo-architect	feat(tooling): JSON-output sample gate (G9) + --sample fixtures (#654 )	2026-06-11 15:29:39 +00:00
README.md	feat(slo-architect): Phase 4 — SLO/SLI/error-budget discipline (#605 )	2026-05-10 07:39:05 +02:00

README.md

SLO Architect

Define SLOs that mean something. Most "SLOs" in the wild are arbitrary numbers nobody believes — 99.9% on every endpoint, no SLI definition, no error budget policy. This skill enforces the Google SRE Workbook discipline.

What's inside

3 stdlib Python tools — SLO designer, error-budget calculator with multi-window burn-rate alerts, SLO reviewer
4 reference docs — principles, SLI design, error budget, composition
2 asset templates — SLO YAML, error budget policy
/slo-design slash command

Install

# Via Claude Code marketplace
/plugin install slo-architect

# Or clone the repo
git clone https://github.com/alirezarezvani/claude-skills.git
cd claude-skills/engineering/slo-architect

Quick start

SKILL=engineering/slo-architect/skills/slo-architect

# 1. Design an SLO
python "$SKILL/scripts/slo_designer.py" \
  --service checkout-svc --sli-type request-success-rate \
  --target 99.9 --window-days 28

# 2. Compute error budget + multi-window burn-rate alerts
python "$SKILL/scripts/error_budget_calculator.py" --target 99.9 --window-days 28

# 3. Review existing SLOs for common bugs
python "$SKILL/scripts/slo_review.py" --slo-doc docs/slos/

Key principles

An SLO is a promise about user experience — not a CPU graph
Pick the SLI from the user's perspective — request-success / latency / availability / freshness / correctness
Pick the target from data — measure 30 days, then floor it
Multi-window burn-rate alerts — single-window is either too noisy or too slow
Error budget without a policy is theater — every SLO ships with a policy

The 5 SLI types

User experience	SLI type
"Did the request succeed?"	request-success-rate
"Was the response fast?"	request-latency
"Was the service up?"	availability-time
"Is the data current?"	data-freshness
"Was the answer correct?"	correctness

Composition with the rest of the portfolio

Skill	Composition
`feature-flags-architect`	Rollout abort criteria reference SLO burn-rate thresholds
`chaos-engineering`	Blast-radius calculator takes monthly error budget as input
`kubernetes-operator`	Operator capability L4 requires SLOs + Prometheus rules

Skill structure

slo-architect/
├── README.md
├── .claude-plugin/plugin.json
└── skills/slo-architect/
    ├── SKILL.md
    ├── scripts/
    │   ├── slo_designer.py
    │   ├── error_budget_calculator.py
    │   └── slo_review.py
    ├── references/
    │   ├── slo_principles.md
    │   ├── sli_design.md
    │   ├── error_budget.md
    │   └── composition.md
    └── assets/
        ├── slo_template.yaml
        └── error_budget_policy.md

Verifiable success

A team using this skill should achieve:

100% of SLOs pass slo_review.py with 0 FAIL findings
Every SLO has a documented owner, error budget, burn-rate alerts, and policy
Burn-rate alerts fire ≤2 times/month per SLO that's hit
Mean time to detect SLO violation: <30 min
Quarterly SLO review actually happens

License

MIT — see repo root LICENSE.