verification-loop
A comprehensive verification system for Claude Code sessions.
Install with Tessl CLI
npx tessl i github:affaan-m/everything-claude-code --skill verification-loop56
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
0%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description is critically weak across all dimensions. It provides no concrete actions, no natural trigger terms, no guidance on when to use it, and is so vague it could conflict with numerous other skills. The phrase 'comprehensive verification system' is meaningless without specifics about what is being verified and how.
Suggestions
Replace 'comprehensive verification system' with specific actions like 'Validates code output, checks test results, verifies file changes' to improve specificity
Add a 'Use when...' clause with natural trigger terms users would say, such as 'Use when the user asks to check, validate, verify, or review session changes'
Define the specific domain clearly - what exactly is being verified (code quality, test results, file integrity, session state) to reduce conflict with other skills
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language ('comprehensive verification system') without listing any concrete actions. It does not specify what verification means or what actions Claude would perform. | 1 / 3 |
Completeness | Missing both 'what' (no specific capabilities listed) and 'when' (no trigger guidance or use cases). The description fails to answer either question meaningfully. | 1 / 3 |
Trigger Term Quality | Contains no natural keywords users would say. 'Verification system' and 'Claude Code sessions' are technical jargon that users wouldn't naturally use when requesting help. | 1 / 3 |
Distinctiveness Conflict Risk | Extremely generic - 'verification system' could apply to testing, code review, authentication, validation, or many other domains. High conflict risk with any skill involving checking or validating. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid, actionable verification skill with clear multi-phase workflows and explicit validation checkpoints. The main weakness is moderate verbosity in explanatory sections and lack of progressive disclosure to external files for advanced topics. The executable commands and structured output format are particular strengths.
Suggestions
Remove the 'When to Use' section - Claude can infer appropriate invocation contexts from the skill content itself
Move 'Continuous Mode' and 'Integration with Hooks' to a separate ADVANCED.md file with a brief reference link
Trim explanatory text like 'This skill complements PostToolUse hooks but provides deeper verification' which doesn't add actionable value
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Generally efficient with executable commands, but includes some unnecessary explanation (e.g., 'This skill complements PostToolUse hooks but provides deeper verification') and the 'When to Use' section explains obvious use cases Claude would infer. | 2 / 3 |
Actionability | Provides fully executable bash commands for each verification phase, specific output formats, and copy-paste ready code blocks. Commands include practical output limiting (head/tail) for real-world use. | 3 / 3 |
Workflow Clarity | Clear 6-phase sequence with explicit stop conditions ('If build fails, STOP and fix before continuing'), validation checkpoints at each phase, and a structured output report format that serves as a checklist. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but everything is inline in a single file. The 'Continuous Mode' and 'Integration with Hooks' sections could be separate references, and there are no links to external documentation for advanced usage. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- 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.