user-story-generator
User Story Generator - Auto-activating skill for Enterprise Workflows. Triggers on: user story generator, user story generator Part of the Enterprise Workflows skill category.
39
Quality
7%
Does it follow best practices?
Impact
100%
1.03xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/20-enterprise-workflows/user-story-generator/SKILL.mdQuality
Discovery
7%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 is severely underdeveloped, essentially serving as a placeholder rather than a functional skill description. It lacks concrete actions, meaningful trigger terms, and explicit guidance on when to use the skill. The redundant trigger term and reliance on category metadata provide no value for skill selection.
Suggestions
Add specific capabilities: 'Generates user stories with acceptance criteria, story points, and persona-based formatting. Supports Gherkin syntax and agile story templates.'
Include a 'Use when...' clause: 'Use when the user asks to write user stories, create backlog items, draft acceptance criteria, or work on agile/scrum artifacts.'
Expand trigger terms to include natural variations: 'user stories, backlog items, acceptance criteria, agile stories, product requirements, as a user I want, story points'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('User Story Generator') without describing any concrete actions. There are no specific capabilities listed like 'creates acceptance criteria', 'generates story points', or 'formats in Gherkin syntax'. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and while it mentions triggers, there is no 'Use when...' clause explaining when Claude should select this skill. The category mention ('Enterprise Workflows') provides no actionable guidance. | 1 / 3 |
Trigger Term Quality | The trigger terms are redundant ('user story generator' listed twice) and miss natural variations users would say like 'write user stories', 'agile stories', 'product backlog items', 'acceptance criteria', or 'as a user I want'. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'user story' is somewhat specific to agile/product management contexts, which provides some distinctiveness. However, without concrete actions described, it could conflict with general writing or documentation skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
7%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is essentially a placeholder with no actionable content. It describes capabilities in abstract terms but provides zero concrete guidance on how to generate user stories - no templates, no examples, no format specifications, no acceptance criteria patterns. The content fails to teach Claude anything it doesn't already know.
Suggestions
Add a concrete user story template with format specification (e.g., 'As a [role], I want [feature], so that [benefit]') and example outputs
Include specific acceptance criteria patterns and examples showing input requirements mapped to generated stories
Provide executable guidance: what information to gather, how to structure the story, validation checklist for completeness
Remove generic boilerplate sections ('Capabilities', 'Example Triggers') and replace with actual instructional content
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that provides no actual value. Phrases like 'provides automated assistance' and 'follows industry best practices' are vague filler that Claude doesn't need. | 1 / 3 |
Actionability | No concrete code, commands, examples, or specific instructions are provided. The entire skill describes what it does abstractly without showing how to actually generate user stories. | 1 / 3 |
Workflow Clarity | No workflow is defined. Claims to provide 'step-by-step guidance' but contains zero actual steps. No process, no validation, no sequence of actions. | 1 / 3 |
Progressive Disclosure | The content is organized into sections with clear headers, but there are no references to detailed materials, examples, or templates that would be expected for a user story generator skill. | 2 / 3 |
Total | 5 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
0c08951
- 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.