CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

init-story

Collect context from the developer and create a story markdown file in .claude/stories/ for the current branch. Use when the user says "init story", "create story", "start story", or "new story".

Quality

85%

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

SKILL.md
Quality
Evals
Security

Quality

Content

88%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.

A highly actionable, well-sequenced instruction skill: executable git/gh commands, scripted asks, a complete output template, explicit failure paths, and correction loops. The only room for improvement is trimming a few justificatory asides and, if the skill grows, moving the project-specific testing philosophy out of Step 4 into a reference file.

DimensionReasoningScore

Conciseness

Largely lean and imperative, assuming Claude's competence ("don't ask the developer to re-type what's already there", "ask once, then go figure out the rest yourself"), with only minor over-explanation such as Step 7's justification for skipping confirmation. Fits the 4 anchor (efficient, minor trimming possible) rather than 5's every-token-earns-its-place.

4 / 5

Actionability

Provides executable commands (git rev-parse, git checkout -b, gh issue view with --json and -q flags), fully scripted developer messages for each ask, a complete story-file template, and a concrete filename example (6032-story-tracking-automation.md). This is copy-paste-ready guidance covering the common cases, matching the top anchor.

5 / 5

Workflow Clarity

Eight clearly sequenced steps with explicit error handling (gh failure fallback to manual input), conditional branches (zero findings skips Step 5), strict batching rules to prevent repeated interruptions, and a final report-and-correct loop in Step 8. The sequence and feedback loops match the top anchor; the only writes are a single tracked file and branch creation, so no destructive-operation cap applies.

5 / 5

Progressive Disclosure

No bundle files exist, and the ~140-line body is well-organized into eight headed steps with nothing that clearly belongs in a separate file (the inline testing-framework list in Step 4 is short and load-bearing). Good structure with minor organization gaps fits anchor 4; the under-50-lines exception for a 5 does not apply.

4 / 5

Total

18

/

20

Passed

Description

78%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.

A strong description with an explicit "Use when..." clause, natural trigger phrases, and a specific deliverable location. Its main weakness is that the "what" undersells the skill's actual work — pulling GitHub issue context and investigating the codebase — which both limits specificity and slightly blurs distinctiveness against generic story-creation requests.

Suggestions

Add the GitHub and investigation work to the "what" clause, e.g. "Pull the GitHub issue, ask the developer one round of optional input, investigate the codebase with agents, and write a story markdown file in .claude/stories/ for the current branch" — this would raise specificity from 1-2 actions to several.

Add one or two more trigger variants (e.g. "set up story", "begin story") to widen natural keyword coverage.

DimensionReasoningScore

Specificity

Names two concrete actions ("Collect context from the developer", "create a story markdown file in .claude/stories/ for the current branch") but is not comprehensive — it omits the GitHub issue pull and codebase investigation that are the skill's core work. This matches the 3 anchor (1-2 concrete actions, not comprehensive) rather than 4's "several specific actions".

3 / 5

Completeness

Explicitly answers both what ("Collect context from the developer and create a story markdown file in .claude/stories/ for the current branch") and when ("Use when the user says..." with four concrete trigger phrases), matching the top anchor exactly.

5 / 5

Trigger Term Quality

Includes four natural trigger phrases users would say ("init story", "create story", "start story", "new story"), giving good coverage, though common variations like "set up story" or "make a story" are missing. Not 5 since coverage of synonyms is not exhaustive.

4 / 5

Distinctiveness Conflict Risk

The niche ("story markdown file in .claude/stories/ for the current branch") and quoted trigger phrases are distinct, but generic phrases like "new story" could overlap with general story- or user-story-writing skills, leaving minor overlap risk rather than minimal.

4 / 5

Total

16

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

frontmatter_unknown_keys

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

Warning

Total

14

/

16

Passed

Repository

HHS/OPRE-OPS

Path

.claude/skills/init-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.