CtrlK
BlogDocsLog inGet started
Tessl Logo

loop-verifier

Independent verification agent for loop-produced changes. Finds reasons to reject. Runs tests. Confirms diff scope. Use after minimal-fix or any implementer sub-agent — never in the same role as the implementer.

61

Quality

73%

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 ./skills/loop-verifier/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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 tight, well-structured maker/checker procedure with a concrete checklist, output template, and validation feedback loop. Its main weakness is mild redundancy between the Checklist and Rules sections and the lack of a worked example verdict.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence with no concept over-explanation, but the Rules section restates checklist items (e.g., 'Do not trust implementer's claim — run them' overlaps checks 3-4), a minor redundancy that could be trimmed.

4 / 5

Actionability

Provides a concrete checklist, a copy-paste-ready output template, and explicit rules; as an instruction-only skill the absence of code is acceptable, though no filled-out example verdict is shown.

4 / 5

Workflow Clarity

Clear checklist with an 'all must pass for APPROVE' gate, explicit validation (run tests), and a feedback loop (REJECT with reasons + suggested next step); minor gaps in that checks are not strictly sequenced and recovery is handed off rather than internal.

4 / 5

Progressive Disclosure

Under 50 lines, single-purpose, no external references needed, and well-organized into Inputs/Checklist/Output/Rules sections, meeting the simple-skill exception for a top score.

5 / 5

Total

17

/

20

Passed

Description

67%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 third-person, concise, and clearly communicates a distinct verification role with an explicit use-clause. It is somewhat held back by technical jargon over natural trigger terms and a positional rather than user-facing when-condition.

Suggestions

Add natural user-facing trigger phrases (e.g., 'Use when you need to review or verify changes made by an implementer agent') to broaden trigger-term coverage.

Include common synonyms such as 'review', 'check', or 'audit' alongside 'verification' so users phrasing the need differently still match.

Tighten the when-clause to reference the user's intent (verifying/rejecting changes) rather than only the loop's internal stage names.

DimensionReasoningScore

Specificity

Lists several concrete actions ('Finds reasons to reject. Runs tests. Confirms diff scope.') but coverage is narrow to the verification niche, leaving minor gaps.

4 / 5

Completeness

Clearly states what it does and includes an explicit 'Use after minimal-fix or any implementer sub-agent' when-clause, though the when is workflow-positional rather than user-natural trigger phrases.

4 / 5

Trigger Term Quality

Relevant keywords (verification, tests, diff scope, minimal-fix, implementer sub-agent) are present but lean technical; common natural synonyms like 'review the changes' or 'check the fix' are missing.

3 / 5

Distinctiveness Conflict Risk

Carves out a clear maker/checker niche tied to loop-produced changes with minimal conflict risk, though it has minor overlap with general code-review skills.

4 / 5

Total

15

/

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository
cobusgreyling/loop-engineering
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.