CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

bmod-core-tools

Required bmod metadata. Never invoke this skill.

Quality

67%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/bmod-core-tools/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

92%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 minimal redirect stub: lean, concrete, and complete for its single purpose of routing to the bmad skill with a fully specified fallback. Its only weakness is minor unspecified follow-up behavior after the fallback offer, which barely affects its otherwise fully actionable guidance.

DimensionReasoningScore

Conciseness

Three sentences, ~60 words, no padding and no explanation of concepts Claude already knows: "This folder is the BMad Core Tools module's record, not something to run. Invoke the `bmad` skill with `setup core-tools`; ... If there is no `bmad` skill, say so and offer `npx skills add ...`" — every clause carries distinct, necessary information.

5 / 5

Actionability

The guidance is mostly executable: a specific skill invocation with argument ("Invoke the `bmad` skill with `setup core-tools`") and a verbatim copy-paste install command ("npx skills add bmad-code-org/BMAD-METHOD --skill bmad") covering both the present and missing-skill cases. Minor gaps keep it at 4 rather than 5: it does not say what to do after the state report or if the user declines the offered install.

4 / 5

Workflow Clarity

For a single-purpose stub, the action is unambiguous with a clearly specified primary path and fallback branch ("Invoke the `bmad` skill with `setup core-tools`; ... If there is no `bmad` skill, say so and offer ..."). No destructive or batch operations are involved, so the simple-skill exception applies and no validation checkpoint is required.

5 / 5

Progressive Disclosure

The skill is under 50 lines, has no bundle files (no references/, scripts/, or assets/ directories exist), and needs no external references; the single paragraph is appropriately sized with nothing that belongs in a separate file. Per the rubric's simple-skill guidance, this warrants the top score.

5 / 5

Total

19

/

20

Passed

Description

25%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 functions as a do-not-invoke marker rather than a capability description: it conveys the stub's non-runnable nature well but offers no functional 'what', no 'when', and no natural trigger terms. Conflict risk is low only because invocation is explicitly forbidden, not because the skill is well-delineated.

Suggestions

State what the record actually contains or does, e.g. "Holds the BMad Core Tools module record; the bmad skill reads it during `setup core-tools`" — this would lift specificity and completeness.

Add a when-to-read clause (e.g. "Read only when asked to set up or check BMad core-tools state") so at least an explicit trigger condition exists, raising completeness above the vague-what/no-when anchor.

Include natural findable terms such as "BMad core-tools", "module setup", or "setup core-tools" so users and Claude can locate it by keyword, improving trigger term quality.

DimensionReasoningScore

Specificity

"Required bmod metadata" names a domain but lists zero concrete capabilities — the only directive is "Never invoke this skill", which describes no action the skill performs. It is not pure abstract fluff (score 1) since it identifies the artifact's role, but it never reaches the '1-2 concrete actions' bar of score 3.

2 / 5

Completeness

The 'what' is vague (identifies the artifact as metadata but states no function) and the 'when' is entirely absent — there is no 'Use when...' clause or equivalent, only an explicit never-invoke directive. This fits 'has a vague what and no when'; it cannot reach 3 because anchor 3 requires a clear functional 'what'.

2 / 5

Trigger Term Quality

No natural keywords a user would ever say appear; "Required bmod metadata" is internal jargon and "Never invoke this skill" is an anti-trigger, not a search term. This matches the 'no natural keywords; only technical jargon' anchor.

1 / 5

Distinctiveness Conflict Risk

"Never invoke this skill" explicitly suppresses triggering, so the risk of firing for the wrong skill is minimal. It falls short of anchor 5 because there is no clear niche with distinct positive triggers — conflict avoidance rests solely on the anti-invoke directive.

4 / 5

Total

9

/

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-core-tools/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.