CtrlK
BlogDocsLog inGet started
Tessl Logo

bmad-review-edge-case-hunter

Deprecated — forwards to bmad-review

53

Quality

60%

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%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 a model shim: it states the merge, gives a precise invocation-and-output contract, and handles the empty-findings edge case, all in a few terse sentences with no padding. It is appropriately structured for a deprecated forwarder that delegates substance to bmad-review.

DimensionReasoningScore

Conciseness

The ~70-word body is lean and assumes Claude's knowledge of bmad-review's 'legacy shape' and 'lens' conventions; every phrase (forwarding target, output constraints, the `[]` edge case) earns its place with no concept re-explanation.

5 / 5

Actionability

It gives a fully executable instruction — invoke `bmad-review` with exactly the `edge-case-hunter` lens, pass through `also_consider`, and emit a precisely specified legacy JSON shape — which is concrete and specific for an instruction-only shim.

5 / 5

Workflow Clarity

This is a single-action forwarding skill whose one action is unambiguous, and it includes explicit output-shape constraints plus the `[]` empty-result case; the simple-skill exception applies and no destructive/batch validation is needed.

5 / 5

Progressive Disclosure

The skill is under 50 lines, needs no bundle files, and correctly defers detail to the `bmad-review` skill it forwards to — appropriate one-level indirection with no nested or buried references.

5 / 5

Total

20

/

20

Passed

Description

21%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 an intentionally minimal deprecation marker: it signals the shim status and forwarding target but provides no capability, trigger, or usage context. It is distinctive enough to avoid random conflicts yet too sparse to guide invocation.

Suggestions

Add a brief capability phrase such as 'Hunts edge cases in reviewed content' before the deprecation note so the what is functional, not just meta.

Include a 'Use when...' clause naming the edge-case-hunter lens so trigger guidance is explicit.

Keep the forwarding instruction but surface the natural terms users would say (e.g., 'edge cases', 'review edge cases') to improve trigger-term quality.

DimensionReasoningScore

Specificity

The description 'Deprecated — forwards to bmad-review' names a single concrete action (forwarding) but offers no functional capability detail, matching the 'names the domain but actions are minimal' anchor rather than the entirely-vague anchor below.

2 / 5

Completeness

It gives a vague meta-'what' (forwards to bmad-review) and entirely omits any 'when' trigger guidance, matching the 'vague what and no when' anchor; it does not rise to a 3 because the stated what is not a clear capability.

2 / 5

Trigger Term Quality

No natural user-facing keywords appear; 'Deprecated' and 'forwards to bmad-review' are meta/jargon a user would never utter when seeking edge-case hunting, fitting the 'no natural keywords; only technical jargon' anchor.

1 / 5

Distinctiveness Conflict Risk

It explicitly names bmad-review, giving it a specific niche, but by design it overlaps directly with that related skill, fitting 'somewhat specific but could still overlap with similar skills' rather than the mostly-distinct anchor above.

3 / 5

Total

8

/

20

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

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

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.