CtrlK
BlogDocsLog inGet started
Tessl Logo

bmad-market-research

Deprecated — forwards to bmad-deep-recon (market type)

55

Quality

62%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

High

Do not use without reviewing

Fix and improve this skill with Tessl

tessl review fix ./src/bmm-skills/v6-shims/bmad-market-research/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

92%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 shim body is a tight, executable 3-step forwarding workflow with concrete commands and a clear stop condition. Its only weakness is slight verbosity in the consolidated-skill description paragraph.

DimensionReasoningScore

Conciseness

The body is lean and assumes competence, giving the exact resolution command, notice text, and forwarding parameters with only minor over-explanation in the consolidated-skill summary paragraph.

4 / 5

Actionability

It provides a fully executable resolve_customization.py command, verbatim deprecation-notice wording, and concrete invocation parameters (research type market, the four legacy fields, original input), all copy-paste ready.

5 / 5

Workflow Clarity

The three-step On Activation sequence is clearly ordered with an explicit stop guard ('do not execute any further steps in this shim'), and the operation is non-destructive so the validation-cap does not apply.

5 / 5

Progressive Disclosure

This is a short single-purpose shim under 50 lines with no external bundle files and a well-organized 'On Activation' section, satisfying the simple-skill exception for progressive disclosure.

5 / 5

Total

19

/

20

Passed

Description

32%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.

This is a deprecated compatibility-shim description that communicates its forwarding role but lacks trigger guidance and natural user keywords. It is distinct but thin on completeness and specificity.

Suggestions

Add an explicit 'Use when...' trigger clause (e.g., legacy invocations of bmad-market-research) so the 'when' is stated, not implied.

Include natural user-facing keywords like 'market research' alongside the technical forwarding note.

Briefly state the concrete outcome (drafts market research prompts / summarizes reports) so the 'what' is more than 'forwards'.

DimensionReasoningScore

Specificity

The description only states it 'forwards to bmad-deep-recon (market type)' — it names the delegation target and type but performs no concrete actions of its own, matching the anchor that names a domain with minimal/generic actions.

2 / 5

Completeness

It gives a vague 'what' (forwards/delegates) and provides no 'when'/Use-when guidance at all, matching the anchor for a vague 'what' with no 'when'.

2 / 5

Trigger Term Quality

Beyond 'market' there are no natural phrases a user would say to invoke this skill; the text is dominated by internal naming ('bmad-deep-recon', 'shim') rather than user-facing trigger terms.

2 / 5

Distinctiveness Conflict Risk

The description scopes the skill to a specific legacy name forwarding to a named target, giving it a clear distinct niche with only minor overlap risk against general market-research requests.

4 / 5

Total

10

/

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.