CtrlK
BlogDocsLog inGet started
Tessl Logo

bmad-review-adversarial-general

Deprecated — forwards to bmad-review

51

Quality

56%

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-adversarial-general/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

82%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 an exemplary lean shim: it tells Claude exactly which skill to invoke, with which lens, what to pass through, and how to format the output. It would benefit only marginally from a concrete invocation example and a brief post-invocation verification note.

DimensionReasoningScore

Conciseness

Two lean sentences ('Merged into bmad-review.' and the forwarding instruction) with no padding and no over-explanation, matching the 'every token earns its place' anchor.

5 / 5

Actionability

Concrete, specific instructions specify the lens ('only the adversarial lens'), the passthrough ('also_consider areas'), and the output format ('Markdown list — descriptions only, no severity... no JSON block'); it stops short of anchor 5 only because no literal invocation command or example output is shown.

4 / 5

Workflow Clarity

The single forward-and-format action is unambiguous and well-sequenced; the simple-skill exception could justify a 5, but the absence of any verification that the forwarded skill actually ran keeps it at anchor 4.

4 / 5

Progressive Disclosure

For a sub-50-line shim with no need for external references, the self-contained single paragraph is well-organized; it does not reach anchor 5 only because there are no section headers to signal structure.

4 / 5

Total

17

/

20

Passed

Description

30%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 honestly signals deprecation and a single forwarding action, but it is too terse to convey capabilities, natural triggers, or usage timing. It reads as a status label rather than an actionable skill description.

Suggestions

Add an explicit 'Use when...' clause so users know when this shim should fire (e.g., 'Use when the deprecated adversarial-general review is requested').

Include a natural trigger term users would actually say, rather than only the technical name 'bmad-review'.

Briefly state the lens/output contract in the description so the skill's behavior is clear without opening the body.

DimensionReasoningScore

Specificity

Quotes 'Deprecated — forwards to bmad-review' name the domain (a shim) and one minimal action; it falls below the midpoint because coverage is a single terse action rather than the 1–2 concrete actions of anchor 3.

2 / 5

Completeness

The 'what' is clear ('forwards to bmad-review') but there is no 'when'/Use-when clause, which per the guidelines caps completeness at 3.

3 / 5

Trigger Term Quality

Contains only the technical skill name 'bmad-review' and the word 'Deprecated'; a user would not naturally say these to invoke the skill, matching the 'no natural keywords' anchor.

1 / 5

Distinctiveness Conflict Risk

It targets one specific skill ('bmad-review') so it is somewhat distinct, but the terse phrasing leaves overlap risk and lacks the clear niche triggers of anchor 4.

3 / 5

Total

9

/

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.