slo

Solid

引導 SLI 選取、SLO 設定與 Error Budget 管理。 Use when: 定義服務品質目標、建立以 SLO 為基礎的告警、Error Budget 政策。 Not for: 埋點與指標收集——請用 /observability；處理正在違反目標的狀況——請用 /incident。 Keywords: SLI, SLO, SLA, Error Budget, burn rate, service level, 服務等級, 錯誤預算, 燃燒率, 服務品質目標.

Code & Development 71 stars 13 forks Updated today NOASSERTION

Install

View on GitHub

Quality Score: 79/100

Stars 20%
62
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
46
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# SLO 助手 > **語言**: [English](../../../../skills/slo-assistant/SKILL.md) | 繁體中文 引導 SLI 選取、SLO 設定方法論和 Error Budget 管理。 ## 功能 | 功能 | 說明 | |------|------| | **SLI 選取** | 按服務類型引導 SLI 選取（API/Batch/Frontend） | | **SLO 設定** | 5 步驟 SLO 設定方法論 | | **Error Budget** | 計算預算、設定 burn rate 告警 | | **SLO 文件** | 產生 SLO 規格文件 | | **SLO 審查** | 季度 SLO 審查引導 | ## 使用方式 ```bash /slo # 顯示 SLO 指南 /slo create "payment-service" # 為服務建立 SLO /slo review # 季度 SLO 審查 /slo budget # Error Budget 計算 ``` ## 下一步引導 > **SLO 引導完成。建議下一步：** > - 執行 `/observability --alerting` 設定 SLO-based 告警 ⭐ **推薦** > - 執行 `/incident` 整合 SLO 影響評估 > - 執行 `/checkin` 提交變更 ## 參考 - 核心規範：[slo-standards.md](../../../../core/slo-standards.md) - 相關：[observability-standards.md](../../../../core/observability-standards.md) - 相關：[alerting-standards.md](../../../../core/alerting-standards.md)

Details

Author
AsiaOstrich
Repository
AsiaOstrich/universal-dev-standards
Created
8 months ago
Last Updated
today
Language
JavaScript
License
NOASSERTION

Bundled in these plugins

universal-dev-standards

Similar Skills

Semantically similar based on skill content — not just same category

Code & Development Solid

observability

引導可觀測性建置、指標設計與告警設定。 Use when: 新服務的埋點、SLO 定義、告警設計、成熟度評估。 Not for: 設定數值目標與 Error Budget 政策——請用 /slo；日誌格式與層級——請用 /logging-guide。 Keywords: observability, metrics, traces, golden signals, alerting, SLO, 可觀測性, 指標, 追蹤, 告警.

71 Updated today
AsiaOstrich
AI & Automation Listed

slo-and-error-budgets

Use when defining or reviewing service reliability targets and alerting — picking SLIs, setting SLO targets, computing error budgets, and writing burn-rate alerts. Triggers on "what should we alert on", "set an SLO", noisy or missing alerts, uptime targets, or dashboards that don't reflect user experience.

0 Updated 2 weeks ago
Markuysa
AI & Automation Listed

observability-designer

SLO/SLI design, alert optimization, and dashboard generation for production services. TRIGGER when: user asks to define SLOs, design alerts, create dashboards, reduce alert fatigue, set error budgets, or improve observability; user runs /observability or /slo. DO NOT TRIGGER when: debugging a specific incident (use debugging tools), writing application code, configuring CI/CD pipelines.

0 Updated 2 weeks ago
DROOdotFOO