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.
36
3%
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 extremely weak—it is essentially just the skill's name repeated with boilerplate category metadata. It provides no concrete actions, no meaningful trigger terms beyond the skill name itself, and no explicit guidance on when Claude should select this skill. It would be nearly indistinguishable from any other enterprise workflow skill.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Generates user stories with acceptance criteria, story points, and persona-based narratives in standard agile format.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks to create user stories, write acceptance criteria, build backlog items, or mentions agile stories, epics, or requirements.'
Remove the duplicate trigger term and expand with natural variations users would say, such as 'user stories', 'agile requirements', 'backlog', 'as a [role] I want [feature]', 'acceptance criteria'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain ('User Story Generator') but provides no concrete actions. It does not describe what the skill actually does—no mention of creating, formatting, accepting criteria, or any specific capabilities. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name itself, and the 'when' clause is just a redundant repetition of the skill name rather than meaningful trigger guidance. There is no explicit 'Use when...' clause. | 1 / 3 |
Trigger Term Quality | The only trigger term listed is 'user story generator' repeated twice. It misses natural variations users would say like 'user stories', 'acceptance criteria', 'agile stories', 'backlog items', 'requirements', or 'as a... I want... so that...'. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'user story generator' is somewhat specific to a niche (agile user stories), which provides some distinctiveness. However, the vague 'Enterprise Workflows' category and lack of detail could cause overlap with other enterprise or agile-related skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is a placeholder/template with no substantive content. It contains only meta-descriptions of what it claims to do without any actual user story templates, formats, examples, acceptance criteria patterns, or actionable instructions. It fails on every dimension because it provides zero value beyond restating its own name and category.
Suggestions
Add a concrete user story template with format specification (e.g., 'As a [role], I want [feature], so that [benefit]') and include 2-3 complete examples with acceptance criteria.
Define a clear workflow: e.g., 1) Gather requirements from user, 2) Identify personas/roles, 3) Generate stories in standard format, 4) Validate stories against INVEST criteria, 5) Output in requested format.
Include actionable output formats—show exactly what a generated user story looks like, including fields like priority, story points estimation guidance, and acceptance criteria checklist.
Remove all generic filler text ('Provides step-by-step guidance', 'Follows industry best practices') and replace with the actual guidance and practices being referenced.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is almost entirely filler and meta-description. It explains what the skill does in abstract terms without providing any actual instructions, templates, or actionable content. Phrases like 'Provides step-by-step guidance' and 'Follows industry best practices' are empty padding. | 1 / 3 |
Actionability | There is zero concrete guidance—no user story template, no format specification, no examples of generated user stories, no commands, no code. The skill describes rather than instructs, offering only vague promises of capability. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. There are no steps, no sequence, no validation checkpoints. The skill merely states it 'provides step-by-step guidance' without actually containing any steps. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of generic descriptions with no references to supporting files, no structured sections with real content, and no navigation to deeper materials. There are no bundle files to support it either. | 1 / 3 |
Total | 4 / 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
3a2d27d
- 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.