braintrust-analyze
This skill analyzes session logs to report on agent performance, tool usage, token consumption, and task productivity.
Install
mkdir -p .claude/skills/braintrust-analyze && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/3802" && unzip -o skill.zip -d .claude/skills/braintrust-analyze && rm skill.zipInstalls to .claude/skills/braintrust-analyze
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Analyze Claude Code sessions via BraintrustKey capabilities
- →Summarize session tool usage
- →Identify repeated loop patterns
- →Track agent productivity metrics
- →Generate token consumption trends
How it works
Parses session traces exported by the agent to correlate events and tool calls, providing statistical breakdowns of behavior.
Inputs & outputs
When to use braintrust-analyze
- →Analyze recent session performance
- →Detect repeated loop patterns
- →Report weekly agent token usage
- →Review skill activation frequency
About this skill
Braintrust Analysis
Analyze your Claude Code sessions for patterns, issues, and insights using Braintrust tracing data.
When to Use
- After completing a complex task (retrospective)
- When debugging why something failed
- Weekly review of productivity patterns
- Finding opportunities to create new skills
- Understanding token usage trends
Commands
Run from the project directory:
# Analyze last session - summary with tool/agent/skill breakdown
uv run python -m runtime.harness scripts/braintrust_analyze.py --last-session
# List recent sessions
uv run python -m runtime.harness scripts/braintrust_analyze.py --sessions 5
# Agent usage statistics (last 7 days)
uv run python -m runtime.harness scripts/braintrust_analyze.py --agent-stats
# Skill usage statistics (last 7 days)
uv run python -m runtime.harness scripts/braintrust_analyze.py --skill-stats
# Detect loops - find repeated tool patterns (>5 same tool calls)
uv run python -m runtime.harness scripts/braintrust_analyze.py --detect-loops
# Replay specific session - show full sequence of actions
uv run python -m runtime.harness scripts/braintrust_analyze.py --replay <session-id>
# Weekly summary - daily activity breakdown
uv run python -m runtime.harness scripts/braintrust_analyze.py --weekly-summary
# Token trends - usage over time
uv run python -m runtime.harness scripts/braintrust_analyze.py --token-trends
Options
--project NAME- Braintrust project name (default: agentica)
What You'll Learn
Session Analysis
- Tool usage breakdown
- Agent spawns (plan-agent, debug-agent, etc.)
- Skill activations (/commit, /research, etc.)
- Token consumption estimates
Loop Detection
Find sessions where the same tool was called repeatedly, which may indicate:
- Stuck in a search loop
- Inefficient approach
- Opportunity for better tooling
Usage Patterns
- Which agents you use most
- Which skills get activated
- Daily/weekly activity trends
Examples
Quick Retrospective
# What happened in my last session?
uv run python -m runtime.harness scripts/braintrust_analyze.py --last-session
Output:
## Session Analysis
**ID:** `92940b91...`
**Started:** 2025-12-24T01:31:05Z
**Spans:** 14
### Tool Usage
- Read: 4
- Bash: 2
- Edit: 2
...
Find Loops
uv run python -m runtime.harness scripts/braintrust_analyze.py --detect-loops
Weekly Review
uv run python -m runtime.harness scripts/braintrust_analyze.py --weekly-summary
Requirements
- BRAINTRUST_API_KEY in ~/.claude/.env or project .env
- Braintrust tracing enabled (via braintrust-claude-plugin)
When not to use it
- →When analyzing non-agentic logs that lack Braintrust traces
- →When security constraints prohibit log data transmission
Prerequisites
Limitations
- →Only works if Braintrust tracing is active during sessions
- →Requires project-specific Braintrust configuration
How it compares
It enables analytical retrospection on agent behavior, whereas generic logs are only used for individual error debugging.
Compared to similar skills
braintrust-analyze side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| braintrust-analyze (this skill) | 1 | 7mo | Review | Intermediate |
| elasticsearch-analysis | 2 | 5mo | Review | Intermediate |
| agent-session-monitor | 2 | 6mo | Review | Intermediate |
| analyze-log-files | 1 | 2mo | Review | Beginner |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by parcadei
View all by parcadei →You might also like
elasticsearch-analysis
incidentfox
Elasticsearch/OpenSearch log analysis using Lucene query syntax and Query DSL. Use when investigating issues via ELK stack, OpenSearch, or any Elasticsearch-based logging.
agent-session-monitor
alibaba
Real-time agent conversation monitoring - monitors Higress access logs, aggregates conversations by session, tracks token usage. Supports web interface for viewing complete conversation history and costs. Use when users ask about current session token consumption, conversation history, or cost statistics.
analyze-log-files
r3bl-org
Analyze log files by stripping ANSI escape sequences first. Use when asked to process, handle, read, or analyze log files that may contain terminal escape codes.
tldr-stats
parcadei
Show full session token usage, costs, TLDR savings, and hook activity
massgen-log-analyzer
massgen
Run MassGen experiments and analyze logs using automation mode, logfire tracing, and SQL queries. Use this skill for performance analysis, debugging agent behavior, evaluating coordination patterns, and improving the logging structure, or whenever an ANALYSIS_REPORT.md is needed in a log directory.
observability
incidentfox
Log, metric, and trace analysis methodology. Use when analyzing logs, investigating errors, querying metrics, or correlating signals across observability backends (Coralogix, Datadog, CloudWatch).