← ClaudeAtlas

observabilitylisted

Query and analyze agent JSONL event logs for debugging, performance analysis, and decision tracing. Use when investigating agent behavior, finding slow tool calls, tracing decisions, or analyzing session performance.
rjmurillo/ai-agents · ★ 33 · AI & Automation · score 79
Install: claude install-skill rjmurillo/ai-agents
# Agent Observability Skill Query structured JSONL event logs to understand agent behavior, debug failures, and analyze performance. ## Triggers | Trigger Phrase | Operation | |----------------|-----------| | `query agent logs` | Run query_logs.py with filters | | `find slow tool calls` | Run with --slow threshold | | `show agent errors` | Run with --errors-only | | `summarize session performance` | Run with --output summary-sessions | | `analyze tool usage` | Run with --output summary-tools | ## When to Use Use this skill when: - Debugging why an agent chose a particular tool or approach - Finding slow tool calls that degrade agent performance - Analyzing error patterns across agent sessions - Comparing tool usage across sessions or agents - Tracing decisions from orchestrator through sub-agents Use direct log file inspection instead when: - Checking a single known event in a small log - The log file has fewer than 10 events ## Event Schema Logs use JSONL format (one JSON object per line). See `schema.json` for the full JSON Schema. ### Event Types | Type | Purpose | Key Fields | |------|---------|------------| | session_start | Agent invocation begins | agent, session_id | | session_end | Agent invocation completes | agent, session_id | | tool_call | Tool invocation with timing | tool.name, tool.duration_ms, tool.success | | decision | Reasoning captured alongside action | decision.action, decision.reasoning | | metric | Numeric measurement | metric.name, metric