agentv-trace-analyst

Analyze AgentV evaluation traces with CLI commands and jq.

15|3|Updated Nov 7, 2025
One-click install
npx skills add https://github.com/EntityProcess/agentv --skill agentv-trace-analyst
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agentv-trace-analyst
Source: https://github.com/EntityProcess/agentv/tree/main/plugins/agentv-dev/skills/agentv-trace-analyst
Command: npx skills add https://github.com/EntityProcess/agentv --skill agentv-trace-analyst

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps users understand and debug the results of AgentV evaluations by providing tools to analyze trace data, identify performance bottlenecks, and detect regressions.

Core Features & Use Cases

  • Analyze Evaluation Results: Inspect detailed execution traces from AgentV evaluations.
  • Identify Failure Patterns: Pinpoint tests with low scores, excessive latency, or high costs.
  • Compare Runs: Perform A/B testing between different evaluation runs to track improvements or regressions.
  • Use Case: After running a new version of your agent, use this Skill to compare its performance against the previous version, identifying any new failure modes or performance degradations.

Quick Start

Use the agentv-trace-analyst skill to list the most recent AgentV evaluation results.

Frequently Asked Questions about agentv-trace-analyst

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

FAQPage Schema
How do I analyze AgentV evaluation traces to identify failure patterns?

Analyze AgentV evaluation traces by using CLI primitives and jq for detailed inspection to pinpoint tests with low scores, excessive latency, or high costs. It scopes to identifying failure patterns by computing cost and latency statistics from trace data to help debug results.

How do I compare AgentV evaluation runs for performance regressions?

Compare AgentV evaluation runs by performing A/B testing between different execution traces to track improvements or regressions. This identifies new failure modes or performance degradations after running a new agent version against the previous one.

What can I do when agent performance debugging requires computing cost and latency statistics?

Compute cost and latency statistics by analyzing trace data with jq and CLI primitives for flexible data manipulation. This provides deterministic task execution via agentv trace commands to help understand and debug evaluation results.

Do I need jq to inspect AgentV execution traces?

Yes, jq is needed to inspect AgentV execution traces as it enables flexible data manipulation during analysis. The process combines jq with deterministic task execution via agentv trace commands for detailed inspection of evaluation results.

What is the best way to debug AgentV evaluation bottlenecks?

The best way to debug AgentV evaluation bottlenecks is by inspecting detailed execution traces to identify performance issues. Using CLI primitives and jq allows you to list recent results and reason about agent performance from trace data.