Observability Design
Design observability (metrics, logs, traces) for understanding system behavior in production. Use when debugging distributed systems or building monitoring.
Install
/plugin marketplace add sethdford/claude-skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add sethdford/claude-skills --skill observability-designgit clone --depth 1 https://github.com/sethdford/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/architect/quality-attributes/skills/observability-design ~/.claude/skills/observability-designPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Observability Design Design comprehensive observability across metrics, logs, and traces to understand system behavior and debug issues. ## Context You are building observability for a system. The user struggles to debug production issues or wants better visibility. Read their current monitoring setup. ## Domain Context Based on Google's SRE practices and observability research: - **Metrics**: Quantitative measurements (latency, error rate, QPS). Fast queries, low cardinality. - **Logs**: Event records with context (error messages, user actions). High volume, searchable. - **Traces**: Request flow across services. Shows dependencies and latency breakdown. - **Correlation IDs**: Link logs and traces across services. Essential for debugging. - **Cardinality**: Unique values for metric labels. High cardinality (millions of unique values) breaks storage. ## Instructions 1. **Define Key Metrics**: For each critical path, specify SLI metrics (success rate, latency, saturation). Example: order checkout: success rate >99.9%, p99 latency <500ms. 2. **Design Metrics Collection**: Instrument code with metrics (request count, latency histogram, error count). Use metrics library (Prometheus, StatsD). Keep cardinality low. 3. **Configure Logging**: Log key events (authentication, errors, deployments). Include correlation ID in every log. Aggregate logs centrally (ELK, Datadog).
Details
- Skill name
observability-design- Repository
- sethdford/claude-skills
- Path
architect/quality-attributes/skills/observability-design/SKILL.md- License
- MIT
- Repo updated
- 11 March 2026
FAQ
What does the Observability Design skill do?
Design observability (metrics, logs, traces) for understanding system behavior in production. Use when debugging distributed systems or building monitoring.
How do I install the Observability Design skill?
Claude Code plugin: /plugin marketplace add sethdford/claude-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Observability Design popular?
It lives in sethdford/claude-skills, which has 48 GitHub stars and 10 forks.
Related skills
A B Test Design
48sethdford/claude-skills
Design rigorous A/B tests with hypotheses, variants, metrics, and sample size calculations.
A B Test Design Pm
48sethdford/claude-skills
Analytics and experimentation skill for product managers.
Abuse Case Design
48sethdford/claude-skills
Design abuse cases (negative use cases) showing how attackers misuse system features. Use when identifying attacks that exploit intended functionality or business logic flaws.
Service Mesh Patterns
48sethdford/claude-skills
Implement service mesh patterns for observability, resilience, and traffic management. Use when managing complex microservices communication at scale.
Monitoring Instrumentation
48sethdford/claude-skills
Metrics, logs, traces (observability); choosing what to measure, dashboards, and incident response.
Vendor Evaluation
48sethdford/claude-skills
Systematically evaluate and select vendors for infrastructure, SaaS, or services.
Browse the most popular Claude skills, all devops & cloud skills, or write your own with the skills generator.