skills.rest
z1439527767
z1439527767COMMUNITY
Explore all skills by this author →
WebsiteGitHub

agenttrace-session-audit

Audit AI coding-agent session traces for cost, failure, latency, and reliability issues.

Updated Jun 25, 2026
Search Tags:#observability#session-analysis#ai-coding#cost-tracking#ci-health#agenttrace
One-click install
npx skills add https://github.com/z1439527767/claude-config --skill agenttrace-session-audit
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: agenttrace-session-audit
Source: https://github.com/z1439527767/claude-config/tree/main/skills/imported/agenttrace-session-audit
Command: npx skills add https://github.com/z1439527767/claude-config --skill agenttrace-session-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers understand slow, expensive, or unreliable AI coding-agent runs by analyzing session traces for failures, inefficiencies, and anomalies.

Core Features & Use Cases

  • Session Auditing: Analyze AI coding-agent logs for cost spikes, tool failures, latency gaps, retries, and health signals.
  • Run Comparison and CI Checks: Compare attempts for workflow drift and create automated health gates using trace metrics.
  • Use Case: Review a failed AI-assisted coding task to identify whether the issue came from excessive retries, broken tools, poor execution paths, or missing validation steps.

Quick Start

Use the agenttrace session audit skill to inspect my latest AI coding-agent run and summarize any reliability problems.

Frequently Asked Questions about agenttrace-session-audit

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

FAQPage Schema
How do I audit AI coding-agent sessions for cost spikes and tool failures?▼

To audit AI coding-agent sessions for cost spikes and tool failures, you analyze session traces to identify reliability problems, excessive retries, and broken execution paths. This process reviews local session data to surface inefficiencies and anomalies.

What causes high latency and retries in AI coding-agent runs?▼

High latency and retries in AI coding-agent runs are caused by broken tools, poor execution paths, or missing validation steps. Session trace analysis isolates these specific failures and workflow drift to pinpoint the exact bottleneck.

Can I create CI health checks using AI coding-agent trace metrics?▼

Yes, you can create CI health checks using AI coding-agent trace metrics by applying session analysis to build automated health gates. This compares coding attempts and uses reliability signals to block bad deployments.

Do I need agenttrace session discovery to analyze local AI coding logs?▼

Yes, agenttrace session discovery is required to analyze local AI coding logs. It provides the necessary trace data inputs for the audit process to detect cost tracking issues, latency gaps, and tool failures safely.

What's the best way to compare AI coding-agent attempts for workflow drift?▼

The best way to compare AI coding-agent attempts for workflow drift is to analyze session traces side-by-side. This structured comparison evaluates execution paths, retry rates, and cost variations to identify deviations.

Related Skills

Explore More Software Engineering Skills→
yoshihiko555yoshihiko555

checkpointing

Persist session context and CLI interactions into agent configuration checkpoints.

Community
Intermediate
Zenobia000Zenobia000
2

continuous-agent-loop

Configure monitored autonomous agent loops with quality gates and failure recovery.

Community
Advanced
camoneartcamoneart
5

grafana-dashboards

Design and deploy Grafana dashboards for real-time system and application metrics.

Community
Intermediate
tedtv1007-ctrltedtv1007-ctrl

session-logs

Search and analyze local JSONL conversation history files with jq and ripgrep.

Community
Intermediate