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

Securityby

Low

Low-risk findings worth noting

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.

The body is a well-structured, highly actionable multi-step workflow with strong validation checkpoints and feedback loops. It is slightly above the simple-skill threshold, which keeps progressive disclosure and conciseness at a 4 rather than a 5.

Suggestions

Move the Agent 3 testing-framework list (Vest, Vitest+RTL, MSW, Cypress) into a references/ file referenced from Step 4 to improve progressive disclosure and tighten the body.

Trim a few rationale clauses (e.g. 'don't ask the developer to re-type what's already there') to push conciseness toward a 5.

Dimension	Reasoning	Score
Conciseness	The body is step-based and lean with executable commands and no concept over-explanation, but a few rationale lines (e.g. 'don't ask the developer to re-type what's already there') and the Agent 3 framework list could be trimmed, keeping it just below a 5.	4 / 5
Actionability	It provides copy-paste-ready commands ('git rev-parse --abbrev-ref HEAD', 'gh issue view <NUMBER> --json title,body,labels -q ...', 'git checkout -b <BRANCH-NAME>'), exact question wording, and a concrete story-file template that cover the common cases.	5 / 5
Workflow Clarity	Seven steps are clearly sequenced with explicit validation checkpoints (gh-failure fallback, a parallel-agent validation step with a 'significant findings' checklist, uncommitted-change warning, developer confirmation before write), satisfying the destructive/batch validation requirement.	5 / 5
Progressive Disclosure	No bundle files exist; the single self-contained file is well-organized into numbered step headers, but at ~143 lines with inlinable detail (Agent 3's framework list, the story template) it sits at 'good structure, minor gaps' rather than the auto-5 reserved for sub-50-line simple skills.	4 / 5
	Total	18 / 20 Passed

Description

82%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 strong: it concretely states what the skill does and provides explicit, natural trigger phrases for when to use it. Its only weak spot is specificity, where it lists just two actions rather than a comprehensive set.

Suggestions

Add one or two more concrete actions (e.g. 'validate the plan against the codebase', 'format acceptance criteria as checkboxes') to lift specificity toward a 4 or 5.

Broaden trigger-term coverage with a synonym or the file extension (e.g. 'set up story', '.md story file') to reach full trigger-term comprehensiveness.

Dimension	Reasoning	Score
Specificity	Names the domain and exactly two concrete actions ('Collect context from the developer' and 'create a story markdown file in .claude/stories/ for the current branch'), matching the 1-2 concrete-actions anchor rather than the 'several specific actions' needed for a 4.	3 / 5
Completeness	Clearly states what it does (collect context and create a story file) and explicitly gives when-to-use trigger phrases, matching the anchor for answering both what and when with concrete triggers.	5 / 5
Trigger Term Quality	Four natural trigger phrases ('init story', 'create story', 'start story', 'new story') give good coverage, but they are all verb+story variations with no synonyms or file-extension terms that would push it to a 5.	4 / 5
Distinctiveness Conflict Risk	It targets a clear niche (a branch story file in .claude/stories/) with distinctive triggers ('init story' etc.), giving minimal overlap risk with other skills.	5 / 5
	Total	17 / 20 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

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

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.