CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

bmod-toolsmith

Required bmod metadata. Never invoke this skill.

Quality

70%

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-toolsmith/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 a model minimal redirect: it declares what the folder is, gives an exact invocation instruction with expected behavior, and a concrete fallback command with a clear conditional. As an instruction-only skill with no risky operations, it fully satisfies conciseness, actionability, workflow clarity, and structure at this scale.

DimensionReasoningScore

Conciseness

Three sentences, every token earning its place: "This folder is the Toolsmith module's record, not something to run" (context), the redirect instruction, and the fallback. Nothing is padded or over-explained; anchor 5's "lean and efficient" fit is exact.

5 / 5

Actionability

Fully executable guidance: "Invoke the `bmad` skill with `setup toolsmith`" plus the copy-paste-ready fallback command `npx skills add bmad-code-org/BMAD-METHOD --skill bmad`. Both common cases (skill present / absent) are covered with concrete instructions, matching anchor 5.

5 / 5

Workflow Clarity

A simple single-purpose skill with one unambiguous action and an explicit conditional branch ("If there is no `bmad` skill, say so and offer..."). No destructive or batch operations, so no validation cap applies, and the simple-skill exception holds: the single action is unambiguous.

5 / 5

Progressive Disclosure

Under 50 lines with no bundle files present (references/, scripts/, assets/ all absent) and no content that belongs in a separate file — the entire body is the overview. Per the rubric's simple-skill note, this scores 5 with nothing to disclose or navigate.

5 / 5

Total

20

/

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 is deliberately anti-triggering metadata rather than a capability description: it names a niche domain but provides no actions, no natural trigger terms, and explicitly negates invocation. While this makes conflict risk low, it fails as discovery metadata — a user (or Claude) scanning descriptions gets no signal about what the skill covers or when to use it.

Suggestions

State what the record actually contains as concrete actions, e.g. "Records the Toolsmith module's bmod setup state for the BMAD method" — this gives the "what" without adding fluff.

Add explicit trigger guidance even for a never-invoke skill, e.g. "Do not invoke; if asked about Toolsmith module status, redirect to the `bmad` skill with `setup toolsmith`" — currently there is no Use-when clause or equivalent, capping completeness at 3 by the rubric guidelines.

Include the natural terms users would actually say (e.g. "toolsmith", "bmad setup", "module state") so the record is at least findable and distinguishable from the parent `bmad` skill.

DimensionReasoningScore

Specificity

Names the domain ("Required bmod metadata") but states no concrete actions; the only behavioral statement is the negative "Never invoke this skill". Not anchor 1 because the domain is named rather than pure abstract language; not anchor 3 because there are no concrete actions at all.

2 / 5

Completeness

Has only a vague "what" ("Required bmod metadata" says what the file is, not what it does) and no "when" — the when is explicitly negated by "Never invoke this skill". Anchor 3 requires a clear "what", which this lacks, so anchor 2 is the best fit.

2 / 5

Trigger Term Quality

"bmod metadata" is technical jargon no user would naturally say, and the description contains no natural or even generic keywords. Anchor 2 requires at least one or two generic keywords, which are absent, so this matches anchor 1.

1 / 5

Distinctiveness Conflict Risk

"Required bmod metadata" carves a clear niche and the explicit "Never invoke this skill" instruction minimizes mis-triggering, but a user mentioning bmod/bmad metadata could still match this instead of the closely related bmad skill. Anchor 5 requires distinct positive triggers, which are absent, so anchor 4 (minor overlap with closely related skills) fits best.

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-toolsmith/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.