CtrlK
BlogDocsLog inGet started
Tessl Logo

create-user-stories

Break a PRD or feature description into implementable user stories with acceptance criteria. Use when handing off to engineering or breaking down work for sprint planning.

76

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The skill body is a well-structured, actionable prompt template that assumes Claude's competence and avoids concept padding. As a simple, self-contained instruction skill it scores well across all content dimensions.

DimensionReasoningScore

Conciseness

The body is a lean prompt template plus a short tips list with no padding of concepts Claude already knows (e.g., no explanation of what a user story or PRD is), matching the anchor-3 lean profile; the brief framing paragraph sets quality bars rather than restating generic knowledge, so it does not drop to 2.

3 / 3

Actionability

Quotes provide a complete, copy-paste-ready prompt template with a fully specified per-story structure (Title, Story, Acceptance Criteria with Given/When/Then, Priority, Notes) and concrete principles, matching the anchor-3 executable/specific bar; it is not 2 because the guidance is concrete and directly usable rather than pseudocode or vague direction.

3 / 3

Workflow Clarity

This is a single-purpose skill (run the prompt to produce stories) with an unambiguous action and no destructive or batch operations requiring validation checkpoints, so per the simple-skills note it qualifies for 3; it is not 2 because there is no multi-step sequence with missing checkpoints to penalize.

3 / 3

Progressive Disclosure

The content is self-contained with clearly signaled sections (Prompt Template, Tips) and no bundle files or nested references, matching the anchor-3 well-organized simple-skill profile; it is not 2 because nothing that should be split out is inlined and there are no 2+ level reference chains.

3 / 3

Total

12

/

12

Passed

Description

90%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description clearly states a specific capability and pairs it with an explicit, natural-language trigger clause, giving strong completeness and distinctiveness. Its only weakness is specificity: it describes one composite action rather than enumerating several concrete operations.

DimensionReasoningScore

Specificity

Quotes "Break a PRD or feature description into implementable user stories with acceptance criteria" name the domain and a composite action with deliverables, but it is a single composite action rather than a list of multiple distinct concrete actions like the anchor-3 example (extract/fill/merge), so it sits at 2 not 3.

2 / 3

Completeness

Quotes answer both what ("Break a PRD ... into implementable user stories with acceptance criteria") and when via an explicit "Use when ..." clause, matching the anchor-3 example; it is not 2 because the trigger is explicit rather than merely implied.

3 / 3

Trigger Term Quality

Quotes "Use when handing off to engineering or breaking down work for sprint planning" provide natural phrases a user would actually say (hand off to eng, break down work, sprint planning), matching the anchor-3 good coverage; it is above 2 because common natural variations are present rather than only one generic term.

3 / 3

Distinctiveness Conflict Risk

The PRD-to-user-stories niche with sprint-planning triggers is clearly distinguishable and unlikely to fire for unrelated skills, matching anchor-3; it is not 2 because the triggers are specific enough to avoid overlap with general planning or doc skills.

3 / 3

Total

11

/

12

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
amplitude/builder-skills
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.