Observability
Apply modern observability practices from Charity Majors / Liz Fong-Jones / George Miranda's "Observability Engineering" (O'Reilly), Charity Majors' recent Observability 2.0 writing (2024-2025), Cindy Sridharan's essays, Google's SRE books, and the OpenTelemetry standard. Covers observability vs. monitoring, Observability 1.0 vs 2.0, wide/canonical high-cardinality structured events, the three signals (traces/metrics/logs) with OpenTelemetry semantic conventions + context propagation, metrics (RED, USE, Four Golden Signals), distributed tracing, sampling, SLO/SLI/error-budget discipline, obser
Install
/plugin marketplace add vnovakovits/claude-skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add vnovakovits/claude-skills --skill observabilitygit clone --depth 1 https://github.com/vnovakovits/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/plugins/engineering-practices/skills/observability ~/.claude/skills/observabilityPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Observability Apply this skill when instrumenting a service, debugging a production issue, defining SLOs, choosing what to log and what to measure, evaluating an existing system's observability, or designing alerting. The central question: **"Can I answer any question about what my system is doing right now, without shipping new code?"** ## Core Philosophy **Observability is the ability to ask new questions of your running system without re-deploying.** Not "did the alert fire?" — that's monitoring. Observability is "this customer reports a slow checkout; what happened on their last 5 requests, and what was different about the slowest one?" **Monitoring is for known-unknowns; observability is for unknown-unknowns.** Monitoring tells you that a known failure mode is happening. Observability lets you investigate a failure mode you didn't anticipate. **Production is the only environment that matters.** Tests and staging cannot reproduce production's load, data distributions, or strange-corner-of-the-graph users. Observability is how you understand production while it's running. **Wide, high-cardinality structured events beat the "three pillars".** The traditional split into logs / metrics / traces is increasingly seen as artificial. A well-structured event (one per request, with all relevant attributes) can serve as log, metric, and trace span — and crucially supports debugging questions that pre-aggregated metrics cannot answer.
Details
- Skill name
observability- Repository
- vnovakovits/claude-skills
- Path
plugins/engineering-practices/skills/observability/SKILL.md- License
- MIT
- Repo updated
- 16 November 2026
FAQ
What does the Observability skill do?
Apply modern observability practices from Charity Majors / Liz Fong-Jones / George Miranda's "Observability Engineering" (O'Reilly), Charity Majors' recent Observability 2.0 writing (2024-2025), Cindy Sridharan's essays, Google's SRE books, and the OpenTelemetry standard. Covers observability vs. monitoring, Observability 1.0 vs 2.0, wide/canonical high-cardinality structured events, the three signals (traces/metrics/logs) with OpenTelemetry semantic conventions + context propagation, metrics (RED, USE, Four Golden Signals), distributed tracing, sampling, SLO/SLI/error-budget discipline, obser
How do I install the Observability skill?
Claude Code plugin: /plugin marketplace add vnovakovits/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 popular?
It lives in vnovakovits/claude-skills, which has 5 GitHub stars and 2 forks.
Related skills
Accidental Cio
5vnovakovits/claude-skills
Apply Scott Millett's "The Accidental CIO — A Lean and Agile Playbook for IT Leaders" (Wiley, 2024) when designing or reviewing how a technology organisation decides, funds, governs and delivers work. Covers the five components of an adaptive IT operating model (organised, work, govern, talent, lead) and its four themes (outcomes over output, intrinsic motivation, being not doing agile, manage flow not people); matching method and governance to context via Cynefin and Wardley evolution; governance as demand management + funding + measurement + decision rights, shifting from project funding to
Agent Retro
5vnovakovits/claude-skills
Run a retrospective on a coding-agent session and improve the agent's environment, not the code. Combines Derby & Larsen's five-stage retrospective, Shigeo Shingo's poka-yoke (turn a mechanical mistake into a check that makes it impossible), and Matt Pocock's retro categories — navigation, automated checks, coding standards, steering files, tool economy, information access. Covers mining the session transcript for corrections, wrong turns and slow searches; deciding where each fix belongs (analyzer, hook, CI, reviewer standards, CLAUDE.md pointer, skill, doc or memory); the no-op test for stee
API Design
5vnovakovits/claude-skills
Design APIs that are clear, evolvable, and idiomatic to their protocol — covering REST (Fielding, Richardson Maturity Model, Massé), GraphQL, gRPC/protobuf, versioning strategies, pagination, error responses (RFC 7807 Problem Details), idempotency, authentication, documentation (OpenAPI), and the pragmatic trade-offs between RESTful purity and developer ergonomics. Use when designing a new endpoint, choosing between REST/GraphQL/gRPC, defining versioning, structuring error responses, deciding pagination strategy, or evaluating an existing API's evolvability.
Ops Devops Platform
8Freddy-CHEN-ux/00_claude_skills
Production-grade DevOps and platform engineering patterns: Kubernetes, Terraform, containers, GitOps, CI/CD, observability, incident response, security hardening, and cloud-native operations (AWS, GCP, Azure, Kafka).
Docker Log Debugger
8Freddy-CHEN-ux/00_claude_skills
Find and debug errors using Docker Compose logs. Use proactively when tests fail or services misbehave. PRIMARY - docker compose logs --since 15m | grep -iE -B 10 -A 10 "error|fail|exception
Systems Thinking Iceberg
5vnovakovits/claude-skills
Apply the systems-thinking iceberg — events, patterns, systemic structures, mental models (and Daniel Kim's fifth level, vision) — to explain why a problem keeps happening and where to intervene. Draws on Peter Senge's The Fifth Discipline (levels of explanation, archetypes), Daniel Kim's Vision Deployment Matrix and archetype work, Donella Meadows' Thinking in Systems and twelve leverage points, Peter Stroh's Systems Thinking for Social Change, and Deming/Ackoff on the system producing the behaviour. Covers the questions and response mode at each level, causal loops and delays, the archetypes
Browse the most popular Claude skills, all devops & cloud skills, or write your own with the skills generator.