analyze-sessions
Analyze session logs to discover automation opportunities. Use periodically to find patterns in your Claude Code usage that could be automated. Use periodically after multiple sessions to find automation opportunities.
npx skills add majiayu000/claude-skill-registry --skill analyze-sessions --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
Analyze recorded session data from ALL Claude Code projects to identify patterns and automation opportunities. ## Arguments - `--project <name>` — Analyze only sessions from the named project (matches the `project` field, which is the basename of the working directory) - `--targets-only` — Exclude toolkit sessions; only analyze target projects ## Data Location Session logs are stored centrally in `~/.claude/logs/sessions.jsonl` in JSONL format (one compact JSON object per line). Each entry contains: ```json {"session_id":"...","timestamp":"2026-01-23T12:00:00Z","project":"project-name","cwd":"/path/to/project","transcript_path":"/path/to/transcript"} ``` The session-end-logger hook is installed at the user level (`~/.claude/hooks/session-end-logger.sh`) so it captures sessions from every project. ## Analysis Process Copy this checklist and track progress: ``` Analyze Sessions Progress: - [ ] Step 1: Read session logs - [ ] Step 2: Calculate statistics (grouped by project) - [ ] Step 3: Identify target projects - [ ] Step 4: Analyze transcripts - [ ] Step 5: Find automation opportunities - [ ] Step 6: Cross-project insights - [ ] Step 7: Generate report ``` ### 1. Read Session Logs
- Arguments
- Data Location
- Analysis Process
- 1. Read Session Logs
- 2. Calculate Statistics (Grouped by Project)
- 3. Identify Target Projects
- 4. Analyze Transcripts (If Available)
- 5. Identify Automation Opportunities
- 6. Cross-Project Insights
- 6b. Review Findings Before Writing
- 7. Generate Report
- 8. Output Summary
- Error Handling
- Limitations
What does the analyze-sessions skill do?
Analyze session logs to discover automation opportunities. Use periodically to find patterns in your Claude Code usage that could be automated. Use periodically after multiple sessions to find automation opportunities.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill analyze-sessions --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 majiayu000/claude-skill-registry, a repository with 534 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.