insights-report
Generate a comprehensive cross-session insights report by analyzing all captured session logs in `.github/sessions/`. Use when reviewing patterns across sessions or preparing retrospectives.
67
51%
Does it follow best practices?
Impact
99%
1.62xAverage score across 3 eval scenarios
Risky
Do not use without reviewing
Optimize this skill with Tessl
npx tessl skill review --optimize ./.github/skills/insights-report/SKILL.mdQuality
Discovery
75%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 reasonably well-crafted description with a clear 'Use when' clause and a distinctive niche. Its main weaknesses are moderate specificity—it could enumerate what kinds of insights or analyses the report contains—and trigger term coverage that misses some natural user phrasings like 'session summary' or 'session history'.
Suggestions
Add more specific concrete actions the report includes, e.g., 'identifies recurring blockers, tracks decision patterns, summarizes key outcomes across sessions'.
Expand trigger terms to include natural variations like 'session summary', 'session history', 'what happened last session', 'review past sessions'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | It names the domain (cross-session insights report) and a key action (analyzing captured session logs), but doesn't list multiple specific concrete actions beyond 'generate a report' and 'analyzing logs'. What the report contains or what specific analyses are performed is not detailed. | 2 / 3 |
Completeness | Clearly answers both 'what' (generate a comprehensive cross-session insights report by analyzing session logs) and 'when' (use when reviewing patterns across sessions or preparing retrospectives) with an explicit 'Use when' clause. | 3 / 3 |
Trigger Term Quality | Includes some relevant terms like 'session logs', 'retrospectives', 'patterns across sessions', and the specific path '.github/sessions/'. However, it misses common variations users might say such as 'session summary', 'session review', 'what happened across sessions', or 'session history'. | 2 / 3 |
Distinctiveness Conflict Risk | The specific focus on cross-session insights from '.github/sessions/' logs and retrospectives creates a clear niche that is unlikely to conflict with other skills. The combination of session log analysis and retrospective preparation is quite distinctive. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
27%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill suffers primarily from extreme verbosity—the ~200-line report template dominates the file and represents content Claude could easily generate from a brief list of required sections. The workflow structure is reasonable but lacks validation steps for parsing potentially malformed session files. The skill would benefit enormously from extracting the template into a separate file and condensing the core instructions to focus on what Claude actually needs to know.
Suggestions
Extract the entire Step 4 report template into a separate TEMPLATE.md file and reference it from the main skill, reducing the SKILL.md to under 80 lines.
Replace the verbose template with a concise list of required report sections (e.g., 'Executive Summary, Project Areas, Top Goals, Friction Points, Tool Usage, Suggestions, Timeline') and let Claude generate appropriate content.
Add validation checkpoints: verify session file format before parsing, handle malformed/incomplete logs gracefully, and confirm parsed data completeness before generating the report.
Add executable code for session file parsing (e.g., a regex or structured extraction approach) rather than just listing field names to extract.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose at ~250+ lines, with the vast majority being a template report that Claude could generate on its own. The detailed markdown template with placeholder text like '<Description of what makes this work well>' and '<2-3 paragraphs summarizing the key findings>' is unnecessary scaffolding that Claude can produce without being shown. The entire Step 4 template could be reduced to a brief list of required sections. | 1 / 3 |
Actionability | Steps 1-3 provide reasonably concrete guidance with a PowerShell command and specific field extraction instructions. However, the bulk of the skill (Step 4) is a template with placeholder text rather than executable guidance. The parsing instructions in Step 2 reference section names but don't provide code for extraction. | 2 / 3 |
Workflow Clarity | The 4-step sequence (Discover → Parse → Analyze → Generate) is clear and logical, with a good early exit condition in Step 1 for no sessions found. However, there are no validation checkpoints—no verification that parsed data is complete, no handling of malformed session files, and no feedback loop for incomplete or corrupted session logs. | 2 / 3 |
Progressive Disclosure | The entire skill is a monolithic wall of text with no references to external files. The massive report template is inlined when it could easily be a separate TEMPLATE.md file. No bundle files are provided despite the content clearly benefiting from splitting the template, analysis patterns, and core instructions into separate files. | 1 / 3 |
Total | 6 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- 0xrabbidfly/eric-cartman
- Commit
17bd06f
- 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.