📊
DevOpsJavaScript

Observability and Instrumentation

by addyosmani

Observability and Instrumentation is a DevOps skill for Claude Code, published by addyosmani in agent-skills.

86.7K stars9.3K forkson addyosmani/agent-skillsAdded 2026/08/13Repository updated 2026/08/11
agent-skillsantigravityclaude-codecodexcursorskills
Install in seconds
Install Observability and Instrumentation
Copy Observability and Instrumentation into your Claude Code skills folder. Run the command in your terminal, or review the source on GitHub before installing.
terminal
npx degit https://github.com/addyosmani/agent-skills/tree/main/skills/observability-and-instrumentation ~/.claude/skills/observability-and-instrumentation

Requires Node.js. Downloads this skill only — not the rest of the repository — into your Claude Code skills folder.

Without Node.js

git clone https://github.com/addyosmani/agent-skills.git

Clones the whole repository, then copy the skill’s own directory into your skills folder yourself.

In this catalog

Source file
skills/observability-and-instrumentation/SKILL.md in addyosmani/agent-skills
Installs to
~/.claude/skills/observability-and-instrumentation
Collection
One of 24 skills cataloged from this repository
Category
DevOps798 skills

What Observability and Instrumentation does

Observability and Instrumentation instruments code so production behavior is visible and diagnosable, adding logging, metrics, tracing, and alerting when shipping production features or diagnosing production issues with limited data.

Observability and Instrumentation is cataloged under DevOps on DirSkills. Observability and Instrumentation comes from a repository tagged agent-skills, antigravity, claude-code, codex and cursor.

Documentation

README

Observability and Instrumentation

Overview

Code you can't observe is code you can't operate. Observability is the ability to answer "what is the system doing and why?" from the outside, using the telemetry the code emits. Instrumentation is not a post-launch add-on — it's written alongside the feature, the same way tests are. If a feature ships without telemetry, the first user-reported bug becomes archaeology instead of a query.

When to Use

  • Building any feature that will run in production
  • Adding a new service, endpoint, background job, or external integration
  • A production incident took too long to diagnose ("we couldn't tell what happened")
  • Setting up or reviewing alerting rules
  • Reviewing a PR that adds I/O, retries, queues, or cross-service calls

This is the opening of the README. Read the full README on GitHub.

Frequently asked about Observability and Instrumentation

  • What else does addyosmani publish alongside Observability and Instrumentation?

    Observability and Instrumentation is one of 24 skills that DirSkills catalogs from addyosmani/agent-skills, the repository it ships in. Its siblings there include API and Interface Design, Agent Skill Discovery and Browser Testing. Each one is a separate skill with its own page in this directory, installs the same way Observability and Instrumentation does, and is maintained by addyosmani in that same repository. The rest of the collection is listed on the addyosmani/agent-skills page.

  • How does Observability and Instrumentation compare to other DevOps skills?

    Observability and Instrumentation ranks #9 by stars among the 798 DevOps skills in this catalog. The most-starred ones next to it are Backend Patterns, API Connector Builder and Migration. DirSkills ranks by the star count of the repository each skill ships in, so that order reflects how popular those repositories are rather than any review of Observability and Instrumentation against them. Open each page to compare what they document and how they install.

More from addyosmani/agent-skills

Observability and Instrumentation is one of 24 skills cataloged on DirSkills from addyosmani/agent-skills.

See all 24 skills
🔌
3w ago

API and Interface Design

API and Interface Design guides the creation of stable, well-documented interfaces including REST APIs, GraphQL schemas, module boundaries, and component props. Use it when designing new endpoints, defining contracts between teams, or changing existing public interfaces.
Quality
86.7K9.3K
🧭
3w ago

Agent Skill Discovery

Agent Skill Discovery discovers and invokes agent skills, helping an agent identify the right engineering workflow for a task. Use it when starting a session or when unsure which skill applies.
AI Engineering
86.7K9.3K
🧪
3w ago

Browser Testing

Browser Testing runs tests and inspections in a real browser via Chrome DevTools MCP. Use it when building or debugging browser UI to inspect the DOM, capture console errors, analyze network requests, profile performance, or verify visual output.
Quality
86.7K9.3K
🚀
3w ago

CI/CD and Automation

CI/CD and Automation sets up and modifies build and deployment pipelines, automating quality gates like lint, type check, tests, build, and security audits so no change reaches production without passing checks.
DevOps
86.7K9.3K
🔍
3w ago

Code Review and Quality

Code Review and Quality conducts multi-axis code review across correctness, readability, architecture, security, and performance before merging changes. Use it to assess code quality before code enters the main branch.
Quality
86.7K9.3K
🧹
3w ago

Code Simplification

Code Simplification simplifies code by reducing complexity while preserving exact behavior. Use it when refactoring for clarity, improving readability, or reviewing code that has accumulated unnecessary complexity.
Quality
86.7K9.3K