This skill should be used when the user asks about "observability" or "monitoring", what "metrics, logs, and traces" to collect, "health checks" (liveness/readiness), "alerting" or "on-call", "SLO/SLI" or "error budgets", the "RED" or "USE" method, "dashboards", or names a tool like "Prometheus", "Grafana", or "Datadog". Use it whenever a design has no answer to "how would we know this is broken?" or "what do we alert on?" — i.e. any time failure would be invisible until users complain, even if the user doesn't say "observability".
$npx -y skills add proyecto26/system-design-skills --skill observabilityInstalls into the current project.
Run `npx skills use "https://github.com/proyecto26/system-design-skills" --skill "proyecto26/system-design-skills/observability"` and follow the generated skill instructions now. Read its complete output, redirecting it to a temporary file first if necessary. Resolve relative paths from the supporting-files directory it provides.
Use the skills in "https://github.com/proyecto26/system-design-skills" that are relevant to the current task. Run `npx skills add "https://github.com/proyecto26/system-design-skills"` and select the relevant skills, then follow their instructions.