ln-002-session-analyzer
Analyzes current or recent session for errors, inefficiencies, and improvement opportunities across skills, tools, hooks, and communication. Use after completing a task or periodically.
npx skills add majiayu000/claude-skill-registry --skill ln-002-session-analyzer-levnikolaevich-claude-code-skills --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.
> **Paths:** File paths (`shared/`, `references/`, `../ln-*`) are relative to skills repo root. If not found at CWD, locate this SKILL.md directory and go up one level for repo root. If `shared/` is missing, fetch files via WebFetch from `https://raw.githubusercontent.com/levnikolaevich/claude-code-skills/master/skills/{path}`. # Session Analyzer (Standalone Utility) **Type:** Standalone Utility **Category:** 0XX Shared Analyzes a session for errors, inefficiencies, and improvement opportunities. Produces actionable fixes for skills, tools, hooks, and communication style. **Scope:** Single-session deep analysis (10 dimensions). Broader than protocol self-audit, narrower than `/audit-sessions` batch. For skill self-audit: `shared/references/meta_analysis_protocol.md` §7. For multi-day patterns: `/audit-sessions`. --- ## When to Use This Skill - After completing a task — find what went wrong and how to improve - Periodically — audit recent sessions for patterns - After a skill run — analyze how well the skill instructions worked - When debugging tool/hook issues — find root causes in session data --- ## Input `$ARGUMENTS`: - (empty) — analyze current session (conversation context) -
- When to Use This Skill
- Input
- Dimensions
- Phase 1: Collect Session Data
- Current session (empty args)
- Recent sessions (recent arg)
- Extract raw data from JSONL session
- Phase 2: Analyze by Dimensions
- D1: Tool Errors
- D2: Tool Waste
- D3: Process Issues
- D4: Script Extraction
- D5: Hook & Permission
- D6: Communication
echo "=== LATEST SESSIONS ===" echo "## Claude" echo "## Codex" echo "## Gemini" echo "=== TOOL CALLS ===" grep -oE '"name"\s*:\s*"[^"]*"' "$F" 2>/dev/null | sed 's/"name"\s*:\s*"//;s/"//' | sort | uniq -c | sort -rn | head -30 echo "=== ERRORS ===" echo "=== TOOL LOOPS (3+ consecutive) ===" grep -oE '"name"\s*:\s*"[^"]*"' "$F" 2>/dev/null | sed 's/"name"\s*:\s*"//;s/"//' | uniq -c | sort -rn | awk '$1 >= 3' echo "=== BUILT-IN vs MCP ==="
What does the ln-002-session-analyzer skill do?
Analyzes current or recent session for errors, inefficiencies, and improvement opportunities across skills, tools, hooks, and communication. Use after completing a task or periodically.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill ln-002-session-analyzer-levnikolaevich-claude-code-skills --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.