CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

openspec-verify-change

Verify implementation matches OpenSpec change artifacts. Use when the user wants to validate that implementation is complete, correct, and coherent before archiving. Also use when the user says "openspec verify" or "opsx verify".

Quality

83%

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

SKILL.md
Quality
Evals
Security

Quality

Content

70%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 highly actionable, well-sequenced verification workflow with strong validation checkpoints, weakened by redundancy across steps and a monolithic single-file structure that inlines reference-grade detail (delta-matching rules, report templates) instead of splitting it out.

Suggestions

State the removal-only-change rule (REMOVED/RENAMED with no ADDED/MODIFIED) once and reference it from the other steps, instead of restating it in steps 4, 6, and 8.

Move the REMOVED/RENAMED baseline-matching rules and the report format template into a references/ file and link to them, turning SKILL.md into a leaner overview.

Make the codebase-search steps concrete by suggesting a specific method, e.g. Grep for the requirement name or scenario keywords and specific file-glob patterns, rather than 'search codebase for keywords related to the requirement'.

DimensionReasoningScore

Conciseness

The body contains no concept-explanation padding and is dense with operational detail, but it repeats key rules across steps (the removal-only-change rule appears in steps 4, 6, and 8; the store-flag shorthand is explained twice in the opening paragraph) and includes long parentheticals like the normalized-name matching rule that could be tightened.

3 / 5

Actionability

Provides copy-paste-ready commands (openspec status/instructions/list with --json flags, git baseline-recovery commands), exact JSON field names to parse, and exact issue/recommendation templates. Minor gap: 'Search codebase for keywords related to the requirement' offers no concrete search method.

4 / 5

Workflow Clarity

Eight clearly numbered steps with explicit validation checkpoints (project root check, '"root": null' branch handling, evidence-availability gates before each check, unavailableTrackingFiles handling) and error-recovery paths such as git baseline recovery with empty-output interpretation.

5 / 5

Progressive Disclosure

A 210-line monolithic file with no references at all; content that would fit separate files (the report format template, the dense REMOVED/RENAMED baseline-matching rules) is inlined, though internal step headers keep it navigable.

3 / 5

Total

15

/

20

Passed

Description

87%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 description: third-person, concrete, and explicit about both capability and trigger conditions, with exact command phrases as triggers. Only minor gaps in action enumeration and synonym coverage keep specificity and trigger term quality at 4.

DimensionReasoningScore

Specificity

Names the domain (OpenSpec change artifacts) and several concrete actions — verify implementation matches, validate completeness, correctness, and coherence before archiving — though the three verification dimensions modify a single 'validate' verb rather than being distinct actions like anchor 5 requires.

4 / 5

Completeness

Clearly answers both 'what' (verify implementation matches OpenSpec change artifacts) and 'when' with concrete trigger phrases ('Use when the user wants to validate that implementation is complete, correct, and coherent before archiving. Also use when the user says "openspec verify" or "opsx verify"'), matching the anchor-5 pattern.

5 / 5

Trigger Term Quality

Includes excellent exact-command triggers users would naturally say ('openspec verify', 'opsx verify') plus 'validate' and 'before archiving', but misses common variations such as 'check implementation' or 'verify change'.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (OpenSpec change verification before archiving) with distinct CLI command triggers that are unlikely to fire for unrelated skills.

5 / 5

Total

18

/

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

Fission-AI/OpenSpec

Path

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.