create-user-story

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

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/create-user-story/SKILL.md

Quality

Content

77%

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

The content is highly actionable with a clear, well-gated multi-phase workflow and concrete commands for each tracker. It loses points on conciseness and progressive disclosure due to repeated per-tracker blocks that could be templated or moved into reference files.

Suggestions

Extract the per-tracker duplicate-check and create instructions into reference files (e.g. references/linear.md, references/github.md) and link from the main body to reduce repetition.

Template the shared Linear/GitHub/Jira instruction structure to eliminate duplicated scaffolding across phases.

Keep the validation gates and fallback table — they are the strongest part of the workflow clarity.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and avoids explaining concepts Claude already knows, but tracker-specific instructions for Linear/GitHub/Jira are repeated across both duplicate-check and create phases and could be templated to tighten token use.	2 / 3
Actionability	Provides copy-paste-ready commands (gh search issues, gh issue create), concrete MCP tool names, JQL queries, and explicit file paths, with clearly flagged CUSTOMIZE placeholders.	3 / 3
Workflow Clarity	A clear six-phase sequence with explicit validation checkpoints — user confirmation before proceeding, story review before creation, and a fallback/error-handling table — provides the feedback loops the rubric rewards.	3 / 3
Progressive Disclosure	The skill is well-sectioned but at ~230 lines keeps tracker-specific duplicate-check and creation blocks inline that could be split into per-tracker reference files; no bundle files are present to offload this content.	2 / 3
	Total	10 / 12 Passed

Description

67%

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 specific and distinctive, clearly stating what the skill does and naming concrete trackers, but it omits an explicit "when to use" trigger clause and lacks common trigger-term variations. Adding a "Use when..." clause with synonyms like story, issue, and ticket would raise completeness and trigger quality.

Suggestions

Append an explicit trigger clause, e.g. "Use when the user asks to create a user story, story, issue, ticket, or feature request."

Add common trigger-term synonyms (story, issue, ticket, feature request) to improve natural keyword coverage.

Keep the tracker enumeration as-is — it contributes positively to specificity and distinctiveness.

Dimension	Reasoning	Score
Specificity	Names multiple concrete actions — "Create user stories", "duplicate checking" — and enumerates three specific trackers (Linear, GitHub Issues, Jira), matching the multi-action anchor.	3 / 3
Completeness	The "what" is clearly answered, but there is no explicit "Use when..." trigger clause in the description; per the guideline a missing trigger clause caps completeness at 2.	2 / 3
Trigger Term Quality	"create user stories" and the tracker names are natural phrasings, but common variations like "story", "issue", "ticket", and "feature request" are missing, so coverage is incomplete.	2 / 3
Distinctiveness Conflict Risk	The combination of user-story creation plus duplicate checking across named trackers is a clear niche with distinct triggers unlikely to conflict with other skills.	3 / 3
	Total	10 / 12 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
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
Commit: dfbf9e9

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

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.