CtrlK
BlogDocsLog inGet started
Tessl Logo

kiro-verify-completion

Verify completion and success claims with fresh evidence. Use before claiming a task is complete, a fix works, tests pass, or a feature is ready for GO.

68

Quality

82%

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

81%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, actionable instruction-only skill with an explicit validation workflow and escalation paths. As an instruction skill it correctly omits code, and its clarity is high; the only minor gains are tighter phrasing and possibly externalizing the rationalizations table.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence (no padding about what verification or tests are); the brief <background_information> block and some repeated phrasing in Claim-Specific Rules are minor trims that could be made, so just below a 5.

4 / 5

Actionability

Concrete, executable guidance throughout: a 7-step gate function, per-claim-type requirement lists, and a copy-paste output template; since validation commands are intentionally discovered by the controller rather than specified, it stops just short of fully copy-paste-ready instructions.

4 / 5

Workflow Clarity

Clear sequenced gate (identify claim → identify proving command → require fresh evidence → check exit code/failures/skipped/coverage → reject over-broad claims → escalate → allow) with explicit validation checkpoints and escalation/feedback loops via NOT_VERIFIED and MANUAL_VERIFY_REQUIRED.

5 / 5

Progressive Disclosure

Well-organized single-file structure with clear section headers (When to Use, Inputs, Outputs, Gate Function, Claim-Specific Rules, Stop/Escalate, Rationalizations, Output Format) and no nested references; at ~125 lines with no bundle files to split into, it sits just below the one-level-deep reference ideal of a 5.

4 / 5

Total

17

/

20

Passed

Description

83%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 what the skill does and gives concrete, natural trigger conditions. It is specific and low-conflict, with only minor room for broader keyword/synonym coverage.

DimensionReasoningScore

Specificity

Names a concrete core action ("Verify completion and success claims with fresh evidence") and enumerates several specific claim scenarios (task complete, fix works, tests pass, feature ready for GO); minor gaps in coverage of verification actions keep it below a 5.

4 / 5

Completeness

Explicitly answers both what ("Verify completion and success claims with fresh evidence") and when ("Use before claiming a task is complete, a fix works, tests pass, or a feature is ready for GO") with concrete trigger phrases.

5 / 5

Trigger Term Quality

"Use before claiming a task is complete, a fix works, tests pass, or a feature is ready for GO" supplies natural phrases a user would say; a few common synonyms (e.g. "shipped", "done", "green") are missing, so not a 5.

4 / 5

Distinctiveness Conflict Risk

The completion-verification niche with GO/test/fix triggers is mostly distinct from peer skills; only minor overlap risk with general testing/build skills keeps it just below a 5.

4 / 5

Total

17

/

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
gotalab/cc-sdd
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.