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

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

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

Quality

Content

82%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 exceptionally concise and delegates cleanly to specific external files with an explicit substitution rule, yielding clear structure and workflow. Its main limitation is that the substantive instructions reside in external non-bundled files, so actionability and progressive disclosure rest on those references being valid.

DimensionReasoningScore

Conciseness

The body is a lean five-line delegation that assumes Claude's competence and adds no padding or redundant explanation, with every token earning its place.

5 / 5

Actionability

Provides concrete, executable guidance via exact file paths and a specific substitution directive, but the actual instructions live in an external non-bundled file, leaving a minor gap.

4 / 5

Workflow Clarity

Presents a clear two-step sequence (read and execute the playbook, then follow cog.md) with a conditional substitution rule; no validation checkpoints, but the task is delegation rather than a destructive or batch operation.

4 / 5

Progressive Disclosure

The body is an overview with clearly signaled one-level-deep references to detailed materials, though the referenced bundle files are not present to fully verify navigation.

4 / 5

Total

17

/

20

Passed

Description

61%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 and names relevant trackers, but it lacks an explicit 'when to use' trigger clause and lists only one concrete action. Adding a 'Use when...' clause with natural trigger phrases would lift completeness and trigger term quality.

Suggestions

Add an explicit 'Use when...' clause with trigger phrases (e.g., 'Use when creating user stories, adding backlog items, or checking for duplicate tickets in Linear, GitHub Issues, or Jira').

Expand the action list beyond a single verb to enumerate concrete actions (e.g., 'create user stories, check for duplicates, and link to existing issues').

Include natural synonyms and file/URL extensions where relevant to broaden trigger term coverage.

DimensionReasoningScore

Specificity

Names the domain ('user stories', 'duplicate checking') and one concrete action (create user stories with duplicate checking) but does not enumerate several specific actions, matching the anchor for 1-2 concrete actions without comprehensive coverage.

3 / 5

Completeness

Provides a clear 'what' (create user stories with duplicate checking across trackers) but has no explicit 'Use when...' trigger clause, which caps completeness at 3 per the rubric guidelines.

3 / 5

Trigger Term Quality

Includes natural terms users would say ('user stories', 'duplicate checking', 'Linear', 'GitHub Issues', 'Jira') with good coverage, though common synonyms like 'tickets' or 'backlog items' are absent.

4 / 5

Distinctiveness Conflict Risk

Occupies a distinct niche (user stories with duplicate checking across named trackers) with low conflict risk, though naming multiple trackers slightly broadens the scope.

4 / 5

Total

14

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

huytieu/COG-second-brain

Path

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

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.