CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

aif-verify

Verify completed implementation against the plan. Checks that all tasks were implemented, nothing was forgotten, code compiles, tests pass, and quality standards are met. Use after "/aif-implement" completes, or when user says "verify", "check work", "did we miss anything".

Quality

81%

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

67%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-architected instruction-only skill: concrete commands, regexes, and gate contracts make it actionable, and the reference bundle is genuinely progressive with conditional one-level-deep loading. The main costs are token inefficiency from duplicated precedence policy and generic interaction rules, plus section-numbering defects that slightly muddy the workflow sequence.

Suggestions

State the skill-context precedence rules once — either in the 'Shared project skill-context' section or Step 0.3 — instead of repeating them in both places.

Move the generic 'Runtime-aware questions' contract into a shared reference, since it is session-interaction policy rather than verification-specific guidance.

Fix section numbering: two sections are labeled 0.3, 'Plan discovery' is unnumbered despite being referenced as Step 0.2, and the body jumps to 'Step 3' with no Steps 1–2, which obscures the actual audit sequence.

DimensionReasoningScore

Conciseness

Skill-context precedence rules are stated twice (the 'Shared project skill-context' section and again in Step 0.3) and the 'Runtime-aware questions' section is generic interaction policy unrelated to verification, fitting 'mostly efficient but includes some unnecessary explanation or could be tightened'; it is not a 2 because the majority of the body is directly relevant procedural instruction with no basic-concept padding.

3 / 5

Actionability

Provides concrete git diff commands, exact config keys and paths, a fully specified parsing regex, and an exact SHA-256 hashing procedure — 'mostly executable guidance with minor gaps'; placeholders like '<configured-base-branch>' and 'HEAD~$(number_of_tasks)' prevent a 5 since commands are not copy-paste ready.

4 / 5

Workflow Clarity

The load-context → plan-discovery → audit → consistency → report sequence is clear and validation-heavy (strict-mode checklist, WARN/ERROR gate semantics, 'never treat missing evidence as a passing check'), but numbering defects — two sections labeled 0.3, an unnumbered 'Plan discovery' heading, and a jump to 'Step 3' with no Steps 1–2 — constitute the 'minor validation gaps' of the score-4 anchor rather than the fully coherent sequence of a 5.

4 / 5

Progressive Disclosure

All eight referenced files exist, are one level deep, and each load is gated by an explicit condition ('read only when a worked rendering is needed', 'only when usage help is needed'), with cross-references pointing back to already-loaded files instead of nesting. It stays at 4 rather than 5 because deep procedural detail (the SHA-256 drift procedure, repeated precedence rules) is inlined in the entrypoint where the well-established reference pattern could carry it.

4 / 5

Total

15

/

20

Passed

Description

88%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 strong: it states concrete capabilities and an explicit, trigger-phrase-rich 'Use when' clause in third person. Its only weaknesses are slightly incomplete natural-term coverage and mild overlap risk from generic trigger phrases like 'check work'.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Checks that all tasks were implemented', 'code compiles', 'tests pass' — giving comprehensive coverage of the verification domain; only 'quality standards are met' is mildly generic, which is not enough to drop to the score-4 anchor's 'minor gaps in coverage'.

5 / 5

Completeness

Explicitly answers both what ('Verify completed implementation against the plan. Checks that all tasks were implemented... code compiles, tests pass') and when ('Use after "/aif-implement" completes, or when user says "verify", "check work", "did we miss anything"') with concrete trigger phrases, exactly matching the top anchor.

5 / 5

Trigger Term Quality

Includes natural user phrases 'verify', 'check work', 'did we miss anything' plus the '/aif-implement' linkage, but misses common variations like 'review the implementation' or 'is everything done', matching the 'good keyword coverage; a few natural terms missing' anchor rather than comprehensive coverage.

4 / 5

Distinctiveness Conflict Risk

'Verify completed implementation against the plan' carves a clear post-implementation niche, but the generic phrases 'check work' and 'did we miss anything' could overlap with code-review or QA skills, fitting 'mostly distinct; minor overlap risk with closely related skills' rather than minimal conflict risk.

4 / 5

Total

18

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

14

/

16

Passed

Repository

lee-to/ai-factory

Path

skills/aif-verify/SKILL.md

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.