claude-skills__.gemini__skills__slo-design
Interactive wizard to design an SLO with SLI, target, error budget, and burn-rate alerts
- License 许可
- MIT
- 所属仓库
- agisota/old-one
- 最近更新
- 2026-07-04
- Stars
- ★ 3
- Forks
- 1
01 前言 Front Matter
- description
- Interactive wizard to design an SLO with SLI, target, error budget, and burn-rate alerts
03 SKILL.md 正文
/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-architectskill 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.jsonwritten for use with downstream tools (chaos-engineering blast radius, etc.)- Markdown SLO streamed for review
- Recommendation printed: PASS / WARN / FAIL on
slo_review.pychecks
04 同仓库更多 Skills
zoom-out
Tell the agent to zoom out and give broader context or a higher-level perspective. Use when you're unfamiliar with a section of code or need to understand how it fits into the bigger picture.
zeroize-audit
Detects missing zeroization of sensitive data in source code and identifies zeroization removed by compiler optimizations, with assembly-level analysis, and control-flow verification. Use for auditing C/C++/Rust code handling secrets, keys, passwords, or other sensitive data.
yeet
Use only when the user explicitly asks to stage, commit, push, and open a GitHub pull request in one flow using the GitHub CLI (`gh`).
yara-rule-authoring
Guides authoring of high-quality YARA-X detection rules for malware identification. Use when writing, reviewing, or optimizing YARA rules. Covers naming conventions, string selection, performance optimization, migration from legacy YARA, and false positive reduction. Triggers on: YARA, YARA-X, malware detection, threat hunting, IOC, signature, crx module, dex module.
x-twitter-growth
X/Twitter growth engine for building audience, crafting viral content, and analyzing engagement. Use when the user wants to grow on X/Twitter, write tweets or threads, analyze their X profile, research competitors on X, plan a posting strategy, or optimize engagement. Complements social-content (generic multi-platform) with X-specific depth: algorithm mechanics, thread engineering, reply strategy, profile optimization, and competitive intelligence via web search.
x-api
X/Twitter API integration for posting tweets, threads, reading timelines, search, and analytics. Covers OAuth auth patterns, rate limits, and platform-native content posting. Use when the user wants to interact with X programmatically.