OB

observability-setup

Provides a checklist and alert plan for setting up service metrics, logs, and traces.

Install

mkdir -p .claude/skills/observability-setup && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/12886" && unzip -o skill.zip -d .claude/skills/observability-setup && rm skill.zip

Installs to .claude/skills/observability-setup

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

Set up metrics, logs, and traces for a service. Use when a mid-level developer needs basic observability coverage.
114 chars✓ has a “when” trigger
Intermediate

Key capabilities

  • Define key service indicators and error budget metrics
  • Instrument logs with correlation IDs
  • Set alerts for critical thresholds
  • Measure user impact
  • Avoid noisy alerts

How it works

This skill defines key service indicators, instruments logs with correlation IDs, and sets alerts for critical thresholds to establish observability.

Inputs & outputs

You give it
Service architecture, key endpoints, existing tools, and SLI/reliability targets
You get back
An instrumentation checklist and an alert plan

When to use observability-setup

  • Setting up service logs
  • Instrumenting metrics and traces
  • Defining monitoring alert thresholds
  • Improving service reliability

About this skill

Observability Setup

Purpose

Set up metrics, logs, and traces for a service.

Inputs to request

  • Service architecture and key endpoints.
  • Existing logging and monitoring tools.
  • SLI or reliability targets.

Workflow

  1. Define key service indicators and error budget metrics.
  2. Instrument logs with correlation IDs.
  3. Set alerts for critical thresholds.

Output

  • Instrumentation checklist and alert plan.

Quality bar

  • Measure user impact, not just system health.
  • Avoid noisy alerts by defining clear thresholds.

When not to use it

  • When only system health needs to be measured, not user impact
  • When noisy alerts are acceptable
  • When a mid-level developer does not need basic observability coverage

Limitations

  • Measures user impact, not just system health
  • Avoids noisy alerts by defining clear thresholds
  • Intended for basic observability coverage for a mid-level developer

How it compares

This workflow provides a structured approach to setting up observability, focusing on user impact and clear alert thresholds, unlike a basic logging setup.

Compared to similar skills

observability-setup side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
observability-setup (this skill)05moNo flagsIntermediate
devops-troubleshooter14moNo flagsAdvanced
observability-monitoring-monitor-setup14moNo flagsIntermediate
Logging and Monitoring for Agentic Workflows03moCautionAdvanced

Try saying

Example prompts that trigger this skill in your AI assistant.

You might also like

devops-troubleshooter

sickn33

Expert DevOps troubleshooter specializing in rapid incident response, advanced debugging, and modern observability. Masters log analysis, distributed tracing, Kubernetes debugging, performance optimization, and root cause analysis. Handles production outages, system reliability, and preventive monitoring. Use PROACTIVELY for debugging, incident response, or system troubleshooting.

12

observability-monitoring-monitor-setup

sickn33

You are a monitoring and observability expert specializing in implementing comprehensive monitoring solutions. Set up metrics collection, distributed tracing, log aggregation, and create insightful da

12

Logging and Monitoring for Agentic Workflows

Hack23

Comprehensive observability patterns for GitHub Agentic Workflows including structured logging, metrics collection, alerting strategies, debugging techniques, and production monitoring best practices for autonomous agent systems.

00

service-mesh-observability

wshobson

Implement comprehensive observability for service meshes including distributed tracing, metrics, and visualization. Use when setting up mesh monitoring, debugging latency issues, or implementing SLOs for service communication.

574

observability-engineer

sickn33

Build production-ready monitoring, logging, and tracing systems. Implements comprehensive observability strategies, SLI/SLO management, and incident response workflows. Use PROACTIVELY for monitoring infrastructure, performance optimization, or production reliability.

1242

ops

matteocervelli

Post-deploy observability for production services — structured logging, RED metrics + Prometheus, Grafana dashboards, SLO-based alerting. Use when setting up monitoring or instrumenting a live service. Trigger on "add logging", "metrics", "dashboard", "alerting", "observability", "monitor this servi

00

Search skills

Search the agent skills registry