Observability Hardening
Audit or improve observability for named production questions, incidents, or opaque operations using privacy-safe telemetry. Use only when the user explicitly asks for an observability or instrumentation pass, telemetry design, dashboards or alerts, or when inability to explain production behavior is the primary problem. Do not trigger for ordinary debugging, adding one log line, generic production readiness, product analytics alone, or implementation work that merely benefits from diagnostics.
Install
npx skills add swyxio/skills --skill observability-hardeninggit clone --depth 1 https://github.com/swyxio/skills.git /tmp/skills
mkdir -p ~/.claude/skills
cp -r /tmp/skills/observability-hardening ~/.claude/skills/observability-hardeningPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Observability Hardening Use this skill when the product works but failures are opaque. The output should make production behavior explainable without leaking private data. ## Counterweight: questions before telemetry - Start with the operator or user question that cannot currently be answered. Add no signal without a named consumer and decision. - Inspect provider-native logs, metrics, traces, request IDs, and dashboards before building parallel telemetry. - Choose the cheapest sufficient signal. Do not add logs, metrics, traces, dashboards, alerts, analytics, and user-visible state as a bundle. - Instrument ownership boundaries and material state transitions, not every function or phase. - Prefer a saved query or clearer existing event over a new pipeline, schema, SDK, collector, or dashboard. - Budget cardinality, volume, retention, latency, privacy, and on-call noise. More telemetry can make diagnosis worse. - Add an alert only when someone owns a concrete response. Add user-visible progress only when users must wait or act. - Do not turn a local debugging gap into a repository-wide observability program or product analytics redesign. - A scoped audit may conclude existing signals are sufficient or recommend deletion of noisy telemetry. - Do not configure external services, create dashboards, change retention, or deploy instrumentation unless the active request explicitly authorizes it. ## Workflow 1. **Map what must be understood**
Details
- Skill name
observability-hardening- Repository
- swyxio/skills
- Path
observability-hardening/SKILL.md- License
- MIT
- Repo updated
- 16 November 2026
FAQ
What does the Observability Hardening skill do?
Audit or improve observability for named production questions, incidents, or opaque operations using privacy-safe telemetry. Use only when the user explicitly asks for an observability or instrumentation pass, telemetry design, dashboards or alerts, or when inability to explain production behavior is the primary problem. Do not trigger for ordinary debugging, adding one log line, generic production readiness, product analytics alone, or implementation work that merely benefits from diagnostics.
How do I install the Observability Hardening skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add swyxio/skills --skill observability-hardening. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Observability Hardening popular?
It lives in swyxio/skills, which has 201 GitHub stars and 12 forks.
Related skills
Accelevents API
201swyxio/skills
Use when reading or updating AI Engineer Europe speaker records through the Accelevents REST API, especially for full-record PUT updates, auth header quirks, and preserving existing speaker fields.
Accelevents Speaker Sync
201swyxio/skills
Use when website speaker, session, schedule, room, track, or headshot changes must be synchronized back to Accelevents for AI Engineer Europe 2026.
Agents SDK
201swyxio/skills
Build or debug stateful applications that specifically use Cloudflare's `agents` package, including Agent classes, routing, callable methods, synchronized state, scheduling, AIChatAgent, durable execution, or Agents SDK client hooks. Do not trigger for generic AI-agent design, the OpenAI Agents SDK, or ordinary Durable Object work that does not use the Cloudflare Agents SDK.
Opensearch Personalize Caching Strategies
228pproenca/dot-skills
Caching strategies in front of AWS OpenSearch (Elasticsearch) or AWS Personalize — search, recommenders, multi-recommender pages, anon vs logged-in traffic. Covers ROI decision (TPS/minProvisionedTPS, Zipf, amplification), key design (canonicalisation, cohort vs user, solution-version pinning, bucketing), personalisation boundary (anon/logged split, fan-out coalescing), strategies (cache-aside, refresh-ahead, write-through, batch precompute, L1+L2), TTL (volatility, soft/hard, jitter, event-driven invalidation), stampede protection (single-flight, XFetch, stale-while-revalidate, circuit breake
Nginx C Modules
228pproenca/dot-skills
nginx C module development guidelines based on the official nginx development guide. This skill should be used when writing, reviewing, or refactoring nginx C modules to ensure correct memory management, request lifecycle handling, and event-driven patterns. Triggers on tasks involving nginx module development, ngx_http_module_t, handler/filter/upstream implementation, pool allocation, or nginx configuration directives.
Pulumi
228pproenca/dot-skills
Pulumi infrastructure as code performance and reliability guidelines. This skill should be used when writing, reviewing, or refactoring Pulumi code to ensure optimal deployment performance and infrastructure reliability. Triggers on tasks involving Pulumi stacks, components, state management, secrets configuration, resource lifecycle options, or CI/CD automation.
Browse the most popular Claude skills, all devops & cloud skills, or write your own with the skills generator.