CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

goal-verifier

Verify goal completion.

Quality

43%

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/goal-audit/test/fixtures/good-goal-project/skills/goal-verifier/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

26%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 skill body is essentially empty — a lone '# Verifier' heading with no executable guidance, workflow, or references. While maximally concise, it provides nothing actionable and cannot guide Claude through the verification task.

Suggestions

Add a concrete verification procedure: how to check completion criteria and produce a pass/fail verdict, ideally with an executable command or code snippet.

Include a short ordered workflow with a validation/checkpoint step (e.g., re-checking unmet criteria before declaring completion) so the process is unambiguous.

If detailed checklists or rubrics belong in separate files, add clearly signaled one-level-deep references under a section heading.

DimensionReasoningScore

Conciseness

The body is just the heading '# Verifier' with no padding or over-explanation, so it is efficient and token-light; it stops short of a 5 because the brevity preserves no actual guidance, making it vacuous rather than meaningfully lean.

4 / 5

Actionability

There is no concrete code, command, or instruction beyond a heading, matching 'entirely vague or abstract; no concrete code or commands'.

1 / 5

Workflow Clarity

No steps, sequence, or validation checkpoints are present at all, matching 'steps missing or incoherent; no sequence'.

1 / 5

Progressive Disclosure

The body has only a single heading and no content, references, or bundle files, giving minimal structure with nothing organized for navigation; it is above 1 only because there is no nested-reference tangle.

2 / 5

Total

8

/

20

Passed

Description

33%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 a terse, third-person statement of purpose that answers 'what' but omits any 'when to use it' trigger guidance and uses only generic keywords. It is distinguishable enough to avoid the lowest scores but lacks the specificity and trigger coverage needed for a strong description.

Suggestions

Add an explicit 'Use when...' clause naming concrete trigger phrases (e.g., 'Use when checking whether a stated goal or task has been fully met').

Expand the 'what' with concrete actions, such as 'checks completion criteria, lists outstanding items, and reports a pass/fail verdict'.

Include natural synonyms users might say ('goal met', 'task done', 'completion check') to improve trigger term coverage and distinctiveness.

DimensionReasoningScore

Specificity

"Verify goal completion" names the domain (goal completion) but offers only a single generic action verb, matching the 'names the domain but actions are minimal or generic' anchor; it does not list concrete sub-actions so it is below a 3.

2 / 5

Completeness

It states a clear 'what' (verify goal completion) but has no 'Use when...' or equivalent 'when' guidance, which the guidelines cap at 3; not a 4 because the trigger context is entirely absent.

3 / 5

Trigger Term Quality

Only the generic keywords 'verify' and 'goal completion' appear with no synonyms, natural user phrases, or related trigger terms, fitting 'one or two generic keywords; missing the natural phrases users say'.

2 / 5

Distinctiveness Conflict Risk

The phrase is very broad and would overlap with many verification-oriented skills, matching 'very broad; high overlap risk'; it is not entirely generic (it scopes to goals) so it stays above 1.

2 / 5

Total

9

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

cobusgreyling/loop-engineering

Path

tools/goal-audit/test/fixtures/good-goal-project/skills/goal-verifier/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.