Skip to content
Back to skills

Llm Observability Evals

ASecurity

LLM and agent observability, tracing, and evaluation workflows with langfuse, phoenix-cli, and phoenix-evals. Use when instrumenting Langfuse, Phoenix, OpenTelemetry GenAI traces, eval datasets, prompt experiments, latency/cost debugging, trace scoring, or regression testing agent behavior.

  • 8 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added September 12, 2026
ai-agentsgotestingdebugging

Works with

  • cli

Security analysis

A100/100

Scanned September 12, 2026

npx -y skills add stanfish06/skillquarium --skill llm-observability-evals --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Llm Observability Evals?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Llm Observability Evals
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/stanfish06-llm-observability-evals/badge)](https://www.skillsdirectory.com/skills/stanfish06-llm-observability-evals)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: llm-observability-evals
description: LLM and agent observability, tracing, and evaluation workflows with langfuse, phoenix-cli, and phoenix-evals. Use when instrumenting Langfuse, Phoenix, OpenTelemetry GenAI traces, eval datasets, prompt experiments, latency/cost debugging, trace scoring, or regression testing agent behavior.
---

# LLM Observability + Evals

Use this skill to make LLM and agent behavior measurable. It routes across installed observability skills and provides the evaluation loop that connects traces, datasets, scorers, and regressions.

## Routing

- Use `langfuse` for Langfuse tracing, prompt management, datasets, and production observability.
- Use `phoenix-cli` and `phoenix-evals` for Phoenix tracing/evaluation workflows.
- Use this skill when deciding what to instrument, how to score behavior, or how to turn traces into tests.

## Workflow

1. Define the behavior to measure:
   - task success
   - factuality
   - tool correctness
   - latency
   - cost
   - refusal/guardrail behavior
2. Instrument traces around meaningful spans:
   - user request
   - planner/router decisions
   - retrieval
   - tool calls
   - model calls
   - final answer
3. Capture inputs, outputs, model/provider, token counts, latency, tool arguments, and error states.
4. Build eval datasets from:
   - known regression cases
   - sampled production traces
   - synthetic adversarial cases
   - golden examples from domain experts
5. Add scorers:
   - deterministic checks for schemas, citations, or tool outcomes
   - LLM-as-judge only with rubrics and calibration examples
   - human review for high-risk workflows
6. Run evals before prompt, model, tool, or retrieval changes.

## Reporting

Report pass rate, cost, latency, sample size, scorer definitions, confidence limits where relevant, and the exact prompt/model/tool versions under test.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.