Observability

Use when the user asks about adding observability to a service: logs, metrics and traces, structured JSON logging, how to instrument services with OpenTelemetry traces per stack, SLIs, and alerting on symptoms not causes. Produces a per-service observability baseline. Not for Collector pipelines and sampling (use devops-opentelemetry) or Prometheus setup (use prometheus-grafana).

45 stars 6 forksDevOps & Cloud

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add j4flmao/agent-skills --skill observability
Manual install
git clone --depth 1 https://github.com/j4flmao/agent-skills.git /tmp/agent-skills
mkdir -p ~/.claude/skills
cp -r /tmp/agent-skills/skills/devops/observability ~/.claude/skills/observability

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Observability

## Purpose
Set up structured logging, metrics, and distributed tracing to understand system behavior in production.

## Agent Protocol

### Trigger
Exact user phrases: "observability", "logging", "metrics", "tracing", "OpenTelemetry", "Grafana", "Prometheus", "structured logs", "distributed tracing", "monitoring".

### Input Context
Before activating, verify:
- The stack is known (for OpenTelemetry SDK selection).
- The existing observability tooling is understood (Prometheus, Grafana, etc.).
- The traffic volume is known (for trace sampling strategy).

### Output Artifact
No file output. This skill produces an observability plan.

### Response Format
Observability plan: logging format, metrics list, trace sampling strategy, SLOs, alert rules.

No preamble. No postamble. No explanations. No filler/hedging/transitions. Compress output — why use many token when few do trick. No explanation of why observability is important.

### Completion Criteria
This skill is complete when:
- [ ] Structured JSON logging format is defined with required fields.
- [ ] Key metrics are listed (counters, gauges, histograms).
- [ ] Trace sampling strategy is specified.
- [ ] SLOs are defined with SLIs.
- [ ] Alert rules follow symptom-based (not cause-based) design.

### Max Response Length
40 lines.

## Quick Start
Read the full skill on GitHub

Details

Skill name
observability
Path
skills/devops/observability/SKILL.md
License
MIT
Repo updated
17 November 2026

FAQ

What does the Observability skill do?

Use when the user asks about adding observability to a service: logs, metrics and traces, structured JSON logging, how to instrument services with OpenTelemetry traces per stack, SLIs, and alerting on symptoms not causes. Produces a per-service observability baseline. Not for Collector pipelines and sampling (use devops-opentelemetry) or Prometheus setup (use prometheus-grafana).

How do I install the Observability skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add j4flmao/agent-skills --skill observability. 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 j4flmao/agent-skills, which has 45 GitHub stars and 6 forks.

Related skills

Agent Observability

45

j4flmao/agent-skills

Use when the user asks about agent observability, tracing agent reasoning, debugging an agent loop, OpenTelemetry GenAI spans for LLM calls, LLM cost tracking per agent, agent audit logs or hallucination/eval monitoring in production. Produces instrumentation config, trace schema, dashboards, alerts and cost attribution. Not for generic service tracing without LLMs (use devops-opentelemetry).

DevOps & Cloud

AI Agent Architectures

45

j4flmao/agent-skills

Use when the user asks to build an AI agent, design an agent that calls tools and keeps memory, write an agent system prompt or pick an agent framework (Claude Agent SDK, OpenAI Agents SDK, LangGraph). Produces an architecture brief covering loop, tools, memory, guardrails and evals, routing depth to child skills. Not for workflow patterns (use ai-agentic-workflows).

AI, LLMs & Agents

AI Agent Core Loop

45

j4flmao/agent-skills

Use when the user asks about the agent loop, ReAct vs plan-and-solve, re-planning, Reflexion, an agent stuck in a loop, max iterations or termination conditions. Produces a loop spec or patch with state, success predicate, caps and no-progress detection. Not for overall agent design (use ai-agent-architectures) or tool schemas (use tool-calling-principles).

AI, LLMs & Agents

Oracle Cloud

45

j4flmao/agent-skills

Use when the user asks about Oracle Cloud Infrastructure (OCI), compartments and IAM policies, VCN, security lists and NSGs, OKE, Autonomous Database, OCI Object Storage, FastConnect, Resource Manager, or the oci Terraform provider. Produces OCI architectures and IaC. Not for AWS (use aws) or IBM Cloud (use ibm-cloud).

DevOps & Cloud

Nomad

45

j4flmao/agent-skills

Use when the user asks about HashiCorp Nomad, Nomad job specs (service, batch, system, periodic, parameterized), ACLs, Nomad Variables, Vault or Consul integration, CSI and host volumes, canary updates, node drain, or the Nomad Autoscaler. Produces Nomad job files and cluster operations. Not for Kubernetes (use kubernetes) or Consul service mesh (use consul).

DevOps & Cloud

Prometheus Grafana

45

j4flmao/agent-skills

Use when the user asks about kube-prometheus-stack, ServiceMonitor, exposing /metrics, PromQL queries, Prometheus alert rules, Alertmanager routing, Grafana dashboards as code, or RED and USE metrics. Produces Prometheus, Alertmanager and Grafana configs. Not for TSDB internals and scaling (use sre-observability-scaling) or SLO burn-rate alerts (use sre-sli-slo-management).

DevOps & Cloud

Browse the most popular Claude skills, all devops & cloud skills, or write your own with the skills generator.