CtrlK
BlogDocsLog inGet started
Tessl Logo

bmad-market-research

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

52

Quality

58%

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/bmm-skills/v6-shims/bmad-market-research/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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 well-structured, concise activation workflow that gives Claude concrete commands and an explicit handoff boundary to the consolidated skill. Its only weakness is minor padding describing the target skill's capabilities.

DimensionReasoningScore

Conciseness

The body is lean and mostly assumes Claude's competence; the only mild padding is the one-sentence catalog of bmad-deep-recon's full capability surface, which a shim does not strictly need.

4 / 5

Actionability

Step 1 gives a concrete executable command with full arguments, and steps 2-3 specify exact notice text and invocation parameters; the invocation in step 3 stays slightly abstract rather than copy-paste ready.

4 / 5

Workflow Clarity

A clear three-step numbered sequence with an explicit terminal checkpoint ("do not execute any further steps in this shim"); this is a non-destructive handoff so no validation feedback loop is required.

4 / 5

Progressive Disclosure

A short single-purpose shim (under 50 lines, no bundle files) with a clear heading and one well-organized activation section, qualifying for the simple-skill exception.

5 / 5

Total

17

/

20

Passed

Description

37%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 accurately signals the skill's deprecated-shim status and forwarding target, but it functions as a lifecycle label rather than a capability/trigger description. It lacks natural trigger terms and any "when to use" guidance.

Suggestions

Add a "Use when..." clause naming the natural trigger phrases users say, e.g. "Use when the user asks for market research or competitive analysis and invokes the legacy bmad-market-research name."

Include concrete trigger synonyms ("market research", "competitive analysis", "market sizing") so the description surfaces on real user requests.

Keep the deprecation note but pair it with the actual capability being forwarded ("drafts and processes market research") so the what is concrete, not just mechanical.

DimensionReasoningScore

Specificity

The description names one mechanical action ("forwards to bmad-deep-recon (market type)") but offers no concrete user-facing capabilities; it matches the anchor that names a domain with minimal actions.

2 / 5

Completeness

It conveys a clear "what" (forwards to bmad-deep-recon with the market type) but provides no "Use when..." trigger guidance, which caps completeness at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

Only the word "market" resembles a natural trigger; the rest ("Deprecated", "forwards to bmad-deep-recon") is lifecycle/technical jargon, missing the natural phrases a user would say like "market research" or "competitive analysis".

2 / 5

Distinctiveness Conflict Risk

It is scoped to a specific legacy name and market type, but as a shim it intentionally overlaps with bmad-deep-recon, so it could trigger for the same requests as its target skill.

3 / 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.