CtrlK
BlogDocsLog inGet started
Tessl Logo

bmad-technical-research

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

47

Quality

50%

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-technical-research/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%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 tight, well-structured deprecation shim: a clear 3-step activation workflow with a concrete resolve command and an explicit hand-off terminator. Its only weakness is an over-described introductory paragraph that enumerates the target skill's full surface unnecessarily.

Suggestions

Trim the introductory paragraph to one sentence; the enumerated modes and research types of bmad-deep-recon belong in that skill, not this shim.

Optionally state the expected outcome of the resolve_customization command (e.g. 'emits the four legacy field values') so the hand-off data contract is explicit.

DimensionReasoningScore

Conciseness

The body is mostly efficient, but the introductory paragraph padding the full capability surface of bmad-deep-recon ('drafts deep-research prompts... across market, domain, technical, competitive, user-voice, and academic-lit types') is unnecessary detail for a forwarding shim.

3 / 5

Actionability

It provides a concrete, copy-paste-ready resolve_customization command and explicit hand-off instructions, with only the final 'Invoke bmad-deep-recon with...' being descriptive rather than a literal command.

4 / 5

Workflow Clarity

Three steps are clearly sequenced with an explicit terminator ('do not execute any further steps in this shim'), but there are no validation checkpoints; this is acceptable for a non-destructive handoff yet keeps it below a 5.

4 / 5

Progressive Disclosure

The skill is well under 50 lines, has no bundle files, and is organized into a heading plus a numbered activation list, satisfying the simple-skill exception for a top score.

5 / 5

Total

16

/

20

Passed

Description

28%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 reads as a deprecation label rather than a capability statement: it states it forwards to bmad-deep-recon but describes no concrete actions and gives no usage trigger. It is identifiable but thin on what/when.

Suggestions

Add a 'Use when...' clause stating when Claude should select this skill (e.g. legacy invocations of bmad-technical-research or technical-type research requests).

Replace 'forwards to' with a concrete statement of what the shim does on activation, e.g. 'Compatibility shim that resolves legacy bmad-technical-research invocations and delegates to bmad-deep-recon with the technical research type.'

Include a natural trigger term such as 'technical research' so users phrasing a request verbally can match it.

DimensionReasoningScore

Specificity

The description only names the domain ('technical type') and a single generic action ('forwards to bmad-deep-recon'), with no concrete capabilities of the skill itself, matching the 'names domain but actions are minimal' anchor.

2 / 5

Completeness

It gives a vague 'what' (a forwarding shim) and entirely omits any 'when'/'Use when' trigger guidance, matching the 'vague what and no when' anchor.

2 / 5

Trigger Term Quality

Only 'technical' functions as a weak keyword; the rest ('Deprecated', 'forwards', 'bmad-deep-recon') is technical jargon a user would not naturally say when needing the skill.

2 / 5

Distinctiveness Conflict Risk

It is somewhat specific to the bmad ecosystem but, being a forwarder to bmad-deep-recon for the technical type, it materially overlaps with that sibling skill on the same trigger.

3 / 5

Total

9

/

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.