bmad-domain-research

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

Quality

48%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./src/bmm-skills/v6-shims/bmad-domain-research/SKILL.md

Quality

Content

75%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 content is a well-structured, lean forwarding shim with concrete executable steps and a clear termination checkpoint. Its only real weakness is mild over-explanation of the target skill's capabilities and inline reference (rather than enumeration) of the legacy fields.

Dimension	Reasoning	Score
Conciseness	The body is lean — a short deprecation note plus a 3-step activation list — with only the promotional sentence enumerating bmad-deep-recon's full surface being mildly over-explanatory for a shim; this matches the level-4 'efficient, minor instances of over-explanation' anchor rather than level 5.	4 / 5
Actionability	It gives an exact executable command ('uv run .../resolve_customization.py --skill ... --key workflow') and concrete handoff instructions (research type 'domain', pass the four legacy fields, user input verbatim), matching level-4 'mostly executable guidance with minor gaps' since the four legacy field names are referenced rather than enumerated inline.	4 / 5
Workflow Clarity	A clear numbered 3-step sequence with an explicit termination checkpoint ('do not execute any further steps in this shim') matches the level-4 anchor; it is a non-destructive forwarding shim so no validation feedback loop is required, keeping it below level 5 only because there is no error-recovery checkpoint.	4 / 5
Progressive Disclosure	This is a short (<20 line), single-file skill with well-organized sections and appropriately one-level references to the target skill and external scripts; no bundle files exist to verify, matching the level-4 'good structure, well-signaled references' anchor.	4 / 5
	Total	16 / 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 honest deprecation/forwarding label rather than a capability statement, so it lacks natural trigger terms and explicit 'when to use' guidance. It is specific about its one action (forwarding) but minimal as a discoverable skill description.

Suggestions

Add a natural 'Use when...' clause naming the actual user need (e.g. 'Use when you need deep domain research') so the deprecated shim still triggers on real requests.

Include the core capability verbs (drafts, processes, runs deep-research reports) rather than only the forwarding action, to give users concrete terms to say.

Add common synonyms/file extensions a user might mention (domain research, market/competitive research, .toml overrides) to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Quotes 'forwards to bmad-deep-recon (domain type)' — it names the domain and a single concrete action (forwarding), which is minimal; not the level-3 anchor that expects 1-2 concrete capability actions, and clearly above the level-1 vague anchor.	2 / 5
Completeness	It gives a vague 'what' (forwards to bmad-deep-recon with the domain type) but no 'when'/trigger guidance, matching the level-2 anchor; the missing 'Use when...' clause would cap it at 3, but here the 'what' is itself minimal so it sits at 2.	2 / 5
Trigger Term Quality	Terms like 'Deprecated', 'forwards', 'bmad-deep-recon', and 'domain type' are internal/technical jargon; a user needing domain research would not naturally say any of these, matching the level-1 anchor of only technical jargon with no natural keywords.	1 / 5
Distinctiveness Conflict Risk	It is tied to a specific niche (domain-type research forwarding) but as a deprecated shim it overlaps heavily with the sibling bmad-deep-recon and other research-type skills, matching the level-3 'somewhat specific but could still overlap' anchor.	3 / 5
	Total	8 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

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

Reviewed: 15 days 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.