specstory-organize
Organize SpecStory AI coding sessions in .specstory/history into year/month folders. Run when user says "organize my history", "clean up specstory", "sort my sessions", or "organize specstory files".
Install with Tessl CLI
npx tessl i github:specstoryai/agent-skills --skill specstory-organize85
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
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 an excellent skill description that hits all the key criteria. It provides specific actions, clear file paths, explicit trigger phrases users would naturally say, and is highly distinctive due to the SpecStory-specific terminology. The description is concise yet comprehensive.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists a concrete action ('Organize...into year/month folders') with specific file paths ('.specstory/history') and clear organizational structure. Uses third person voice correctly. | 3 / 3 |
Completeness | Clearly answers both what ('Organize SpecStory AI coding sessions...into year/month folders') and when ('Run when user says...') with explicit trigger phrases listed. | 3 / 3 |
Trigger Term Quality | Includes excellent natural trigger phrases users would actually say: 'organize my history', 'clean up specstory', 'sort my sessions', 'organize specstory files'. Covers multiple natural variations. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with specific tool name 'SpecStory', specific path '.specstory/history', and unique trigger terms. Unlikely to conflict with other file organization 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 skill provides clear, actionable guidance with executable commands and good usage examples. However, it's verbose with unnecessary explanations (why organize, detailed output examples) and lacks explicit error handling or validation steps for a file-moving operation. The content could be 40% shorter while retaining all essential information.
Suggestions
Remove the 'Why Organize?' section entirely - Claude understands the benefits of file organization
Condense the output examples to a single brief example showing key information (file count, folder breakdown)
Add explicit error handling guidance: what to do if files fail to move, how to verify the operation succeeded
Combine 'Output' and 'Dry Run Output' sections into a single condensed example
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The 'Why Organize?' section explains benefits Claude already understands, and the example outputs are verbose. The core functionality could be conveyed in half the tokens. | 2 / 3 |
Actionability | Provides fully executable bash commands, clear slash command syntax with a table, and specific examples of both normal and dry-run usage. Copy-paste ready. | 3 / 3 |
Workflow Clarity | The 5-step 'How It Works' section describes the process clearly, but lacks explicit validation checkpoints. For a file-moving operation, there's no guidance on verifying success or handling errors beyond 'note any skips'. | 2 / 3 |
Progressive Disclosure | Content is reasonably structured with clear sections, but the extensive output examples could be condensed or moved to a separate file. The 'Present Results to User' section adds bulk that could be trimmed. | 2 / 3 |
Total | 9 / 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 |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | 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.