CtrlK
BlogDocsLog inGet started
Tessl Logo

openspec-verify-change

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

73

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

92%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-structured, executable verification workflow with concrete commands, explicit feedback loops, and graceful degradation. Only minor conciseness trimming would improve it.

DimensionReasoningScore

Conciseness

Mostly efficient procedural instructions with no padding of concepts Claude already knows, but some redundancy in repeated "Recommendation:" phrasing across dimensions; not 5 due to minor trimming opportunities, not 3 because there is no over-explanation.

4 / 5

Actionability

Provides concrete executable commands (openspec list/status/instructions with --json), precise output formats (checkbox parsing, table scorecard, file.ts:123 references), and specific examples covering common cases.

5 / 5

Workflow Clarity

Clear 8-step sequence with explicit validation checkpoints, a false-positive feedback loop (SUGGESTION over WARNING over CRITICAL), and graceful-degradation guidance for missing artifacts.

5 / 5

Progressive Disclosure

Single self-contained skill with no bundle files and well-organized section headers; under the simple-skills exception this scores 5 with clear organization and no nested references.

5 / 5

Total

19

/

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, third-person description that clearly states both capability and trigger conditions scoped to a distinct niche. Minor keyword/synonym gaps keep trigger_term_quality and specificity at 4 rather than 5.

DimensionReasoningScore

Specificity

Names the domain and concrete verification dimensions ("complete, correct, and coherent") with minor gaps in coverage; not 3 because it lists several specific actions rather than 1-2, not 5 because it does not enumerate the artifact types in the description itself.

4 / 5

Completeness

Explicitly answers what ("Verify implementation matches change artifacts") and when ("Use when the user wants to validate that implementation is complete, correct, and coherent before archiving") with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural trigger phrases like "validate that implementation is complete" and "before archiving"; not 5 because it lacks synonyms and file/artifact-type variations (e.g. specs, tasks).

4 / 5

Distinctiveness Conflict Risk

Scoped to openspec change artifacts and archiving, giving it a clear niche with distinct triggers and minimal conflict with other 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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
PBH-BTN/PeerBanHelper
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.