bmad-market-research

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

Quality

67%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

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

Quality

Content

85%

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, actionable forwarding shim with a clear activation sequence and explicit handoff boundary. Its main weakness is mild verbosity from restating the target skill's full surface in both the intro and step 2.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean for a shim, but the intro and step 2 each enumerate bmad-deep-recon's full surface (research types, draft/process/run modes, verification levels, briefing, handoffs), which could be tightened.	2 / 3
Actionability	It provides an executable command (`uv run {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --key workflow`) and concrete handoff parameters (research type `market`, skip type inference, the four legacy fields, verbatim input).	3 / 3
Workflow Clarity	A clear three-step activation sequence (resolve customization, emit deprecation notice, invoke bmad-deep-recon) with an explicit stop boundary: 'do not execute any further steps in this shim.'	3 / 3
Progressive Disclosure	A short, self-contained shim well under 50 lines with well-organized sections (deprecation notice plus numbered activation steps) and no need for external bundle references.	3 / 3
	Total	11 / 12 Passed

Description

50%

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 clearly signals deprecation and the forwarding target, but it functions as a dispatch notice rather than a capability description: it lacks explicit trigger guidance and natural user keywords. Scores cluster at 2 because the 'when to use' dimension is entirely absent.

Suggestions

Add an explicit trigger clause, e.g. 'Use when existing invocations or bmad-market-research.toml overrides reference the legacy market-research skill.'

Surface natural user keywords such as 'market research' or 'competitive analysis' so the description reads as a capability rather than only a deprecation notice.

Briefly state the underlying capability (e.g. 'Conducts market-type deep research') before noting it forwards to bmad-deep-recon.

Dimension	Reasoning	Score
Specificity	It names a concrete action ('forwards') and a specific target skill, but offers only a single action rather than the multiple specific actions the anchor for 3 requires.	2 / 3
Completeness	It states what the skill does ('forwards to bmad-deep-recon (market type)') but provides no 'Use when...' clause or explicit trigger guidance, which caps completeness at 2 per the rubric guidelines.	2 / 3
Trigger Term Quality	It contains one relevant keyword ('market') a user might say, but lacks common variations like 'market research' or 'competitive analysis' and is dominated by deprecation jargon ('forwards to bmad-deep-recon (market type)').	2 / 3
Distinctiveness Conflict Risk	It names a specific target skill and market type, giving it a niche, but as a forwarding shim it intentionally overlaps with bmad-deep-recon.	2 / 3
	Total	8 / 12 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: bmad-code-org/BMAD-METHOD
Path: src/bmm-skills/v6-shims/bmad-market-research/SKILL.md
Commit: bb45db4

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.