specstory-session-summary
Summarize recent SpecStory AI coding sessions in standup format. Use when the user wants to review sessions from .specstory/history, prepare for standups, track work progress, or understand what was accomplished.
Install with Tessl CLI
npx tessl i github:specstoryai/agent-skills --skill specstory-session-summary90
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
89%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 well-crafted description with strong completeness and distinctiveness. It clearly identifies when to use the skill and targets a specific niche (SpecStory sessions). The main weakness is limited specificity in describing the range of concrete actions beyond summarization.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (SpecStory AI coding sessions) and one action (summarize in standup format), but doesn't list multiple concrete actions like parsing, filtering, or formatting options. | 2 / 3 |
Completeness | Clearly answers both what (summarize SpecStory sessions in standup format) and when (explicit 'Use when' clause with multiple trigger scenarios: review sessions, prepare for standups, track progress, understand accomplishments). | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'standup', 'sessions', '.specstory/history', 'track work progress', 'what was accomplished', 'review sessions' - good coverage of how users would phrase these requests. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with specific tool reference (.specstory/history), specific format (standup), and specific domain (AI coding sessions) - unlikely to conflict with generic summarization or standup skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured, actionable skill with clear step-by-step workflows and concrete examples. The main weakness is minor verbosity in explanations that Claude doesn't need (e.g., explaining what information each section captures). The executable commands, output format templates, and example output make this highly actionable.
Suggestions
Trim explanatory comments like 'This shows line numbers of user messages, helping you understand...' - Claude can infer the purpose from context
Consolidate the outcome emoji definitions into a simple table rather than a bulleted list with descriptions
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some redundancy (e.g., explaining what SpecStory is in the error message, detailed explanations of what each section captures). Could be tightened by ~20%. | 2 / 3 |
Actionability | Provides fully executable bash commands, specific grep patterns, concrete file reading strategies with exact parameters (offset=0, limit=500), and a complete output format template with examples. | 3 / 3 |
Workflow Clarity | Clear 4-step sequence with explicit branching (if no history exists, stop). Step 2 has detailed sub-steps (2a, 2b, 2c) for handling different session types. Includes fallback guidance ('If a file read fails... don't skip the session entirely'). | 3 / 3 |
Progressive Disclosure | Well-organized single file with clear sections (Context, Task steps, Guidelines, Example Output). For a skill of this complexity (~120 lines), the structure is appropriate without needing external references. | 3 / 3 |
Total | 11 / 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.
- 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.