openspec-verify-change

Verify implementation matches change artifacts. Use when the user wants to validate that implementation is complete, correct, and coherent before archiving.

Quality

76%

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/openspec-verify-change/SKILL.md

Quality

Content

77%

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-sequenced, actionable verification workflow with executable commands and clear degradation handling. Its main weakness is progressive disclosure: everything sits in one inline file with no references to split detail into.

Suggestions

Move the full report template and detailed per-dimension heuristics into a reference file (e.g. references/verify-report.md) and link to it from a concise overview in SKILL.md to improve progressive disclosure.

Tighten obvious-explanation padding such as the checkbox legend and repeated 'Add ... issue' phrasing to improve token efficiency.

Consider adding a short validation feedback loop (run verify -> review CRITICAL issues -> re-run) to make the workflow's error-recovery step explicit rather than implied.

Dimension	Reasoning	Score
Conciseness	The body assumes Claude's competence and avoids explaining basic concepts, but minor padding (e.g. spelling out '- [ ] (incomplete) vs - [x] (complete)') and some restated guidance could be tightened to earn the top anchor.	2 / 3
Actionability	It provides concrete, copy-paste-ready commands ('openspec list --json', 'openspec status --change ... --json', 'openspec instructions apply ...') plus a fully specified report template, matching the executable-guidance anchor.	3 / 3
Workflow Clarity	The eight-step sequence is explicit and ordered, with a severity-tiered issue checklist, graceful-degradation branches, and false-positive guidance that function as validation checkpoints for a read-only verification task.	3 / 3
Progressive Disclosure	No bundle files exist and the ~170-line body is a single monolith with no one-level-deep references; it is well-sectioned but content that could live in separate files (report template, heuristics) is inline, so it does not reach the top anchor.	2 / 3
	Total	10 / 12 Passed

Description

75%

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 cleanly states both capability and an explicit use-when trigger, with a distinct openspec-scoped niche. It is slightly limited on action specificity and trigger-term breadth, which keep it from a perfect profile.

Dimension	Reasoning	Score
Specificity	It names the domain and a primary action ('Verify implementation matches change artifacts') plus the three verification axes ('complete, correct, and coherent'), but it does not list multiple distinct concrete actions, so it stops short of the top anchor.	2 / 3
Completeness	It answers both 'what' ('Verify implementation matches change artifacts') and 'when' with an explicit 'Use when...' trigger clause, satisfying the top anchor.	3 / 3
Trigger Term Quality	Natural terms like 'validate that implementation is complete' and 'before archiving' appear, but coverage of common variations a user might say (e.g. 'check tasks are done', 'review spec coverage') is partial.	2 / 3
Distinctiveness Conflict Risk	The niche of validating openspec change artifacts against specs/tasks/design before archiving is specific and unlikely to trigger for unrelated skills.	3 / 3
	Total	10 / 12 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: PBH-BTN/PeerBanHelper
Path: .claude/skills/openspec-verify-change/SKILL.md
Commit: be872c1

Reviewed: 3 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.