Slo design

Skill srg-sphynx/MDForge/Sources/MDForge/Resources/SkillLibrary/Business & Ops/slo-design

Native macOS skill-catalog studio for Claude Code — browse 1,492 Markdown skills, customize with variables or AI (hosted or local), export to .claude/skills. SwiftUI + Liquid Glass.

Install

npx -y skills add srg-sphynx/MDForge --skill slo-design

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Interactive wizard to design an SLO with SLI, target, error budget, and burn-rate alerts

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

2.0 KB, 508 tokens by cl100k_base, as published. Nobody here has run it

/slo-design

Step through SLO design using the slo-architect skill. Produces an SLO definition, computes error budget + multi-window burn-rate alerts, and runs the reviewer to catch common bugs.

Usage

/slo-design
/slo-design --service checkout-svc --sli-type request-success-rate --target 99.9

Implementation

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

# Step 1: gather inputs (service, sli-type, target, window, owner)
# Step 2: render SLO definition
python "$SKILL/scripts/slo_designer.py" \
  --service "$SERVICE" \
  --sli-type "$SLI_TYPE" \
  --target "$TARGET" \
  --window-days "$WINDOW_DAYS" \
  --owner "$OWNER" \
  --policy-doc "$POLICY_DOC" \
  --format json > .slo.json

# Step 3: compute error budget + burn-rate alerts
python "$SKILL/scripts/error_budget_calculator.py" \
  --target "$TARGET" \
  --window-days "$WINDOW_DAYS"

# Step 4: render the markdown SLO for peer review
python "$SKILL/scripts/slo_designer.py" \
  --service "$SERVICE" \
  --sli-type "$SLI_TYPE" \
  --target "$TARGET" \
  --window-days "$WINDOW_DAYS" \
  --owner "$OWNER" \
  --policy-doc "$POLICY_DOC"

# Step 5: validate against the reviewer
echo "=== After saving the SLO, run slo_review.py against the doc ==="

Output

A markdown SLO definition with:

Service, owner, user journey
SLI type with numerator/denominator expressions
Target, window, error budget
Multi-window burn-rate alert thresholds (PromQL-shaped)
Review cadence

Pre-conditions

slo-architect skill installed
Service identified
30 days of historical SLI data available (to pick a sustainable target)
Error budget policy doc exists or will be created

Post-conditions

.slo.json written for use with downstream tools (chaos-engineering blast radius, etc.)
Markdown SLO streamed for review
Recommendation printed: PASS / WARN / FAIL on slo_review.py checks