Skip to content
SkillModel-led3,107 tokens in use

observability-and-instrumentation

Instrument production code with structured logs, RED and USE metrics, OpenTelemetry traces and symptom-based alerts.

119,377 stars on the repository MIT Licenseaddyosmani/agent-skills · skills/observability-and-instrumentation
npx skills add addyosmani/agent-skills --skill observability-and-instrumentation
View source

Install command as written in the repository's README

Skill label

measured from its files

What installing observability-and-instrumentation costs

67tokens idle
3,107tokens in use

Idle is what sits in context while the skill is installed. In use is its instructions, loaded when it runs. Counts are approximate, made offline with cl100k_base.

Model dependence Model-led

Script-ledMixedModel-led

Mostly instructions, so how well it works depends on the model that follows them.

This describes the skill's structure, how much of it is scripts. It does not say how well it works.

Touches

Nothing detected: no shell, network, file writes, git or credentials in its files.

Declared tags come from the skill's frontmatter; detected ones from its scripts, its code blocks and the commands it names in inline code. This is detected, not audited.

How it scores

Quality

How well the skill is written, counted from its own files: its frontmatter, its steps, examples, stated output and constraints, its size and whether every file it ships is one it names.How we score it →
Excellent
  • Frontmatter12/15
  • Structure25/25
  • Examples15/15
  • Output15/15
  • Size13/15
  • Resources10/15

Security

Starts at 100 and loses points for each thing in the skill's files that a reader should look at first.How we score it →
Excellent

No findings.

Repository health

Pre-computed score based on development activity, maintenance, community, maturity, and trend momentum.How we score it →
Excellent
  • Development activity96
  • Maintenance100
  • Community76
  • Maturity32
  • Momentum40

Observability and Instrumentation tells an agent to write telemetry alongside the feature. It starts by writing the questions an on-call engineer will ask, then picks logs, metrics or traces to answer each one.

The skill covers structured logging with correlation IDs and entry-point fields, RED and USE metrics with bounded labels, OpenTelemetry tracing, symptom-based alerting, minimal runbooks and a step for verifying that the telemetry works.

What You Get

  • A seven-step process from on-call questions to telemetry verification
  • A table matching logs, metrics and traces to the questions they answer
  • TypeScript examples for Express logging, Prometheus histograms and OpenTelemetry setup
  • A runbook template, red flags and a verification checklist

Common Use Cases

  • Adding logging and metrics to a new service
  • Setting up alerting rules
  • Reviewing a pull request that adds retries or queues
  • Making production incidents easier to diagnose

What Makes It Unique

The skill is firm about cardinality, with a list of what can and cannot be a metric label, and about naming the entry point when a scheduler, a replay endpoint and a CLI write to one log. It limits alerts to two severities and requires each alert to be actionable.

Under The Hood

The skill is a single SKILL.md of instructions with TypeScript examples. It runs no scripts. The code it asks for adds OpenTelemetry and Prometheus client libraries and sends telemetry to a backend you choose, and it tells the agent to test by inducing errors in staging.

Join founders building with open source

Opinionated takes, migration guides, cost-saving tips, and insights from the open source ecosystem.

Subscribe on SubstackJoin 750+ subscribers