Agent skill · Design & Presentation

session-deep-dive

Deep qualitative analysis of high-signal sessions. Spawns subagents with v2 template, synthesizes patterns, compares against known findings. Use after /session-scan.

oliver-kriskagithub.com/oliver-kriskaGitHub ↗
claude-codeMIT
Install
npx skills add oliver-kriska/claude-elixir-phoenix --skill session-deep-dive --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 3
SKILL.md size: 6 KB
Bundled scripts: none
Path: .claude/skills/session-deep-dive/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 515
Language: Python

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Session Deep Dive (Tier 2) Qualitative analysis of high-signal sessions identified by `/session-scan`. Spawns subagents with pre-computed metrics context for focused analysis. ## Requirements Requires **ccrider MCP**. If not available: > ccrider MCP is required. See: <https://github.com/neilberkman/ccrider> ## Usage ``` /session-deep-dive ffa155ee-ed8a-492c-8797-878fcbec4d9e /session-deep-dive --last # Most recent Tier 2 eligible /session-deep-dive --from-scan # All Tier 2 eligible from last scan /session-deep-dive --from-scan --compare .claude/UPDATED_PLUGIN_REPORT_160_SESSIONS.md ``` ## Pipeline ### Step 1: Resolve Target Sessions From `$ARGUMENTS`: - **Session ID**: Single session to analyze - **`--last`**: Most recent Tier 2 eligible session from metrics.jsonl - **`--from-scan`**: All sessions where `tier2_eligible: true` AND `tier2_completed: false` in `.claude/session-metrics/metrics.jsonl` - **`--compare REPORT.md`**: Previous report to compare against (default: most recent `.claude/session-analysis/insights-*.md`) If no metrics.jsonl exists, tell the user: > No metrics found. Run `/session-scan` first to discover and score sessions. ### Step 2: Load Pre-computed Metrics F

What's inside
Steps it walks through
  1. Requirements
  2. Usage
  3. Pipeline
  4. Step 1: Resolve Target Sessions
  5. Step 2: Load Pre-computed Metrics
  6. Step 3: Fetch Transcripts — One Subagent Per Session
  7. Step 4: Analyze Sessions
  8. Step 5: Compress (if 3+ sessions)
  9. Step 6: Synthesize
  10. Step 7: Update Ledger
  11. Step 8: Write Output
  12. Output Files
  13. Iron Laws
Ships with 2 files
  • references/analysis-template-v2.md
  • references/synthesis-template.md
Commands it runs
python3 -c "
import json
ids = {SESSION_IDS_SET}  # e.g., {'ffa155ee-...', '90a74843-...'}
lines = open('{PROJECT_ROOT}/.claude/session-metrics/metrics.jsonl').readlines()
with open('{PROJECT_ROOT}/.claude/session-metrics/metrics.jsonl', 'w') as f:
for line in lines:
entry = json.loads(line)
if entry.get('session_id') in ids:
More from claude-elixir-phoenix
All skills →
About this skill
What does the session-deep-dive skill do?

Deep qualitative analysis of high-signal sessions. Spawns subagents with v2 template, synthesizes patterns, compares against known findings. Use after /session-scan.

How do I install it?

Run `npx skills add oliver-kriska/claude-elixir-phoenix --skill session-deep-dive --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From oliver-kriska/claude-elixir-phoenix, a repository with 515 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going