CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

The canonical home for this skill is openspec-verify-change in dwmkerr/git-workforest

SKILL.md
Quality
Evals
Security

Quality

Content

73%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 strongly structured verification workflow with copy-ready CLI commands, explicit conditionals, graceful degradation for missing artifacts, and a severity-gated archive decision. The main cost is token weight: repeated issue templates and a few explanations of things Claude already knows could be consolidated to tighten the body.

Suggestions

Define the issue format once (e.g., "Every issue: severity, message, and a Recommendation with file/line references where applicable") and list the six checks as one-line entries, removing the repeated issue-plus-Recommendation pattern in steps 5-7.

Delete explanations of knowledge Claude already has, such as the checkbox syntax ("`- [ ]` (incomplete) vs `- [x]` (complete)") and "Count complete vs total tasks".

Extract the full report template and issue message examples into a references/ file (e.g., REPORT_FORMAT.md) and keep a one-line pointer in SKILL.md, slimming the main body below its current ~157 lines.

DimensionReasoningScore

Conciseness

The body is mostly efficient prescriptive guidance, but includes unnecessary explanation Claude already knows ("Parse checkboxes: `- [ ]` (incomplete) vs `- [x]` (complete)", "Count complete vs total tasks") and repeats the issue-plus-"Recommendation:" template six times across steps 5-7 instead of defining the issue format once. This fits anchor 3 (mostly efficient but could be tightened) rather than 4, where over-explanation would be only minor.

3 / 5

Actionability

Concrete, executable commands are given throughout ("openspec list --json", "openspec status --change \"<name>\" --json", "openspec instructions apply --change \"<name>\" --json") plus an explicit report template and file-reference format. It falls short of anchor 5 because the codebase-verification steps remain high-level ("Search codebase for keywords related to the requirement") with no worked example of a filled-in report.

4 / 5

Workflow Clarity

Steps 1-8 form a clear numbered sequence with explicit decision points ("If no change name provided, prompt for selection", "If no design.md: Skip... and note"), a severity-gated final assessment that explicitly controls archiving ("Fix before archiving" / "Ready for archive"), and error-recovery rules ("When uncertain, prefer SUGGESTION over WARNING", WARNING over CRITICAL). This matches anchor 5: explicit validation steps, feedback rules, and a checklist-like three-dimension report; the operation is read-only verification, so no destructive-operation cap applies.

5 / 5

Progressive Disclosure

The bundle contains no references/ and the body is well-organized into Steps, Verification Heuristics, Graceful Degradation, and Output Format sections with all content operational rather than misfiled reference material. At ~157 lines it exceeds the under-50-line exception for a reference-free 5, and the report template and issue-message formats could arguably be extracted to a reference file, so anchor 4 (good structure, minor organization gaps) is the best fit.

4 / 5

Total

16

/

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 well-formed description that clearly and explicitly states both what the skill does and when to use it, with a distinctive spec-workflow trigger (pre-archive verification). Its main weakness is that it summarizes one broad action rather than naming the specific verification checks it performs, which slightly limits specificity and trigger coverage.

Suggestions

Enumerate the concrete verification actions in the description, e.g., "Checks task completion, maps requirements and scenarios to implementation, and verifies design adherence" — this would raise specificity from one broad action to several distinct ones.

Add one or two natural trigger synonyms users would actually say, such as "check if a change is ready to archive" or "verify the change", to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

"Verify implementation matches change artifacts" names the domain and one concrete action, with "complete, correct, and coherent" naming qualities of that single action rather than several distinct actions. It matches anchor 3 (domain plus 1-2 concrete actions) — not 4, since it lacks an enumeration of specific verification actions (task checking, requirement mapping, scenario coverage), and not 2, since it goes beyond generically naming the domain.

3 / 5

Completeness

It explicitly answers both questions: "Verify implementation matches change artifacts" (what) and "Use when the user wants to validate that implementation is complete, correct, and coherent before archiving" (when, with concrete trigger conditions). This mirrors the anchor 5 example structure; anchor 4's caveat ("'when' could be more explicit") does not apply since the Use-when clause is explicit and specific.

5 / 5

Trigger Term Quality

Natural trigger phrases are present — "validate that implementation is complete", "verify implementation", "before archiving" — including two synonym verbs (verify/validate) and the workflow-specific term "archiving". A few natural terms users would say are missing (e.g., "check the change", "ready to archive"), so it fits anchor 4 rather than anchor 5's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

"change artifacts" and "before archiving" carve out a clear openspec-specific niche, but the leading phrase "Verify implementation matches" could plausibly fire on general implementation-verification or code-review requests. This is anchor 4 (mostly distinct, minor overlap with closely related skills) rather than 5, whose example has triggers with minimal conflict risk.

4 / 5

Total

16

/

20

Passed

Validation

100%

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

TencentBlueKing/bk-bcs

Path

bcs-runtime/bcs-k8s/bcs-component/bcs-drplan-controller/.claude/skills/openspec-verify-change/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.