CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

create-user-story

Create user stories with duplicate checking across any project tracker (Linear, GitHub Issues, Jira)

Quality

78%

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 ./.claude/skills/create-user-story/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

77%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 body delivers a well-sequenced, highly actionable workflow with strong user-confirmation checkpoints and thorough fallback/error handling. Its weaknesses are the monolithic single-file structure — the story template and tracker-specific prompts should be split into reference files — and minor vagueness in the Jira creation path.

DimensionReasoningScore

Conciseness

The body is lean and directive throughout — tables, terse phase descriptions, and no explanation of concepts Claude already knows; a 4 rather than 5 because the per-tracker duplicate-checker agent prompts and the 35-line story template repeat structural boilerplate that could be tightened.

4 / 5

Actionability

Provides concrete, executable guidance: exact gh commands with flags ("gh search issues ... --json number,title,state,url,body --limit 20"), exact MCP tool names (mcp__claude_ai_Linear_2__save_issue), and vault file paths; not a 5 because Jira creation is vague ("Use WebFetch to POST to Jira REST API") and several placeholders ([CUSTOMIZE: your-org/your-repo], [story title]) require the agent to fill in structure.

4 / 5

Workflow Clarity

Six clearly sequenced phases with explicit validation checkpoints ("Wait for user confirmation before proceeding", "Present the formatted story to the user for review before creating it"), plus a fallback behavior table and error handling section with retry/recovery guidance — this matches the anchor for clear sequence with explicit validation and feedback loops.

5 / 5

Progressive Disclosure

The skill is a single 230-line SKILL.md with no bundle files; sections are well-organized, but the full story-format template and the per-tracker duplicate-check prompts are inlined content that clearly belongs in separate reference files (matching the anchor "content that should be separate is inline"), not a 2 because the structure is clear and navigable rather than minimal.

3 / 5

Total

16

/

20

Passed

Description

70%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 is concise, concrete, and clearly differentiated, with strong natural trigger terms from the tracker names. Its main weakness is the complete absence of a "when to use" clause, leaving the trigger guidance implicit.

Suggestions

Append an explicit trigger clause such as "Use when the user wants to create a story, feature request, or issue, or says 'new story', 'add issue', or 'create ticket'" to raise completeness and add natural trigger variations.

Mention the markdown/vault fallback for when no tracker is active, so the description covers the skill's full behavior rather than only the tracker-backed path.

Consider naming the story format output (e.g., "with acceptance criteria in Given/When/Then format") to add another concrete, distinguishing capability.

DimensionReasoningScore

Specificity

Names two concrete actions ("create user stories", "duplicate checking") plus the enumerated trackers (Linear, GitHub Issues, Jira), which is slightly more specific than anchor 3's two-action example; not a 5 because only two actions are stated rather than multiple comprehensive ones.

4 / 5

Completeness

The "what" is clear (create user stories with duplicate checking across trackers) but there is no "Use when..." clause or equivalent explicit trigger guidance, which the rubric says caps completeness at 3; not a 2 because the "what" is concrete and specific, not vague.

3 / 5

Trigger Term Quality

"user stories", "create", and the tracker names are natural terms users would say, but common variations like "new story", "add issue", "create ticket", or "feature request" (which appear only in the body) are missing from the description.

4 / 5

Distinctiveness Conflict Risk

The combination of user-story creation, duplicate checking, and the three named trackers carves out a clear niche with distinct triggers and minimal overlap with other skills.

5 / 5

Total

16

/

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.

Validation — 15 / 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

huytieu/COG-second-brain

Path

.claude/skills/create-user-story/SKILL.md

Revision

144c7a3

Reviewed

Table of Contents

DiscoveryImplementationValidation

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.

Claim skill