CtrlK
BlogDocsLog inGet started
Tessl Logo

verification-loop

A comprehensive verification system for Claude Code sessions.

50

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

85%

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, highly actionable verification workflow with concrete commands, explicit validation checkpoints, and a useful report template. Its only real weakness is minor redundancy and fluff that slightly hurt token efficiency.

DimensionReasoningScore

Conciseness

The body is mostly lean commands, but it repeats the full test-suite command in both Phase 4 and the Pre-Push Gate and includes mild fluff ("Set a mental checkpoint", "Run: /verify"), so it could be tightened rather than earning the every-token-earns-its-place anchor.

2 / 3

Actionability

It provides concrete, copy-paste-ready commands (npx nx run-many, tsc --noEmit, nx lint, grep/git invocations) plus a filled-in report template, matching the fully-executable anchor.

3 / 3

Workflow Clarity

Phases 1–6 are clearly sequenced with explicit checkpoints ("If build fails, STOP and fix", "Fix critical ones before continuing") and a pre-push feedback loop (fail → fix → re-run full suite → push), matching the clear-sequence-with-validation anchor.

3 / 3

Progressive Disclosure

It is a self-contained single-purpose checklist with well-organized section headers and no nested or broken references; no bundle files exist and none are needed, so well-organized inline sections satisfy the disclosure goal.

3 / 3

Total

11

/

12

Passed

Description

25%

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 too vague and generic: it names no concrete actions and provides no trigger terms or "Use when" guidance, making it hard to distinguish from related quality-assurance skills. It identifies its domain but little else.

Suggestions

List concrete capabilities in the description (e.g. "Runs builds, type checks, lint, tests, and secret scans, then produces a PR-readiness report").

Add an explicit trigger clause such as "Use when finishing a feature, before opening a PR, or before a git push."

Include natural user-facing keywords (build, type-check, lint, tests, coverage, PR, push) so the skill triggers on real requests.

DimensionReasoningScore

Specificity

The phrase "A comprehensive verification system" is abstract and names no concrete actions, matching the vague-language anchor rather than the level-2 anchor which requires named actions.

1 / 3

Completeness

It states a (weak) "what" but gives no "when" trigger guidance, so the missing "Use when..." clause caps it at 2; it is not 1 because the domain (verification for Claude Code sessions) is at least identified.

2 / 3

Trigger Term Quality

It contains no natural user-facing keywords (e.g. "tests", "build", "lint", "PR"); "verification system for Claude Code sessions" reads as generic jargon rather than terms a user would naturally say.

1 / 3

Distinctiveness Conflict Risk

"Verification system" could overlap with code-review or testing skills, but scoping it to "Claude Code sessions" gives it a partial niche, placing it between the generic and clearly-distinct anchors.

2 / 3

Total

6

/

12

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
devrev/meerkat
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.