slo
Skill4 starsChanged 30 days agoMITView on GitHub
Guide SLI selection, SLO setting, and Error Budget management. Use when: defining service quality targets, setting up SLO-based alerting, Error Budget policy. Not for: instrumentation and metric collection — use /observability; responding to an active breach of the target — use /incident. Keywords: SLI, SLO, SLA, Error Budget, burn rate, service level.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- AsiaOstrich/universal-dev-standardsword for word, first seen Nov 4, 2026
Other versions1 project uses a version of this.
Word for word · 1
- AsiaOstrich/universal-dev-standards★ 84100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository55 other files it gives its agents.
- AGENTS.mdAGENTS.md
- ac-coverageSkill
- adrSkill
- ai-collaboration-standardsSkill
- ai-friendly-architectureSkill
- ai-instruction-standardsSkill
- api-designSkill
- atddSkill
- auditSkill
- bddSkill
- brainstormSkill
- changelogSkill
- checkinSkill
- ci-cdSkill
- code-reviewSkill
- commitSkill
- contract-testSkill
- databaseSkill
- deploySkill
- methodologySkill
- dev-workflowSkill
- docgenSkill
- documentation-guideSkill
- durableSkill
- e2eSkill
- error-code-guideSkill
- git-workflow-guideSkill
- incidentSkill
- journey-test-assistantSkill
- knowledge-graphSkill
- logging-guideSkill
- metricsSkill
- migrateSkill
- observabilitySkill
- orchestrateSkill
- planSkill
- prSkill
- discoverSkill
- project-structure-guideSkill
- pushSkill
- refactorSkill
- releaseSkill
- requirementSkill
- retrospectiveSkill
- reverseSkill
- runbookSkill
- securitySkill
- scanSkill
- skill-builderSkill
- spec-deriveSkill
- sddSkill
- sweepSkill
- tddSkill
- coverageSkill
- testing-guideSkill
The file
Files
SLO Assistant | SLO 助手
Language: English | 繁體中文
Guide SLI selection, SLO setting methodology, and Error Budget management.
引導 SLI 選取、SLO 設定方法論和 Error Budget 管理。
Capabilities | 功能
| Capability | Description | 說明 |
| SLI Selection | Guide SLI choice by service type (API/Batch/Frontend) | 按服務類型引導 SLI 選取 |
| SLO Setting | 5-step SLO setting methodology | 5 步驟 SLO 設定方法論 |
| Error Budget | Calculate budget, set burn rate alerts | 計算預算、設定 burn rate 告警 |
| SLO Document | Generate SLO specification document | 產生 SLO 規格文件 |
| SLO Review | Quarterly SLO review guide | 季度 SLO 審查引導 |
Usage | 使用方式
/slo # Show SLO guide
/slo create "payment-service" # Create SLO for service
/slo review # Quarterly SLO review
/slo budget # Error Budget calculationNext Steps Guidance | 下一步引導
SLO 引導完成。建議下一步:
- 執行
/observability --alerting設定 SLO-based 告警 ⭐ 推薦- 執行
/incident整合 SLO 影響評估- 執行
/checkin提交變更
Reference | 參考
- Detailed guide: guide.md — SLI/SLO/error-budget definition and management. Read it when defining SLOs, selecting SLIs, calculating error budgets, or setting reliability targets.
- Core standard: slo-standards.md
- Related: observability-standards.md
- Related: alerting-standards.md
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

