verification-loop

This skill should be used when the user asks to "verify code", "run verification", "check quality", "validate changes", or before creating a PR. Provides comprehensive verification including build, type check, lint, tests, security scan, and diff review.

Quality

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

High

Do not use without reviewing

Quality

Content

75%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 well-structured and actionable with strong per-phase validation gates, but loses points for an inlined duplicate of the report template, a broken example reference, and minor filler prose.

Suggestions

Remove the inline "Output Format" report block and point to references/REPORT-TEMPLATE.md instead to avoid duplication and reduce tokens.

Delete or create the referenced examples/example-verification-report.md; a broken reference undermines navigation.

Trim the opening line and the "Integration with Hooks" section to essentials, or move them into a reference file, to tighten conciseness.

Dimension	Reasoning	Score
Conciseness	Mostly lean phase-and-command structure, but the opener ("A comprehensive verification system...") and the hooks-comparison prose are slight filler that could be trimmed.	4 / 5
Actionability	Provides concrete, executable commands across stacks plus a copy-ready report template; minor gaps such as assuming pyright/ruff are installed and using grep in place of a real secret scanner.	4 / 5
Workflow Clarity	Six clearly sequenced phases with explicit stop-and-fix gates ("If build fails, STOP and fix before continuing"); recovery loops are terse rather than fully spelled out, so it sits just below the anchor-5 checklist bar.	4 / 5
Progressive Disclosure	References real one-level-deep bundle files (STACK-DETECTION.md, REPORT-TEMPLATE.md), but the report template is duplicated inline and the cited examples/example-verification-report.md does not exist.	4 / 5
	Total	16 / 20 Passed

Description

100%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 strong example: it pairs concrete capabilities with natural trigger phrasing and an explicit use-when clause, all in third person. It scores at the top of every dimension.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete verification actions (build, type check, lint, tests, security scan, diff review) with comprehensive coverage matching the anchor-5 example.	5 / 5
Completeness	Explicitly answers both what (comprehensive verification across build/types/lint/tests/security/diff) and when (explicit trigger phrases plus the PR-creation context), matching the anchor-5 example.	5 / 5
Trigger Term Quality	Provides natural user phrasings ("verify code", "run verification", "check quality", "validate changes", "before creating a PR") with synonym coverage, matching the anchor-5 example.	5 / 5
Distinctiveness Conflict Risk	Occupies a clear QA-gate-before-PR niche with distinct trigger phrases and minimal overlap risk with other skills.	5 / 5
	Total	20 / 20 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: Galaxy-Dawn/claude-scholar
Path: skills/verification-loop/SKILL.md
Commit: 6ed46da

Reviewed: 8 days ago

Table of Contents

Discovery Implementation Validation

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.