update-story

Update the current story's acceptance criteria checkboxes based on recent git history, then sync the updated body back to the linked GitHub issue. Use when the user says "update story", "mark AC done", "sync story", or "update the issue".

Quality

96%

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

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

An exemplary instruction skill: a tight five-step workflow of copy-paste-ready commands with explicit validation checkpoints and error-recovery fallbacks. Concise, fully actionable, and well-structured with no unnecessary explanations.

Dimension	Reasoning	Score
Conciseness	Lean body of executable commands and task-essential rules; it does not explain git, gh, or branch-convention concepts Claude already knows, and every line earns its place.	5 / 5
Actionability	Fully executable commands throughout (git rev-parse, grep -rl, git log/diff, gh issue view/edit --body-file) with concrete failure-fallback instructions and specific Write-tool guidance.	5 / 5
Workflow Clarity	Five clearly sequenced steps with explicit validation/failure checkpoints (ask on missing issue number, stop on gh failure, careful AC merge logic, manual-paste fallback) forming feedback loops for an external-write operation.	5 / 5
Progressive Disclosure	Self-contained skill with no bundle files needed, organized into five well-labeled step sections and no nested/deep references; appropriately compact for its scope.	5 / 5
	Total	20 / 20 Passed

Description

92%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, concise description that pairs concrete capabilities with explicit, natural trigger phrases. It clearly answers both 'what' and 'when' and carves out a distinct niche with low conflict risk.

Dimension	Reasoning	Score
Specificity	Names multiple concrete actions — "Update the current story's acceptance criteria checkboxes based on recent git history" and "sync the updated body back to the linked GitHub issue" — giving comprehensive coverage of its domain.	5 / 5
Completeness	Explicitly answers both what it does (update AC + sync to GitHub issue) and when to use it via an explicit "Use when..." clause with concrete trigger phrases.	5 / 5
Trigger Term Quality	Provides four natural user phrases ("update story", "mark AC done", "sync story", "update the issue") that a developer would plausibly say; good coverage but lacks synonym/file-extension variants beyond these niche terms.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (story AC sync tied to GitHub issues) with distinct, domain-specific triggers and minimal overlap risk with other skills.	5 / 5
	Total	19 / 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/update-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.