CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

90

1.08x
Quality

89%

Does it follow best practices?

Impact

90%

1.08x

Average score across 3 eval scenarios

SecuritybySnyk

High

Do not use without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

82%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A highly actionable, well-organized reference of executable log-analysis recipes that mostly respects token budget. It lacks external bundle files and carries some inline redundancy, leaving minor room for tighter conciseness and file splitting.

Suggestions

Remove the Quick Reference table or the inline duplicates it repeats, keeping one canonical form to cut redundancy and token cost.

Move the bulk recipe catalog (Advanced Analysis, Export Formats) into a references/ markdown file and link to it from SKILL.md so the main file stays a concise overview.

Add a short validation note for batch scans (e.g., confirm files exist and are non-empty before the *.jsonl pipe) so error-swallowing 2>/dev/null usage does not hide empty results.

DimensionReasoningScore

Conciseness

Mostly lean command recipes that assume Claude's competence, but the opening paragraph restates the description and the Quick Reference table duplicates commands already shown inline, adding modest redundancy.

4 / 5

Actionability

Extensive copy-paste-ready jq and bash commands with real session/variable examples covering tool stats, thinking extraction, error analysis, and exports across the common cases.

5 / 5

Workflow Clarity

Content is organized by task with clear command sequences; as a read-only log-analysis skill there is no destructive operation requiring validation, though sequencing across batch *.jsonl scans relies on implicit ordering rather than explicit checkpoints.

4 / 5

Progressive Disclosure

No bundle files exist, so all content lives in one ~318-line SKILL.md; section headers organize it well, but the volume of recipes could arguably be split into reference files, leaving minor organization gaps.

4 / 5

Total

17

/

20

Passed

Description

96%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, specific description with concrete capabilities and a rich set of natural trigger phrases covering both what and when. Minor overlap risk from generic debugging terms keeps distinctiveness just below the top anchor.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ('extract thinking blocks, tool usage stats, error patterns, debug trajectories') covering the skill's capabilities comprehensively.

5 / 5

Completeness

Explicitly answers both what ('Analyze Claude Code session logs - extract thinking blocks, tool usage stats, error patterns, debug trajectories') and when ('Triggers on: ...') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Comprehensive natural trigger phrases users would actually say ('what went wrong', 'my reasoning', 'past sessions', 'what did I do', 'session history') plus the skill name 'introspect'.

5 / 5

Distinctiveness Conflict Risk

Clear niche of session-log introspection with distinct triggers, but broad debugging phrases like 'what went wrong' carry minor overlap risk with general debugging skills.

4 / 5

Total

19

/

20

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
NeverSight/skills_feed
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.