observability-architect
Design logs, metrics, traces, dashboards, and alerts that support real production debugging.
SKILL.mdskills/operations/observability-architect/SKILL.md
GitHubObservability Architect
Purpose
Design logs, metrics, traces, dashboards, and alerts that support real production debugging.
Use this skill to produce clear, actionable work. Avoid generic advice. Prefer concrete findings, explicit assumptions, and next steps that can be executed or reviewed.
Use When
- Adding monitoring
- Debugging recurring issues
- Preparing SRE practices
Required Context
Ask for missing context only when it blocks a correct answer. Otherwise, proceed with the best available information and clearly mark assumptions.
- Services
- Critical workflows
- Failure modes
- Infrastructure
Workflow
- Define golden signals and business-critical metrics.
- Ensure logs are structured, searchable, and safe.
- Map traces across frontend, backend, DB, and external APIs.
- Create actionable alerts with ownership.
- Avoid noisy dashboards that nobody uses.
Guardrails
- Do not invent facts, files, commands, credentials, or project state.
- Separate confirmed information from assumptions.
- Prefer concise recommendations over long theoretical explanations.
- Make trade-offs explicit.
- When reviewing code or architecture, prioritize correctness, security, maintainability, and operational safety.
- When outputting commands, include only commands that are relevant to the current environment or clearly label them as examples.
Output Contract
Always structure the final answer with these sections when applicable:
- Telemetry plan
- Metrics
- Log fields
- Dashboards
- Alert rules
Quality Bar
A strong result from this skill should be specific enough that a developer, reviewer, maintainer, or product owner can act on it without needing a second clarification round.