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.
Install with Tessl CLI
npx tessl i github:0xrabbidfly/eric-cartman --skill insights-report83
Quality
76%
Does it follow best practices?
Impact
99%
1.62xAverage score across 3 eval scenarios
Optimize this skill with Tessl
npx tessl skill review --optimize ./.github/skills/insights-report/SKILL.mdDiscovery
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 description has good structure with explicit 'Use when' guidance and a distinct niche around session log analysis. However, it could be strengthened by listing more specific concrete actions the skill performs and including additional natural trigger terms users might use when requesting this functionality.
Suggestions
Add specific concrete actions like 'identify recurring blockers, track completion rates, summarize key decisions, highlight productivity trends'
Expand trigger terms to include variations like 'session summary', 'what did I work on', 'review my sessions', 'session history'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (session logs analysis) and a general action (generate insights report), but lacks specific concrete actions like 'identify recurring blockers', 'track velocity trends', or 'summarize key decisions'. | 2 / 3 |
Completeness | Clearly answers both what ('Generate a comprehensive cross-session insights report by analyzing all captured session logs') and when ('Use when reviewing patterns across sessions or preparing retrospectives') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes some relevant terms ('session logs', 'patterns', 'retrospectives') but misses common variations users might say like 'session summary', 'what happened last week', 'review my sessions', or 'session history'. | 2 / 3 |
Distinctiveness Conflict Risk | Has a clear niche with specific path reference ('.github/sessions/'), distinct purpose (cross-session analysis), and specific triggers (retrospectives, patterns across sessions) that are unlikely to conflict with other skills. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides excellent actionability with concrete commands and clear workflow steps for analyzing session logs. However, it suffers from verbosity due to the extensive inline report template that inflates the token count significantly. The template could be externalized or condensed to key structural elements while trusting Claude to generate appropriate content.
Suggestions
Extract the full report template to a separate REPORT_TEMPLATE.md file and reference it, keeping only a condensed structural overview in the main skill
Condense the template sections to show structure and key elements rather than full example content for every section
Remove redundant explanatory text in template sections (e.g., '<Description of work done, patterns observed, outcomes>') that Claude can infer from context
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is moderately efficient but includes extensive template content that could be condensed. The full report template is verbose and could be summarized with key sections, letting Claude generate appropriate content. | 2 / 3 |
Actionability | Provides concrete, executable PowerShell commands, specific file paths, and detailed extraction instructions. The step-by-step process is clear with exact section names to parse from session files. | 3 / 3 |
Workflow Clarity | Clear 4-step sequence with explicit validation (Step 1 includes 'If no sessions found' handling). Each step has numbered sub-steps and the workflow progresses logically from discovery to report generation. | 3 / 3 |
Progressive Disclosure | Content is well-structured with clear sections, but the massive inline report template (100+ lines) could be split into a separate REPORT_TEMPLATE.md file. The skill is monolithic when it could reference external templates. | 2 / 3 |
Total | 10 / 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 | |
- 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.