agent-observability

Instruments OpenTelemetry-based traces and AI agent decision chains for observability and evaluation.

Updated Apr 13, 2026
One-click install
npx skills add https://github.com/bermudi/skills --skill agent-observability-bermudi
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: agent-observability
Source: https://github.com/bermudi/skills/tree/main/agent-observability
Command: npx skills add https://github.com/bermudi/skills --skill agent-observability-bermudi

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides end-to-end observability for AI agents by recording decisions, tools, and model interactions to enable tracing, evaluation, and continuous improvement.

Core Features & Use Cases

  • Structured traces and OpenTelemetry spans for agent decision chains.
  • Evals and LLM-as-Judge scoring to assess output quality and trajectory.
  • A quality loop that turns production failures into regression tests and guides debugging.

Quick Start

Set up OpenTelemetry instrumentation in your agent and emit a root span for each run.

Frequently Asked Questions about agent-observability

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I trace AI agent decisions and tool calls end-to-end?▼

You trace AI agent decisions by instrumenting your code with OpenTelemetry-based spans, recording each model interaction and tool call into a structured decision chain for full visibility.

What is the LLM-as-Judge method for evaluating agent outputs?▼

LLM-as-Judge is an evaluation method where a language model scores the quality of another agent's output and trajectory, enabling automated assessment of agent decisions without manual human review.

How do I turn production agent failures into regression tests?▼

You turn production agent failures into regression tests by running a quality loop that captures failed traces and eval scores, automatically converting them into test cases for continuous debugging.

Does this observability approach support OpenTelemetry instrumentation?▼

Yes, this observability approach supports OpenTelemetry instrumentation, allowing you to emit a root span for each agent run and record structured traces for decision chains and tool calls.

Why do I need observability for my AI agent decision chains?▼

You need observability for AI agent decision chains to gain visibility into model interactions and tool calls, enabling effective debugging, output evaluation, and continuous improvement of production agents.

Can I use code-based evals alongside LLM-as-Judge for agent tracing?▼

Yes, you can use code-based evals alongside LLM-as-Judge scoring within the quality loop to assess agent output quality and trajectory, capturing failures for regression testing.