CtrlK
BlogDocsLog inGet started
Tessl Logo

bmad-domain-research

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

50

Quality

55%

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

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, highly actionable deprecation shim with a concrete activation command and an explicit handoff checkpoint. Its only weakness is mild verbosity in the intro's enumeration of the successor's capabilities.

DimensionReasoningScore

Conciseness

The body is mostly efficient with a clear numbered activation list, but the intro paragraph enumerates bmad-deep-recon's full capability surface and migration detail that is unnecessary context for a thin shim, so it is not fully lean.

2 / 3

Actionability

It gives a concrete executable command ("uv run {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --key workflow"), named override files, and explicit invocation parameters for bmad-deep-recon, which is copy-paste ready.

3 / 3

Workflow Clarity

The three-step activation sequence is clearly ordered and terminates with an explicit handoff checkpoint ("bmad-deep-recon takes the workflow from here — do not execute any further steps in this shim"), appropriate for a non-destructive forwarder.

3 / 3

Progressive Disclosure

The skill is under 50 lines with no external references needed and is organized into a labeled intro plus a numbered "On Activation" section, meeting the simple-skill bar for full marks.

3 / 3

Total

11

/

12

Passed

Description

25%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

As a deprecation shim the description is accurate and honest, but it functions as a redirect notice rather than a capability/trigger statement, scoring low on specificity and trigger terms. It is distinguishable but offers no user-facing trigger guidance.

Suggestions

Add a brief "Use when..." clause stating when this legacy name is still invoked (e.g., existing invocations or bmad-domain-research.toml override files) so completeness is not capped at 2.

Include a natural-language trigger term such as "domain research" so users have a keyword they would actually say, raising trigger_term_quality above the jargon-only anchor.

Optionally name one concrete action the shim performs (forwarding with a pre-resolved domain type) to lift specificity out of the no-actions anchor.

DimensionReasoningScore

Specificity

The description ("Deprecated — forwards to bmad-deep-recon (domain type)") states no concrete capabilities of the skill itself; it only describes a redirect, matching the vague/no-actions anchor rather than the named-actions anchor.

1 / 3

Completeness

It states what the skill does (forwards to bmad-deep-recon with the domain type) but provides no "Use when..." trigger guidance, so it is capped at 2 per the missing-trigger guideline.

2 / 3

Trigger Term Quality

It contains no natural keywords a user would say; "bmad-deep-recon" and "domain type" are internal technical jargon, matching the no-natural-keywords anchor.

1 / 3

Distinctiveness Conflict Risk

It names a specific target and type so conflict risk is limited, but the "bmad...research" naming overlaps with bmad-deep-recon and no distinct trigger terms separate them.

2 / 3

Total

6

/

12

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

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.