CtrlK
BlogDocsLog inGet started
Tessl Logo

kiro-validate-impl

Validate feature-level integration after all tasks are implemented. Checks cross-task consistency, full test suite, and overall spec coverage.

60

Quality

70%

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

Fix and improve this skill with Tessl

tessl review fix ./tools/cc-sdd/templates/agents/antigravity-skills/skills/kiro-validate-impl/SKILL.md
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.

The content is a well-structured, actionable validation workflow with explicit decision gates and feedback loops, and it is appropriately concise for the complexity it covers. Progressive disclosure is good but the single long file has no external reference layer.

DimensionReasoningScore

Conciseness

The body is dense and targeted; the background section explains kiro-specific boundary terminology Claude would not already know, with only minor repeated emphasis on boundary integrity that could be trimmed — matching the 'efficient; minor instances of over-explanation' anchor.

4 / 5

Actionability

Provides concrete commands (grep patterns for TBD/TODO and secrets, canonical command discovery), specific file paths under {{KIRO_DIR}}/specs/, and a copy-ready report template; judgment checks are necessarily descriptive rather than executable, matching the 'mostly executable guidance; minor gaps' anchor.

4 / 5

Workflow Clarity

A clear four-step sequence (Detect Target → Load Context → Execute Validation → Generate Report) with explicit validation gates (GO/NO-GO/MANUAL_VERIFY_REQUIRED) and a feedback loop (NO-GO → mandatory remediation → re-validate); the skill is read-only/idempotent so the destructive/batch cap does not apply, matching the top anchor.

5 / 5

Progressive Disclosure

No bundle files exist and the skill is a self-contained cohesive workflow organized into well-labeled sections (background_information, instructions with numbered steps, Safety & Fallback), matching the 'good structure; most content appropriately placed' anchor; not a 5 because it is a single ~180-line document with no one-level-deep reference split.

4 / 5

Total

17

/

20

Passed

Description

58%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 gives a clear, moderately specific statement of what the skill does but omits any explicit 'Use when…' trigger guidance, which caps both completeness and trigger-term quality. It is reasonably distinctive within the kiro workflow niche.

Suggestions

Add an explicit 'Use when…' clause, e.g. 'Use when all tasks for a kiro feature are marked complete and you need cross-task integration validation before declaring the feature done.'

Include natural trigger synonyms a user might say, such as 'validate implementation', 'integration check', or 'verify feature complete'.

Broaden the action list to mention design-alignment and boundary-audit checks so specificity approaches comprehensive coverage.

DimensionReasoningScore

Specificity

Names the domain ('feature-level integration') and lists three concrete actions ('cross-task consistency, full test suite, and overall spec coverage'), matching the 'several specific actions; minor gaps' anchor; not a 5 because coverage is incomplete (e.g., design alignment, boundary audit not mentioned).

4 / 5

Completeness

A clear 'what' is stated but there is no explicit 'when'/'Use when' clause; per the judging guidelines a missing explicit trigger clause caps completeness at 3.

3 / 5

Trigger Term Quality

Relevant keywords ('Validate', 'integration', 'test suite', 'spec coverage') are present but there is no 'Use when…' phrasing and no synonyms or natural variations users would say, matching the 'some relevant keywords but missing common variations' anchor.

3 / 5

Distinctiveness Conflict Risk

The 'feature-level integration' and 'cross-task' framing carves a clear niche distinct from task-local review, with only minor overlap risk against general test/validation skills, matching the 'mostly distinct; minor overlap risk' anchor.

4 / 5

Total

14

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

15

/

16

Passed

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.