implement-story

Implements a GitHub user story from planning through PR creation, with research, codebase analysis, and structured commits.

Quality

72%

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

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/implement-story/SKILL.md

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 well-crafted, actionable implementation workflow with strong sequencing and explicit validation/feedback loops. The main gap is progressive disclosure: content is largely monolithic within SKILL.md and referenced project files are cited by path rather than as signaled, navigable references.

Suggestions

Consider moving the detailed PR-template rules and regeneration-task table into a referenced reference file, keeping SKILL.md as a concise overview with one-level-deep links.

Make external references explicit and navigable (e.g. 'See [pr-creation.md](.claude/rules/pr-creation.md)') rather than bare paths.

Trim the prose principles in section 3.2 to the essential rules to lift conciseness from 4 to 5.

Dimension	Reasoning	Score
Conciseness	The body is efficient and assumes Claude's competence — concrete commands and tables rather than concept explanations — with only minor instances of over-explanation (e.g. the principles bullets in 3.2) that could be trimmed.	4 / 5
Actionability	Guidance is fully executable: concrete shell commands (`gh search issues`, `git checkout -b`, `gh pr checks --watch`), a regeneration task table with exact `task` invocations, and a concrete plan template covering the common cases.	5 / 5
Workflow Clarity	Four phases are clearly sequenced with explicit validation checkpoints — plan approval gates, an AC coverage checklist (4.2), and a CI feedback loop (4.3: read logs → fix → push → re-check) — plus a checklist for the destructive/batch PR operation.	5 / 5
Progressive Disclosure	Well-structured into phase sections with a clear overview, but most guidance is inlined in SKILL.md and external references (`.github/pull_request_template.md`, `.claude/rules/pr-creation.md`, RFC repo) are referenced by path rather than clearly signaled one-level-deep links, so it sits just below the ideal 5.	4 / 5
	Total	18 / 20 Passed

Description

56%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 specific and clearly distinct, but it omits any 'Use when...' trigger guidance, which caps completeness at 3 and weakens trigger-term quality. Adding an explicit usage clause with natural trigger phrases would raise both dimensions.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when the user asks to implement a GitHub issue/user story or take a feature from plan to PR.'

Include natural trigger phrases users actually say, such as 'implement this issue', 'build this user story', or 'turn this ticket into a PR'.

Tighten the action list toward the most concrete outcomes (research, plan, code, tests, PR) to push specificity from 4 toward 5.

Dimension	Reasoning	Score
Specificity	Names the domain (GitHub user story) and several concrete actions — 'planning', 'codebase analysis', 'structured commits', 'PR creation' — which is multiple specific actions with only minor gaps in coverage.	4 / 5
Completeness	It clearly states the 'what' (implements a user story end-to-end) but provides no 'when' / 'Use when...' trigger clause, so per the judging guidelines completeness is capped at 3.	3 / 5
Trigger Term Quality	Includes relevant terms like 'GitHub user story', 'PR creation', and 'codebase analysis', but lacks the natural phrases a user would actually say (e.g. 'implement this issue', 'user story', 'feature ticket') and common synonyms.	3 / 5
Distinctiveness Conflict Risk	The 'GitHub user story from planning through PR creation' niche is fairly distinct from general coding skills, with only minor overlap risk against generic git/PR helpers.	4 / 5
	Total	14 / 20 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: stacklok/toolhive
Path: .claude/skills/implement-story/SKILL.md
Commit: ccabad6

Reviewed: about 13 hours 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.