observability-and-ops
SolidDesigning observability into systems from the start, including metrics, health checks, staleness detection, quality signals, admin dashboards, and operational alerts. Use when designing admin panels, health monitoring, quality enforcement, system diagnostics, adding metrics to existing code, setting up alerts, building status pages, or debugging production issues. Also use when the user mentions "health check", "monitoring", "alerting", "metrics", "dashboard", or "staleness".
Install
Quality Score: 82/100
Skill Content
Details
- Author
- Canhada-Labs
- Repository
- Canhada-Labs/ceo-orchestration
- Created
- 4 weeks ago
- Last Updated
- today
- Language
- Python
- License
- MIT
Integrates with
Bundled in these plugins
Similar Skills
Semantically similar based on skill content — not just same category
observability-monitoring
Design, audit, and troubleshoot production monitoring and observability using user-impact checks, layered telemetry, USE/RED, SLI/SLO/SLA, error budgets, cardinality controls, actionable alerting, burn-rate response, and postmortems. Use when asked about monitoring, наблюдаемость, алерты, Prometheus, Grafana, OpenTelemetry, logs, traces, profiles, service health, or incident evidence. Do not use for generic dashboard styling, frontend-only UI work, or unrelated code review.
observability
Instrument software so production questions get answered from signals, not guesses. Use when adding logging, metrics, tracing, or alerts, or when a system is hard to debug in production.
principle-observability
Observability principles — logs vs metrics vs traces, structured logging, distributed tracing, span/trace context, cardinality control, OpenTelemetry, SLI/SLO/SLA, RED method, USE method, alerting on symptoms vs causes. Auto-load when adding logging, choosing a metric, instrumenting distributed tracing, debating cardinality, defining SLIs/SLOs, designing alerts, or discussing observability budgets.