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 concrete capabilities, and provides an extensive set of natural trigger terms. The explicit 'Triggers on:' clause with both technical and conversational keywords makes it easy for Claude to select this skill appropriately. The description is concise yet comprehensive.
| 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 weaknesses are its length (could be split into overview + detailed references) and the lack of a clear end-to-end workflow with validation steps. The quick reference table is a nice touch but the overall document would benefit from better progressive disclosure.
Suggestions
Add a brief 'Getting Started' workflow at the top that sequences the key steps: 1) Find project directory, 2) List sessions, 3) Pick a session, 4) Run overview analysis - with a validation check that the project path exists.
Split the document: keep core patterns and quick reference in SKILL.md, move Advanced Analysis, Export Formats, and Usage Examples into separate referenced files (e.g., ADVANCED.md, EXAMPLES.md).
| 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 'how to analyze a session from start to finish' with validation checkpoints. The usage examples at the end help but lack verification steps (e.g., checking if the project directory exists before running queries). | 2 / 3 |
Progressive Disclosure | The content is well-structured with clear headers and a logical progression from basics to advanced, plus a quick reference table. However, at ~300 lines this is a monolithic document that could benefit from splitting advanced analysis, export formats, and usage examples into separate referenced 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
9f4534c
- 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.