CtrlK
BlogDocsLog inGet started
Tessl Logo

bmad-review-edge-case-hunter

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-edge-case-hunter/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 lean, highly actionable forwarding instruction that specifies the exact invocation and output contract with no wasted tokens. It cleanly serves its single purpose.

DimensionReasoningScore

Conciseness

A single dense paragraph with no padding and no explanation of concepts Claude already knows; every token earns its place.

3 / 3

Actionability

Gives concrete, executable guidance: exact invocation (bmad-review with edge-case-hunter lens, pass-through also_consider) and precise output-format constraints (raw JSON, four fields, kind/confidence on deletions, no lens/markdown).

3 / 3

Workflow Clarity

It is a simple single-action skill (invoke another skill, format output) with an unambiguous sequence and no destructive/batch step requiring validation.

3 / 3

Progressive Disclosure

Under 50 lines with no need for external references; the single coherent forwarding instruction is appropriately self-contained for such a minimal skill.

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 deprecated-forwarding notice: it conveys the forwarding action and target but omits any usage trigger and the legacy surface terms that would drive activation. Trigger-term quality is the main weakness.

Suggestions

Add a "Use when..." clause naming the natural trigger terms (e.g., "edge-case-hunter", "edge case review") so the deprecated skill activates on the original intent.

Mention the legacy skill name or lens keyword in the description so users referencing the old surface discover the forwarder.

Lead with a one-phrase statement of purpose (edge-case finding) before the forwarding note, instead of only "Deprecated — forwards to".

DimensionReasoningScore

Specificity

Names a single concrete action ("forwards to") and a specific target skill, but offers no broader capability description.

2 / 3

Completeness

It states what the skill does (forwards to bmad-review) but provides no "Use when..." guidance for when Claude should invoke it, capping completeness at 2.

2 / 3

Trigger Term Quality

The description contains no natural trigger terms a user would say; the legacy skill/lens name "edge-case-hunter" is absent, so the deprecated stub would not surface on the right intent.

1 / 3

Distinctiveness Conflict Risk

It is tied to a specific named skill (bmad-review) so conflict risk is low, but without distinct triggers it could still overlap with sibling bmad-review skills.

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.