CtrlK
BlogDocsLog inGet started
Tessl Logo

bmad-domain-research

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

53

Quality

60%

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-domain-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 shim body is concise, actionable, and clearly sequenced, with concrete commands and an explicit handoff to the consolidated skill. It is well-structured for a short single-purpose skill and makes the deprecation migration path explicit.

DimensionReasoningScore

Conciseness

The body is lean, assumes Claude's competence, and avoids explaining concepts Claude already knows; the only slight padding is the somewhat long deprecation notice in step 2, keeping it just below the 'every token earns its place' bar.

4 / 5

Actionability

It provides a concrete, copy-pasteable command (the resolve_customization.py invocation) and an explicit handoff instruction with parameters, with only minor gaps such as the exact bmad-deep-recon invocation syntax.

4 / 5

Workflow Clarity

Three steps are clearly sequenced with an explicit stop condition ("do not execute any further steps in this shim"); it lacks a validation checkpoint but the forwarding operation is non-destructive, so no cap applies and it sits just below the explicit-feedback-loop anchor.

4 / 5

Progressive Disclosure

Under 50 lines with no external references needed, organized into a clear overview and an On Activation section, qualifying for the simple-skill exception that allows a 5 on well-organized structure alone.

5 / 5

Total

17

/

20

Passed

Description

42%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 clearly communicates the skill is a deprecated forwarding shim but omits any explicit "when to use" guidance and relies on a skill name rather than natural user triggers. It is readable and honest but leaves the activation conditions implicit.

Suggestions

Add a concise 'Use when...' clause stating the conditions that should trigger this skill, even for a deprecated shim (e.g., legacy invocations by name or existing bmad-domain-research.toml overrides).

Include natural trigger terms users might actually say, or explicitly state that new work should invoke bmad-deep-recon directly so the description self-disambiguates from the consolidated skill.

DimensionReasoningScore

Specificity

Names the domain and one concrete action ("forwards to bmad-deep-recon (domain type)") but lists no further capabilities, matching the anchor for a domain plus 1-2 concrete actions that is not comprehensive.

3 / 5

Completeness

It states a clear "what" (a deprecated shim that forwards to bmad-deep-recon) but never gives a "when"/Use-when clause, so per the guidelines completeness is capped at 3 for a missing trigger clause.

3 / 5

Trigger Term Quality

It references the target skill name "bmad-deep-recon" rather than natural trigger phrases a user would say, with only one or two generic keywords and no common variations or synonyms.

2 / 5

Distinctiveness Conflict Risk

It targets a specific named skill and research type, giving it a recognizable niche, but as a shim it overlaps heavily with bmad-deep-recon and could still be triggered where the consolidated skill should be used directly.

3 / 5

Total

11

/

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.