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.

72

Quality

87%

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

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-sequenced, actionable verification workflow with concrete commands and a clear reporting structure. Its main weakness is mild redundancy between the procedural steps and the closing heuristics/degradation sections.

Suggestions

Collapse the 'Verification Heuristics' and 'Graceful Degradation' notes into the relevant steps (or a single concise aside) to remove redundancy and improve conciseness.

Replace vague 'search codebase for keywords related to the requirement' with a concrete search method (e.g., a ripgrep invocation or the field names to grep for) to strengthen actionability.

Add an explicit validation checkpoint in step 8 (e.g., 're-run openspec status to confirm no incomplete tasks remain before final assessment') to make the closing feedback loop explicit.

DimensionReasoningScore

Conciseness

The body is mostly efficient and assumes Claude's competence, but the 'Verification Heuristics' and 'Graceful Degradation' sections restate guidance already implied by the numbered steps, so it could be tightened.

2 / 3

Actionability

It provides concrete executable commands (openspec list/status/instructions apply with --json), a defined report structure, and templated issue categories with actionable recommendations, despite a few vague 'search codebase for keywords' steps.

3 / 3

Workflow Clarity

An explicit 8-step sequence is given with severity-tiered validation guidance, false-positive calibration ('prefer SUGGESTION over WARNING, WARNING over CRITICAL'), and graceful-degradation fallbacks that act as checkpoints.

3 / 3

Progressive Disclosure

No bundle files exist and the single SKILL.md is under ~170 lines; content is well-organized into clearly headed sections, which satisfies the simple-skill allowance for a top score without external references.

3 / 3

Total

11

/

12

Passed

Description

90%

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 concise, well-structured description that clearly states capability and an explicit use-when trigger, occupying a distinct niche. It could list more discrete capabilities to push specificity higher.

Suggestions

Expand the capability clause to name discrete actions (e.g., 'check task completion, verify spec coverage, map requirements to code, and confirm design adherence') to raise specificity.

DimensionReasoningScore

Specificity

It names the domain ('change artifacts') and a core action ('Verify implementation matches') but does not enumerate multiple distinct concrete actions the way the score-3 anchor ('Extract text... fill forms, merge documents') does.

2 / 3

Completeness

It answers both 'what' (verify implementation matches change artifacts) and 'when' via an explicit 'Use when the user wants to validate... before archiving' trigger clause.

3 / 3

Trigger Term Quality

Phrases like 'validate that implementation is complete, correct, and coherent before archiving' are natural terms a user of this workflow would say, giving good coverage of relevant trigger vocabulary.

3 / 3

Distinctiveness Conflict Risk

The niche is sharply defined (verifying openspec change artifacts before archiving) with triggers unlikely to fire for unrelated skills.

3 / 3

Total

11

/

12

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
fengshao1227/ccg-workflow
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.