CtrlK
BlogDocsLog inGet started
Tessl Logo

bmad-review-verification-gap

Deprecated — forwards to bmad-review.

59

Quality

67%

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 ./src/core-skills/v6-shims/bmad-review-verification-gap/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a tight, fully actionable delegation instruction with an explicit edge-case handling rule and no wasted tokens. It is an exemplar of a concise forwarding skill and needs no improvement.

DimensionReasoningScore

Conciseness

The body is four lean sentences of pure instruction with no padding and no explanation of concepts Claude already knows; every token carries actionable direction.

3 / 3

Actionability

It gives concrete, executable guidance: invoke bmad-review with the verification-gap lens, render markdown only, list gap_shape "other" findings under a named heading, and emit the exact literal 'No verification gaps found.' when empty.

3 / 3

Workflow Clarity

The delegation sequence is unambiguous — run the lens, format markdown, branch on no findings — and the explicit no-findings case acts as a clear conditional checkpoint, satisfying the simple-skill allowance for a 3.

3 / 3

Progressive Disclosure

This is a short single-paragraph skill under 50 lines with no need for external references, so the well-organized inline content meets the progressive-disclosure bar without separate files.

3 / 3

Total

12

/

12

Passed

Description

35%

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 deprecation forwarder: it conveys what it does (forwards to bmad-review) but omits any trigger guidance and contains no natural user keywords, leaving it indistinguishable from the skill it delegates to. It is clear but minimal and would benefit from an explicit 'Use when...' clause.

Suggestions

Add a 'Use when ...' clause stating when this forwarder should be invoked instead of bmad-review directly, so the description answers both what and when.

Include natural trigger terms a user might actually say (e.g. 'verification gap review', 'review findings') rather than relying on the bare skill name 'bmad-review'.

Clarify the distinction from bmad-review itself, since a description that only says 'forwards to bmad-review' gives the router no basis to choose this skill over the target.

DimensionReasoningScore

Specificity

The phrase 'forwards to bmad-review' names one concrete action and its target skill, but it is a single action rather than the multiple specific actions the top anchor calls for.

2 / 3

Completeness

It states what the skill does ('forwards to bmad-review') but provides no 'Use when...' clause or any trigger guidance for when Claude should invoke it, capping completeness at 2 per the guidelines.

2 / 3

Trigger Term Quality

'Deprecated' and 'forwards' are not terms a user would naturally say when they need this skill; the description contains no natural trigger keywords, only a deprecation notice and a skill name.

1 / 3

Distinctiveness Conflict Risk

It targets a specific named skill, but because it forwards directly to bmad-review it overlaps with that skill and gives no trigger context to distinguish when this forwarder vs bmad-review itself should fire.

2 / 3

Total

7

/

12

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
bmad-code-org/BMAD-METHOD
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.