CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

bmod-method

Required bmod metadata. Never invoke this skill.

Quality

78%

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 ./skills/bmod-method/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

100%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 an exemplary short instruction skill: it identifies what the folder is, gives one unambiguous action with its expected result in both setup and already-installed states, and supplies a complete fallback command for the missing-skill case. No padding, no missing steps, no references needed.

DimensionReasoningScore

Conciseness

Three sentences, every one load-bearing: "This folder is the BMad Method module's record, not something to run" (what this is), "Invoke the `bmad` skill with `setup method`..." (the action and its expected outcomes), and the fallback with a copy-paste command. No padding, no concepts Claude already knows — matches anchor 5's "every token earns its place".

5 / 5

Actionability

Fully concrete and executable: exact skill name (`bmad`), exact argument (`setup method`), expected behavior in both states ("sets the module up if it never was, and otherwise reports its state"), and a copy-paste-ready fallback command "npx skills add bmad-code-org/BMAD-METHOD --skill bmad" with its trigger condition (no `bmad` skill). Matches anchor 5; anchor 4 would require a minor gap, and none is present.

5 / 5

Workflow Clarity

This is a simple single-purpose skill under 50 lines, and the single action is unambiguous, with both branches (skill present → invoke with `setup method`; absent → say so and offer the install command) and expected outcomes for each. No destructive or batch operations, so the validation cap does not apply — the rubric's simple-skill exception gives a clear 5.

5 / 5

Progressive Disclosure

Three sentences with no external references needed and no bundle files present (no references/, scripts/, or assets/ directories exist), so there is nothing to disclose progressively. Under the rubric's under-50-line/no-references-needed rule, this self-contained structure scores 5.

5 / 5

Total

20

/

20

Passed

Description

45%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.

As a deliberate never-invoke metadata marker, the description excels at conflict avoidance and gives an explicit (negative) trigger clause, but it names no concrete capabilities and offers no natural trigger terms beyond the jargon "bmod". It cannot stand alone: the actual purpose and redirect target only become clear from the body. Lower-scoring dimensions are specificity and trigger term quality; distinctiveness is its clear strength.

Suggestions

State what the metadata is for in one clause, e.g. "Metadata record for the BMad Method module used by the `bmad` skill's `setup method` command" — this gives the 'what' a concrete referent and lifts specificity and completeness.

Align the naming with what users actually type: the description says "bmod" while the body and package use "BMad Method"/"bmad"; including "bmad"/"BMAD-METHOD" terms would improve trigger-term quality and consistency.

Keep the "Never invoke this skill" directive (it is highly effective at conflict prevention) but pair it with the redirect in the description itself, e.g. "...Never invoke; use the `bmad` skill instead", so the description is complete without the body.

DimensionReasoningScore

Specificity

"Required bmod metadata" names the domain but describes zero concrete capability actions; the only directive, "Never invoke this skill", is a usage prohibition rather than an action. It is not entirely vague abstract fluff (anchor 1) because the domain and non-invocable nature are stated unambiguously, but it falls short of anchor 3, which expects 1-2 concrete actions.

2 / 5

Completeness

The 'when' is explicitly present ("Never invoke this skill"), and the 'what' is present but vague — "Required bmod metadata" says what it is, not what the metadata is for or what the BMad Method module does. It beats anchor 2 because an explicit trigger clause exists, but does not reach anchor 4 since the 'what' cannot stand alone without the body's explanation.

3 / 5

Trigger Term Quality

The only keyword is the technical term "bmod metadata"; no natural user phrases would trigger this skill. It edges above anchor 1 because "Never invoke this skill" is an explicit, natural-language anti-trigger signal, but common trigger variations and synonyms ("bmad", "BMAD-METHOD", "setup method") are absent from the description.

2 / 5

Distinctiveness Conflict Risk

"Never invoke this skill" eliminates conflict risk about as thoroughly as possible — no other skill's triggers can capture it — and "bmod metadata" carves out a clear niche. This matches anchor 5's "clear niche with distinct triggers; minimal conflict risk" rather than anchor 4, which is reserved for descriptions that could still overlap with closely related skills.

5 / 5

Total

12

/

20

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

bmad-code-org/BMAD-METHOD

Path

skills/bmod-method/SKILL.md

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.