braintrust-analyze

What the source does

• FilesystemNone observedNo reads or writes in the source
• NetworkNone observedNo outbound calls in the source
• ShellNone observedNo commands run in the source
• DependenciesPinnedNothing floats
• SecretsNone foundNo keys in source

Five audit layers

Gates applied: no behavioural pass.

.claude/scripts/mcp

Audit 0.4.1 · source sha 79ffdab59d4c · 29 Oct 2026Report an issue or request a re-scan

• Publisherparcadei GitHub userOwner of the repository this skill is read from
• Source folderparcadei/continuous-claude-v3/.claude/skills/braintrust-analyzeThe exact folder we audited
• LicenceMITAs the repository states it
• Commit pinned for this verdict79ffdab59d4cA new audit runs when the source changes
• Repository statusNot archivedLast push 275 days ago
• Sandboxed runNot runSkills are read, not executed; layer L4 is skipped

Its description: Analyze Claude Code sessions via Braintrust

---
name: braintrust-analyze
description: Analyze Claude Code sessions via Braintrust
---

# 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:

```bash
# 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
```bash
# 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
```bash
uv run python -m runtime.harness scripts/braintrust_analyze.py --detect-loops
```

### Weekly Review
```bash
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)

Excerpt, first 2,727 characters of SKILL.md, verbatim from the audited commit. It is text from someone else’s repository, quoted so you can judge it before your agent reads it.

1. 2026-10-29
   ✓SAFE B 89 / 100

   first audit · source 79ffdab59d4c

Questions about braintrust-analyze

• github.com/parcadei/continuous-claude-v3/tree/main/.claude/skill — the audited source at commit 79ffdab59d4c and every finding aboveObserved · 29 Oct 2026

Spotted something wrong? Report a correction · Methodology