Agent skill · Code Review & Quality

session-profiler

Profile and debug Hermes sessions from their JSONL transcripts. Find a session and its subagents, build a queryable event table, summarize the work as a hierarchical table of contents, break down wall time, inference, tools, tokens, and estimated cost per agent, identify errors and improvement opportunities, and export a shareable Perfetto trace. Use when a user wants to inspect what a Hermes session did, debug agent or subagent activity, understand session cost or latency, create a session timeline, generate a trace, or learn how to improve the next agent run.

tamdogoodgithub.com/tamdogoodGitHub ↗
claude-codecodexships scriptsMIT
Install
npx skills add tamdogood/builder-essential-skills --skill session-profiler --agent claude-code

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

Facts
Files in the skill folder: 18
SKILL.md size: 6 KB
Bundled scripts: yes
Path: skills/session-profiler/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 90
Language: Python

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

From the SKILL.md

# Session Profiler Turn one Hermes main transcript plus its subagent transcripts into analysis artifacts. Route every operation through the bundled wrapper so it uses a consistent environment and remembers the latest parsed work directory. ```bash SP="$SKILL/scripts/sp" ``` Resolve `SKILL` to this skill's directory. If it is unavailable, use the absolute path to `scripts/sp` beside this file. ## Workflow 1. Find and inspect the session. ```bash $SP projects $SP list [--provider hermes] [--n 20] $SP list --project-dir "${HERMES_HOME:-$HOME/.hermes}/sessions" $SP find <session-id-prefix> $SP info <session-id-or-path> ``` Hermes stores rollouts under `${HERMES_HOME:-~/.hermes}/sessions/YYYY/MM/DD/rollout-*.jsonl` and archived rollouts under `archived_sessions/`. Hermes subagent rollouts identify their parent thread recursively in `session_meta`. 2. Parse the session before analyzing it. Re-run this for a session that is still active. ```bash $SP parse <session-id-or-main-jsonl-path> ``` The command prints and remembers its work directory. It writes `events.parquet`, `events.csv`, and `agents.json`. Override the remembered directory with global `--data-dir <dir>` or `SESSION_DATA_DIR`.

What's inside
Steps it walks through
  1. Workflow
  2. Interpretation Rules
  3. Privacy And Failure Handling
Ships with 17 files
  • README.md
  • agents/openai.yaml
  • scripts/requirements.txt
  • scripts/session_profiler/__init__.py
  • scripts/session_profiler/analyses.py
  • scripts/session_profiler/cli.py
  • scripts/session_profiler/dataset.py
  • scripts/session_profiler/discover.py
  • scripts/session_profiler/toc.py
  • scripts/session_profiler/trace.py
  • scripts/sp
  • scripts/tests/fixture/main.jsonl
  • scripts/tests/fixture/main/subagents/agent-abc.jsonl
  • scripts/tests/fixture/main/subagents/agent-abc.meta.json
  • scripts/tests/hermes_home/sessions/2026/01/01/rollout-child.jsonl
  • scripts/tests/hermes_home/sessions/2026/01/01/rollout-root.jsonl
  • scripts/tests/test_fixture.py
More from builder-essential-skills
All skills →
About this skill
What does the session-profiler skill do?

Profile and debug Hermes sessions from their JSONL transcripts. Find a session and its subagents, build a queryable event table, summarize the work as a hierarchical table of contents, break down wall time, inference, tools, tokens, and estimated cost per agent, identify errors and improvement opportunities, and export a shareable Perfetto trace. Use when a user wants to inspect what a Hermes session did, debug agent or subagent activity, understand session cost or latency, create a session timeline, generate a trace, or learn how to improve the next agent run.

How do I install it?

Run `npx skills add tamdogood/builder-essential-skills --skill session-profiler --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 tamdogood/builder-essential-skills, a repository with 90 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