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.
Overall
score
19%
Does it follow best practices?
Validation for skill structure
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill user-story-generatorActivation
7%This description is severely underdeveloped, essentially serving as a placeholder rather than a functional skill description. It lacks any concrete actions, has redundant and limited trigger terms, and provides no guidance on when Claude should use this skill. The only slight positive is that 'user story' is a recognizable domain term.
Suggestions
Add specific capabilities: 'Generates user stories with acceptance criteria, story points, and proper formatting. Converts requirements into agile-ready stories with Given/When/Then scenarios.'
Add a 'Use when...' clause: 'Use when the user asks to write user stories, create product backlog items, convert requirements to agile format, or mentions acceptance criteria.'
Expand trigger terms to include natural variations: 'user stories, agile stories, product backlog, PBIs, acceptance criteria, story points, as a user I want, Gherkin format'
| 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 the 'when' guidance is just a duplicate trigger term. There is no explicit 'Use when...' clause explaining when Claude should select this skill. | 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 development contexts, which provides some distinctiveness. However, 'Enterprise Workflows' is vague and could overlap with many business-related skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill is essentially a placeholder with no substantive content. It describes what a user story generator skill might do but provides absolutely no actionable guidance, examples, templates, or workflows for actually generating user stories. The entire content could be replaced with a single sentence without losing any practical value.
Suggestions
Add a concrete user story template with format specification (e.g., 'As a [role], I want [feature], so that [benefit]') and acceptance criteria structure
Include 2-3 complete example user stories showing input requirements and expected output format
Define a clear workflow: 1) Gather requirements, 2) Identify user roles, 3) Draft story, 4) Add acceptance criteria, 5) Validate completeness
Remove all generic boilerplate ('provides automated assistance', 'follows best practices') and replace with specific, actionable instructions
| 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 meaningless filler that Claude doesn't need. | 1 / 3 |
Actionability | The skill contains zero concrete guidance, no code examples, no specific commands, and no actual instructions on how to generate user stories. It only describes what it claims to do without showing how. | 1 / 3 |
Workflow Clarity | There is no workflow defined at all. The skill mentions 'step-by-step guidance' but provides none. No sequence, no validation steps, no actual process for generating user stories. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of vague descriptions with no references to detailed materials, no examples file, no templates, and no structured navigation to actual implementation details. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 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.