773 free skills
Observability skills
Skills for observability — structured logging, distributed tracing, metrics dashboards, alerting, and incident response runbooks.
Sourced from real, public repositories — synced daily, never invented.
773 free skills
Skills for observability — structured logging, distributed tracing, metrics dashboards, alerting, and incident response runbooks.
Sourced from real, public repositories — synced daily, never invented.
15 tools across six categories
13 of them never send your data anywhere
Free · No signup · No trial clock
SEE THE DIRECTORY
on-call-runbook
kienbui1995/magic-powers
Use when writing runbooks for on-call engineers, documenting incident response steps, or creating operational playbooks
runbook
notharshhaa/devops-skills
Write or audit operational runbooks as a senior SRE — one document per failure mode, with detection signal, triage decision tree, verified read-only diagnostics, mitigation with rollback, escalation path, and verification — grounded in the real repo, alerts, and dashboards rather than generic advice. Strictly read-only on systems — it drafts documents under runbooks/ and never executes a mitigation itself. Use when asked to write a runbook or on-call playbook, document a failure mode or recovery procedure, close a "no runbook for this alert" gap, or review existing runbooks for staleness and accuracy.
runbook-generator
galyarderlabs/galyarder-framework
Use when an operational workflow, release procedure, incident pattern, or support process needs to be captured as a repeatable runbook.
eng-runbook
0xforked/open-design
|
tracing
yiweiwan/skills
Use only when adding or improving distributed tracing, spans, trace context propagation, request correlation, OpenTelemetry instrumentation, dependency timing, and trace-based production diagnostics.
logging
yiweiwan/skills
Use only when adding or improving application logs, structured logging, log levels, request IDs, error context, audit logs, sensitive data redaction, and log usefulness for debugging.
distributed-tracing
truongnat/simple-skills
Implement distributed tracing with Jaeger and Tempo to track requests across microservices and identify performance bottlenecks. Use when debugging microservices, analyzing request flows, or implementing observability for distributed systems.
incident-response
charlieviettq/awesome-agent-skill
Run an incident response workflow — triage, communicate, and write postmortem. Trigger with \"we have an incident\", \"production is down\", an alert that needs severity assessment, a status update mid-incident, or when writing a blameless postmortem after resolution.
incident-response
alizafarbati/opencode-agents-mcp
Expert SRE specializing in incident management, post-mortem analysis, reliability engineering, and production outage response strategies.
runbook-writing
yiweiwan/skills
Use only when writing or improving operational runbooks, incident response guides, on-call procedures, diagnosis steps, mitigation steps, rollback steps, escalation paths, service health checks, and production support playbooks.
sota-observability
martinholovsky/sota-skills
>-
workers-best-practices
cloudflare/com
Reviews and authors Cloudflare Workers code against production best practices. Load when writing new Workers, reviewing Worker code, configuring wrangler.jsonc, or checking for common Workers anti-patterns (streaming, floating promises, global state, secrets, bindings, observability). Biases towards retrieval from Cloudflare docs over pre-trained knowledge.
exploring-llm-clusters
posthog/posthog
Investigate AI observability clusters — understand usage patterns in AI/LLM traffic, compare cluster behavior, compute cost/latency metrics, and drill into individual traces within clusters.
gdpr
petrogurcak/skills
GDPR and Czech data protection specialist — validates data processing, employee monitoring, consent, and DPIA requirements against GDPR (2016/679) and Czech ZZOÚ (110/2019). Use when asked about personal data processing, employee data, monitoring, cookies, data subject rights, or privacy compliance.
do-k8s
tomz/agent-skills
DigitalOcean Kubernetes (DOKS), node pools, auto-scaling, Container Registry, and monitoring
k8s-network-and-identity-policy
amritmalla/claude-full-stack-2.0
Use when authoring or hardening the Kubernetes network and workload-identity policy for a service after security and infrastructure-platform have decided the trust zones, identity model, and east-west posture. Produces default-deny NetworkPolicy (namespace-scoped, label-selected), least-privilege ServiceAccount + Role/ClusterRole bindings, Ingress / Gateway API exposure posture, mTLS or service-mesh wiring where adopted, image-pull secret and registry-auth handling, and Pod Security Standards namespace enforcement. Do not use for workload manifest authoring, autoscaling and resilience topology, observability wiring, image hardening / signing / admission-controller policy, or cluster provisioning; use the other Family G archetype skills (cluster provisioning is out of family).
elk
wilsonwong1990/homelab-assistant-agent
Elastic Stack (Elasticsearch, Logstash, Kibana, Beats/APM) observability for homelab logging, metrics, tracing, dashboards, and alerting.
apache-kafka
ivanshamaev/de-agent-skills
Apache Kafka — topics, partitions, consumer groups, producer/consumer configuration (acks, idempotence, compression, commit strategies), exactly-once semantics, Kafka Connect (source/sink connectors, SMTs, DLQ), Schema Registry, consumer lag monitoring, CLI operations, Python confluent-kafka examples, partition strategy, replication, retention
data-pipelines
dtsong/data-engineering-skills
Use this skill when scheduling, orchestrating, or monitoring data pipelines. Covers Dagster assets, Airflow DAGs, Prefect flows, sensors, retries, alerting, and cross-tool integrations (dagster-dbt, dagster-dlt). Common phrases: \"schedule this pipeline\", \"Dagster vs Airflow\", \"add retry logic\", \"pipeline alerting\", \"consulting pipeline\". Do NOT use for building transformations (use dbt-transforms or python-data-engineering) or designing integration patterns (use data-integration).
adk-observability-guide
keiyamamoto-web/kei-agentic-playground
>
fp-go-logging
ibm/fp-go
Use this skill when working with logging in fp-go functional pipelines (github.com/IBM/fp-go/v2/logging). Trigger on mentions of logging in monadic contexts, ChainFirstIOK, ChainFirst with logging, side-effect logging, structured logging (SLog), context-embedded loggers, LoggingCallbacks, TapSLog, LogEntryExit, Printf/Logf in IO/ReaderIO/ReaderIOResult, or when the user needs to add logging to functional pipelines without breaking the data flow.
structured-logging
piwero/ai-harness
Add structured JSON logging to code following project standards. Includes correct log levels, required fields, and what never to log.
structured-logging-and-tracing
addzyyy/dora-skills
Apply when adding console.log, print, logger calls, error handling, debug output, or any observability — use structured JSON logs with trace/correlation IDs, never free-form strings; covers distributed tracing and log aggregation
use-structured-logging
mew-ton/coding-guidelines
Enforces structured JSON logging with context fields such as TraceID for backend observability. Use when adding or reviewing log statements in backend services. Do not use for development-only debug scripts or CLI tools where human-readable output is preferred.
skill-implement-structured-logging-mdc
govil-dev/peajes
Ensure all log entries include mandatory MDC fields (correlationId, tagId, stationId, traceId) for traceability and strictly prohibit PII by using masking functions.
incident-response
witi-projects/skills
Handle production incidents — triage, mitigate, communicate, and write postmortems. Use when the user says "/incident-response", "incident response", or asks about incident response.
logging
wellux/claude-code-deprecated
>
logging-patterns
eliranabu/schoolclaudeskills
>
logging-best-practices
repairyourtech/cfsa-antigravity
Implement structured logging with JSON formats, log levels (DEBUG, INFO, WARN, ERROR), contextual logging, PII handling, and centralized logging. Use for logging, observability, log levels, structured logs, or debugging.
log-structured
filip-podstavec/claude-leverage
>
distributed-tracing
jiho00seo-dev/antigravity-awsome-skill
Implement distributed tracing with Jaeger and Tempo to track requests across microservices and identify performance bottlenecks. Use when debugging microservices, analyzing request flows, or implementing observability for distributed systems.
distributed-tracing
ranbot-ai/awesome-skills
Implement distributed tracing with Jaeger and Tempo for request flow visibility across microservices.
distributed-tracing
0motionguy/gicm
OpenTelemetry, Jaeger, tracing across microservices for full request visibility.
instrument-distributed-tracing
pjt222/agent-almanac
>
incident-response
0king0p/claude-skills
>
incident-response
agenticdevops/devops-execution-engine
Structured incident response and diagnosis workflows
distributed-debugging-debug-trace
atilamedeiros/skills
You are a debugging expert specializing in setting up comprehensive debugging environments, distributed tracing, and diagnostic tools. Configure debugging workflows, implement tracing solutions, and establish troubleshooting practices for development and production environments.
lmt
selisedigitalplatforms/blocks-construct-blazor
Use this skill for viewing service logs, filtering logs by date, streaming live logs, browsing distributed traces, or analyzing API performance and HTTP status distributions on SELISE Blocks.
microservices-architect
liyin2015/claude-skills-2
Use when designing distributed systems, decomposing monoliths, or implementing microservices patterns. Invoke for service boundaries, DDD, saga patterns, event sourcing, service mesh, distributed tracing.
quality-observability
corentinlumineau/base-skills
>
distro-debugger
chili-piper/mcp-assets
Debugs why a CRM record was routed (or not routed) through a Chili Piper distribution — accepts a log ID, Salesforce record ID, or contact/lead name, explains each rule stage, and recommends a targeted fix
incident-response
mohammad-shaddad/cardo
Incident response pipeline — triage, investigate, track, and review incidents using structured workflows. Dispatches sre-engineer for analysis.
incident-response
uptimerobot/ai
End-to-end incident workflow — find what's down, diagnose it, pause flapping monitors, and verify recovery.
incident-response
bjornjee/skills
Use when production is broken or degraded — mitigation-first response, timeline capture, severity ladder, and blameless postmortems. Agent-loop failures go to agent-introspection-debugging instead.
incident-response
boparaiamrit/skills-by-amrit
Use during production incidents — outages, security breaches, data corruption, performance degradation. Provides structured triage, mitigation, resolution, and post-mortem processes.
incident-response
cheggin/request-for-startups
Automated incident lifecycle from detection through diagnosis, fix, deploy, verification, and post-mortem with budget-guarded escalation.
incident-response
jessefmoore/offensive-claude
IR playbook execution — evidence collection, timeline analysis, memory forensics, disk forensics, containment strategies, post-incident reporting
incident-response
jonusnattapong/dek1skills
Handle active incidents — failing CI, production issues, runtime breakage, security alerts, agent failures. Stabilize first, diagnose second, fix third. Trigger on /incident-response, or when something is actively broken, CI is red, or emergency fixes are needed.
incident-response
resultakak/argos
Production incident triage, stabilizasyon, forensics, communication ve postmortem disiplini.
incident-response
grandheman/claude-sdlc
>
monitoring-alerting
ricardoroche/ricardos-claude-code
Automatically applies when implementing monitoring and alerting. Ensures proper metric instrumentation, alerts, SLO/SLI definition, dashboards, and observability patterns.
ari-monitoring-alerting
ari-os/ari
Real-time monitoring and alerting system for ARI
monitoring
wellux/claude-code-deprecated
>
alert_monitor
marcoamu/openclaw-workspace
Monitorea eventos y envía alertas cuando ocurren condiciones específicas.
discord-alerts
spinnakergit/a0-discord
Monitor Discord channels for new alerts and messages. Automatically polls at configurable intervals, extracts images for analysis, and saves alerts to memory.
dd-monitors
mtullalizardi/agent-skills
Monitor management - list, search, file-based create, and alerting best practices.
agent-health-monitor
manteclaw/skills-marketplace
Full-stack health monitoring for AI agent infrastructure. Monitors API keys, wallet balances, daemon processes, cron jobs, disk space, and service endpoints. Auto-alerts via Telegram/Discord when thresholds breach. Use when an agent needs operational monitoring, infrastructure health checks, automated alerting, or recovery from system failures.
on-call-runbooks
themyerman/ai-skills
>-
runbook-writing-weapon
jzferrell26/dm-skills
Operational runbook authorship specialist — canonical templates (break-fix, scheduled operation, diagnostic), the no-implied-context audit protocol, exact-command discipline, escalation path architecture, rollback procedure standards, runbook-as-test (game day) methodology, and postmortem-to-runbook linkage. Activate when the user says "write a runbook", "audit this runbook", "our runbooks are out of date", "we need a runbook for this alert", "turn this postmortem into a runbook", "schedule a game day", "our on-call docs are weak", or when `runbook-writing-guardian` is invoked. Do NOT activate for incident management tooling setup (PagerDuty/OpsGenie — route to devops-guardian), infrastructure provisioning decisions (route to devops-guardian), or documentation culture/process design beyond the runbook format (route to library-guardian).
runbook-generator
dundas/uhr
Generate operational runbooks documenting what needs to be running locally and in production for effective system testing and deployment.