llm-observability

Trace LLM calls with OpenTelemetry GenAI semantic conventions and enforce governance policies.

3|Updated Sep 27, 2025
One-click install
npx skills add https://github.com/Sheldon-92/TAD --skill llm-observability
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: llm-observability
Source: https://github.com/Sheldon-92/TAD/tree/main/.agents/skills/llm-observability
Command: npx skills add https://github.com/Sheldon-92/TAD --skill llm-observability

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

LLM observability and LLMOps capability pack provides the rules, tooling, and patterns needed to monitor, measure, and govern AI agents in production, including tracing, cost attribution, drift detection, and prompt/versioning governance.

Core Features & Use Cases

  • OpenTelemetry GenAI semantic conventions adoption and telemetry conformance checks.
  • End-to-end production observability: tracing, latency profiling (TTFT/ITL), and per-call cost attribution with four-layer token accounting.
  • Drift detection, grounding checks, and online evaluation for high-stakes LLM deployments.
  • Centralized prompt registry and versioning discipline to enforce stable operational templates.

Quick Start

Apply this pack to your LLM-powered system to enable production-grade observability and governance.

Frequently Asked Questions about llm-observability

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

FAQPage Schema
How do I implement LLM observability and tracing for production AI agents?

LLM observability enables structured tracing, latency profiling, and per-call cost attribution for production AI agents. It applies OpenTelemetry GenAI semantic conventions to monitor distributed LLM deployments across self-hosted or cloud environments.

What is drift detection in LLMOps and how does it work?

Drift detection in LLMOps identifies performance degradation and behavioral changes in high-stakes LLM deployments. It works by running online evaluation workflows and grounding checks alongside continuous telemetry monitoring.

How do I calculate per-call LLM cost attribution with token accounting?

Per-call LLM cost attribution uses four-layer token accounting to measure resource consumption for individual inference requests. This approach tracks token usage across distributed deployments to deliver precise operational cost measurement.

Can I use OpenTelemetry GenAI semantic conventions for telemetry conformance checks?

Yes, OpenTelemetry GenAI semantic conventions are supported for telemetry conformance checks. The system enforces conformance rules and budgets while applying registry-driven prompt management to ensure auditable AI operations.

What is the best way to manage prompt versioning policies for LLM deployments?

Prompt versioning policies are managed through a centralized prompt registry enforcing stable operational templates. This registry-driven approach delivers reliable governance by maintaining strict versioning discipline across distributed LLM systems.

Does LLM observability support TTFT and ITL latency profiling?

Yes, LLM observability supports TTFT and ITL latency profiling to measure end-to-end production performance. These metrics enable detailed latency analysis for distributed LLM deployments, ensuring reliable and auditable AI operations.