CtrlK
BlogDocsLog inGet started
Tessl Logo

user-story

Generate user stories with acceptance criteria and sprint planning. Usage: /user-story <generate|sprint> [options]

56

Quality

64%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.gemini/skills/user-story/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

70%Weight 40%Scale 1-5

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

The content is concise and well-structured with clear usage examples, but actionability and workflow clarity are limited by delegating the real logic to an external script and by the absence of validation checkpoints for sprint capacity planning.

Suggestions

Add an explicit validation checkpoint for sprint planning, e.g. 'Confirm selected stories sum to <= capacity and are ranked by priority before presenting the plan.'

Surface the script's concrete invocation (e.g. `python user_story_generator.py sprint 21`) and its expected output rather than only noting positional args.

DimensionReasoningScore

Conciseness

The body is lean and efficient, assuming Claude's competence; every section earns its place with no padding or explanation of concepts Claude already knows.

5 / 5

Actionability

It gives concrete invocations and input examples, but the actual generation logic is delegated to an external script whose usage is only described at a high level ('positional args'), leaving key execution details unspecified.

3 / 5

Workflow Clarity

The two modes (generate, sprint) are sequenced with examples, but sprint planning is a batch operation with no validation/verification checkpoint (e.g. confirming stories fit capacity, priority ranking rules), capping workflow clarity at 3.

3 / 5

Progressive Disclosure

Structure is good with well-organized sections and a one-level-deep reference to a script and the source SKILL.md; minor gaps because the referenced bundle paths are not local files and there is no navigation to detail documents.

4 / 5

Total

15

/

20

Passed

Description

58%Weight 40%Scale 1-5

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 what the skill does with concrete actions, but omits any 'Use when...' trigger guidance, which caps its completeness. Trigger-term coverage is decent but lacks natural synonyms users might say.

Suggestions

Add a 'Use when...' clause, e.g. 'Use when the user asks to write user stories, define acceptance criteria, or plan a sprint by story-point capacity.'

Broaden trigger terms with natural synonyms like 'agile', 'backlog', 'story points', and 'acceptance criteria' that users would actually say.

DimensionReasoningScore

Specificity

Names the domain and lists several concrete actions ('acceptance criteria', 'sprint planning', 'story points') with only minor gaps in coverage.

4 / 5

Completeness

The 'what' is clear ('Generate user stories with acceptance criteria and sprint planning') but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

Includes relevant terms like 'user stories', 'acceptance criteria', and 'sprint planning', but misses common variations users would naturally say such as 'agile', 'backlog', or 'story points' as a trigger phrase.

3 / 5

Distinctiveness Conflict Risk

The niche is fairly distinct (user-story generation and sprint planning), with only minor overlap risk against generic project-management skills.

4 / 5

Total

14

/

20

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
alirezarezvani/claude-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.