What is observability?

A skill for operating and improving software systems by collecting logs, metrics, and traces. This practice is called observability: using system evidence to understand what happened, especially when something fails.

Use it to design monitoring, logging, metrics, tracing, alerting, dashboards, service objectives, and incident-detection processes.

It helps teams find problems, understand their impact, and detect incidents instead of guessing from incomplete information. It also covers service targets and alerts.

observability — Skill for Claude Code by camilooscargbaptista

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add camilooscargbaptista/cto-toolkit --skill observability

Clone the repo

git clone --depth 1 https://github.com/camilooscargbaptista/cto-toolkit

Made for: Claude Code.

Or install cto-toolkit, the plugin that ships this one along with the rest of its 54 skills, 6 agents, 3 hooks.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/camilooscargbaptista/cto-toolkit/observability/github.svg)](https://agentmods.dev/skills/camilooscargbaptista/cto-toolkit/observability)

Your own site

<a href="https://agentmods.dev/skills/camilooscargbaptista/cto-toolkit/observability"><img src="https://agentmods.dev/badge/skills/camilooscargbaptista/cto-toolkit/observability/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/camilooscargbaptista/cto-toolkit/observability"><img src="https://agentmods.dev/badge/skills/camilooscargbaptista/cto-toolkit/observability.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 180 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 2,295 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00180	$0.02295
Opus 5.5	$0.00072	$0.00918
Sonnet 5.5	$0.00036	$0.00459
Haiku 4.5	$0.00018	$0.00230

Measured 2mo ago against content hash bf37cefd2a68, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

observability scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

observability/SKILL.md · 261 lines

How it starts

The opening of the file, as written. The whole thing — 261 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Observability, Monitoring & SRE

You are a senior SRE / platform engineer helping teams build observable systems. Observability is not about collecting data — it's about being able to answer questions you haven't thought of yet when things go wrong at 3am.

The Three Pillars

1. Logs — What happened

Structured events that tell the story of what the system did.

{
  "timestamp": "2024-03-15T14:32:01.123Z",
  "level": "error",
  "service": "payment-service",
  "traceId": "abc123def456",
  "spanId": "span789",
  "userId": "usr_42",
  "message": "Payment processing failed",
  "error": "InsufficientFundsError",
  "orderId": "ord_123",
  "amount": 15000,
  "currency": "BRL",
  "duration_ms": 340,
  "environment": "production"
}

Log best practices:

Always structured (JSON), never unstructured text
Include correlation/trace IDs in every log line
Log level discipline: ERROR for things that need attention, WARN for degradation, INFO for business events, DEBUG for troubleshooting (off in prod by default)
Never log PII, passwords, tokens, or full credit card numbers
Include context: who (user), what (action), where (service), result
Use consistent field names across all services

2. Metrics — How much / how fast

Numeric measurements aggregated over time.

The Four Golden Signals (Google SRE):

Signal	What it measures	Example metric
Latency	Time to serve a request	`http_request_duration_seconds`
Traffic	Demand on the system	`http_requests_total`
Errors	Rate of failed requests	`http_requests_errors_total`
Saturation	How "full" the system is	`cpu_usage_percent`, `memory_usage_percent`

USE Method (for infrastructure):

Utilization — % of resource capacity used
Saturation — Queue depth, waiting work
Errors — Error count per resource

RED Method (for services):

Rate — Requests per second
Errors — Errors per second
Duration — Latency distribution (p50, p90, p99)

Read the full file on GitHub · 261 lines

Files

What ships with it

3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

2mo ago First seen · 261 lines · 180 tokens per session scan A bf37cefd2a68

Subscribe to this mod's changes

observability is a skill published in the GitHub repository camilooscargbaptista/cto-toolkit (8 stars, last pushed 7mo ago), licensed MIT. It adds 180 tokens to every session and 2,295 once invoked, about $0.0007 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Analytics and metrics DevOps and cloud alerting logging monitoring operational slo tracing

observability next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
observabilitycamilooscargbaptista/cto-toolkit	Skill	8	7mo ago	MIT	A	180	Claude Code
datadogbobmatnyc/claude-mpm-skills	Skill	78	3mo ago	MIT	A	43	Claude Code
frontmcp-observabilityagentfront/frontmcp	Skill	148	yesterday	Apache-2.0	A	196	Claude Code, Codex
monitoring-alerting-commercefinsilabs/awesome-ecommerce-skills	Skill	63	15d ago	MIT	A	31	Claude Code, Codex
monitoring-expertpersonamanagmentlayer/pcl	Skill	44	11d ago	Apache-2.0	B	70	Claude Code
Observability ChecklistNotysoty/openagentskills	Skill	9	2mo ago	MIT	A	28	Claude Code, Codex
Observabilityniels-emmer/myace	Skill	1	5d ago	MIT	A	36	Claude Code, Codex