introspect
Analyze Claude Code session logs - extract thinking blocks, tool usage stats, error patterns, debug trajectories. Triggers on: introspect, session logs, trajectory, analyze sessions, what went wrong, tool usage, thinking blocks, session history, my reasoning, past sessions, what did I do.
86
82%
Does it follow best practices?
Impact
90%
1.08xAverage score across 3 eval scenarios
Risky
Do not use without reviewing
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong skill description that clearly defines its niche (Claude Code session log analysis), lists specific capabilities, and provides comprehensive trigger terms. The explicit 'Triggers on:' clause with both technical and natural language terms makes it easy for Claude to select appropriately. The description is concise yet thorough, covering both what the skill does and when to use it.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'extract thinking blocks', 'tool usage stats', 'error patterns', 'debug trajectories'. These are clear, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers 'what' (analyze session logs, extract thinking blocks, tool usage stats, error patterns, debug trajectories) and 'when' with an explicit 'Triggers on:' clause listing specific trigger terms. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms including both technical ('thinking blocks', 'tool usage', 'trajectory') and conversational phrases ('what went wrong', 'what did I do', 'my reasoning', 'past sessions'). Good mix of how users would naturally phrase requests. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive niche focused specifically on Claude Code session log analysis. The trigger terms like 'session logs', 'thinking blocks', 'trajectory', and 'introspect' are very specific to this domain and unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a highly actionable reference skill with excellent executable examples for analyzing Claude Code session logs. Its main weakness is length - it reads more like a comprehensive reference manual than a concise skill file, with some redundancy across sections. Adding a clear workflow sequence and splitting detailed command references into a separate file would improve it significantly.
Suggestions
Add a brief workflow sequence at the top (e.g., '1. Find project dir → 2. List sessions → 3. Pick session → 4. Analyze') to guide the typical analysis process
Move the detailed command examples (Advanced Analysis, Export Formats) into a separate REFERENCE.md file and link to it from the main skill
Consolidate redundant tool usage commands that appear in multiple sections with slight variations
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is quite long (~300 lines) and while most content is actionable code, there's some redundancy across sections (e.g., tool usage stats appear in multiple places with slight variations). The privacy considerations and export formats sections add bulk that could be trimmed. However, it avoids explaining basic concepts Claude already knows. | 2 / 3 |
Actionability | Excellent actionability - nearly every section provides fully executable bash/jq commands that are copy-paste ready. The commands are specific, use real file paths and jq filters, and cover a comprehensive range of analysis tasks from basic session listing to advanced error pattern analysis. | 3 / 3 |
Workflow Clarity | The skill is organized as a reference catalog of individual commands rather than a sequenced workflow. While each command is clear, there's no explicit workflow for a typical analysis session (e.g., 'first find the session, then analyze it, then export results'). The usage examples at the end help but lack validation checkpoints. | 2 / 3 |
Progressive Disclosure | The content is a monolithic document with good section headers but no references to external files for detailed content. The quick reference table is helpful for navigation, but the sheer volume of inline examples (core analysis, advanced analysis, usage examples, export formats) could benefit from being split into separate reference files. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- NeverSight/skills_feed
- Commit
f772de4
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.