CtrlK
BlogDocsLog inGet started
Tessl Logo

loop-verifier

Independent checker for release note drafts. Reviews accuracy against the changelog-scan data, tone, completeness, and flags breaking/security items. Use after draft-release-notes. Never let the drafter verify itself.

64

Quality

76%

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

Quality

Content

86%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 tight, well-structured instruction-only skill that tells Claude exactly what to check and what to emit, with a concrete verdict template. Its only real gap is an implicit rather than explicit feedback loop for the REVISE case.

DimensionReasoningScore

Conciseness

Lean and efficient with no padding or explanation of concepts Claude already knows; the stance line, checklist, and output template each earn their place.

5 / 5

Actionability

A concrete 6-item checklist plus a copy-paste verdict template with explicit APPROVE/REVISE/ESCALATE_HUMAN options gives mostly executable guidance; the only gap is the lack of a worked example of a filled-in verdict.

4 / 5

Workflow Clarity

The Inputs→Checklist→Output sequence is clear with the checklist serving as validation checkpoints, but the REVISE re-verify feedback loop is implicit rather than an explicit retry instruction.

4 / 5

Progressive Disclosure

Under 50 lines, single-purpose, no external references needed, and organized into clearly labeled sections (Inputs, Checklist, Output), meeting the simple-skill exception.

5 / 5

Total

18

/

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.

A solid, third-person description that clearly states what the skill does and when to use it, with a well-defined niche distinct from the drafter skill. It is held back mainly by trigger-term quality, which relies on skill-name jargon rather than natural user phrases.

Suggestions

Add natural user-trigger phrases, e.g. 'Use when the user asks to verify, check, or QA release notes or a changelog draft'.

Replace or supplement the skill-name references ('changelog-scan', 'draft-release-notes') with plain synonyms (changelog, release notes) so the description triggers on user language, not internal workflow names.

DimensionReasoningScore

Specificity

Lists several concrete actions ('Reviews accuracy…tone, completeness, and flags breaking/security items') within a clear domain, but the actions are somewhat abstract compared to the fully comprehensive 5 anchor.

4 / 5

Completeness

Provides a clear 'what' and an explicit 'when' ('Use after draft-release-notes'), but the when is a skill-sequencing cue rather than a concrete user-trigger phrase, so it stops short of 5.

4 / 5

Trigger Term Quality

Domain terms appear (release notes, changelog, breaking/security) but the description leans on internal skill-name jargon ('changelog-scan', 'draft-release-notes') and omits natural user verbs/synonyms like 'verify' or 'check my notes'.

3 / 5

Distinctiveness Conflict Risk

Occupies a clear niche with explicit separation ('Never let the drafter verify itself'), carrying only minor overlap risk with generic review/QA requests.

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.