verification-loop

A comprehensive verification system for Kiro sessions.

Quality

51%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.kiro/skills/verification-loop/SKILL.md

Quality

Content

75%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.

The body is a well-structured, actionable verification workflow with concrete commands and clear stop-gate checkpoints. It is concise and appropriately self-contained, with only minor padding and a few phases that lean on guidance rather than code.

Dimension	Reasoning	Score
Conciseness	The body is largely efficient with copy-paste commands and minimal concept explanation, but minor padding exists (the repeated lead sentence 'A comprehensive verification system...' and the somewhat fluffy 'Continuous Mode'/'Integration with Hooks' sections), fitting the 'efficient; minor instances that could be trimmed' anchor rather than the fully lean anchor 5.	4 / 5
Actionability	It provides concrete, executable commands for every phase (npm run build, npx tsc --noEmit, npm run lint, npm run test -- --coverage, grep scans, git diff) plus a copy-paste report template, but the security scan is simplistic and the diff-review phase is descriptive guidance rather than commands, leaving minor gaps below the fully-executable anchor 5.	4 / 5
Workflow Clarity	Six phases are clearly sequenced with explicit stop gates ('If build fails, STOP and fix before continuing', 'Fix critical ones before continuing') and a structured output report, but the feedback loops are terse rather than full validate-fix-retry cycles, matching anchor 4; verification is non-destructive so the destructive/batch cap does not apply.	4 / 5
Progressive Disclosure	Content is well-organized into clearly headed sections (When to Use, Verification Phases, Output Format, Continuous Mode, Integration with Hooks) with no nested or buried references, and no external bundle files are needed for this self-contained workflow; minor tangential sections keep it just below the ideal anchor 5.	4 / 5
	Total	16 / 20 Passed

Description

28%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.

The description is too vague to function as an effective skill trigger: it states a domain without any concrete actions or a 'Use when...' clause. It would rarely be selected on the basis of the description alone.

Suggestions

List the concrete verification actions performed, e.g. 'Runs build, type-check, lint, tests with coverage, secret scan, and diff review for Kiro sessions.'

Add an explicit trigger clause, e.g. 'Use after completing a feature, before creating a PR, or when you need to confirm quality gates pass.'

Include natural trigger terms users would actually say: 'verify', 'run checks', 'quality gates', 'before PR', 'pre-PR review'.

Dimension	Reasoning	Score
Specificity	The description names the domain ("verification system for Kiro sessions") but lists zero concrete actions — none of the actual phases (build, type check, lint, test, security, diff) appear, matching the 'names domain but actions minimal/generic' anchor; it is above the purely vague anchor 1 because a specific domain is named.	2 / 5
Completeness	It offers only a vague 'what' ("comprehensive verification system") with no 'when' clause at all, matching anchor 2; the judging guideline caps completeness at 3 for missing trigger guidance, and the vague 'what' pulls it further down.	2 / 5
Trigger Term Quality	Only 'verification' and 'Kiro sessions' appear as keywords; the natural phrases a user would say ('run checks', 'before PR', 'quality gates', 'verify my code') are absent, fitting the 'one or two generic keywords; missing natural phrases' anchor.	2 / 5
Distinctiveness Conflict Risk	Bounding to 'Kiro sessions' gives it some specificity, but 'verification' is broad and overlaps with general QA/lint/review skills, fitting the 'somewhat specific but could still overlap' anchor; it is not broad enough for a 2 nor distinct enough for a 4.	3 / 5
	Total	9 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: affaan-m/ECC
Path: .kiro/skills/verification-loop/SKILL.md
Commit: d8409a4

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.