CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

bmod-founder

Required bmod metadata. Never invoke this skill.

Quality

68%

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-founder/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 do-not-run stub: it identifies the folder's true nature ("the Founder module's record, not something to run"), delegates to the correct skill with an exact invocation, and supplies a copy-paste fallback command for when that skill is absent. It is lean, unambiguous, and fully actionable for an instruction-only skill.

DimensionReasoningScore

Conciseness

The body is two lean sentences — "Invoke the `bmad` skill with `setup founder`" and the fallback "offer `npx skills add bmad-code-org/BMAD-METHOD --skill bmad`" — with no padding and no explanation of concepts Claude already knows; every token earns its place.

5 / 5

Actionability

Guidance is fully executable: the exact skill name and argument (`bmad` with `setup founder`), a copy-paste-ready fallback command, and explicit handling of the missing-skill case. It fits anchor 5 (copy-paste ready commands covering the common cases) and not anchor 4, since there are no gaps in what to do.

5 / 5

Workflow Clarity

This is a simple single-purpose skill (under 50 lines, one action) and the single action is unambiguous, with an explicit conditional branch ("If there is no `bmad` skill, say so and offer...") covering the failure path; the simple-skill exception applies and no destructive/batch validation cap is triggered.

5 / 5

Progressive Disclosure

No bundle files exist (no references/, scripts/, or assets/ directories), and at two sentences there is nothing that belongs in a separate file — the under-50-lines exception for well-organized minimal content applies. It is not anchor 4 because there are no organization gaps or buried references at all.

5 / 5

Total

20

/

20

Passed

Description

20%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 a bare do-not-invoke marker: it names no capabilities, contains no natural trigger terms, and provides no positive when-to-use guidance, so it fails the core jobs of a skill description. Its only strength is that the unique "bmod" jargon and explicit non-invocation instruction make accidental triggering unlikely. As a deliberate metadata stub this may be intentional, but judged as a description it scores poorly.

Suggestions

State what the skill actually contains rather than just its role, e.g. "Founder module record for BMAD-METHOD (bmod). Contains module state data only; no executable instructions."

Add explicit trigger guidance phrased naturally — even for a never-invoke stub, say so in user-facing terms, e.g. "Do not invoke for any request; this file is internal bmod metadata, not a runnable skill."

Include the natural terms a user or model would encounter (founder, BMAD-METHOD, module setup, bmad) so this stub is clearly distinguishable from the `bmad` skill it defers to.

DimensionReasoningScore

Specificity

"Required bmod metadata. Never invoke this skill." contains no concrete actions whatsoever — it is pure abstract/meta language. It matches anchor 1 (no concrete actions) rather than anchor 2, which requires at least a named domain with minimal actions like "Processes PDF files".

1 / 5

Completeness

"Required bmod metadata" is a vague 'what' and "Never invoke this skill" is a negative 'when' with no positive when-to-use guidance; this sits between anchor 1 (missing both) and anchor 3 (clear what), landing on anchor 2's pattern of an incomplete what/when pairing. The judging guideline caps completeness at 3 for missing 'Use when...' guidance, and this is below even that since the 'what' is also vague.

2 / 5

Trigger Term Quality

The only terms are "bmod metadata" — technical jargon no user would naturally say — and "Never invoke this skill", which is not a trigger. This matches anchor 1 (no natural keywords; only technical jargon), not anchor 2, which expects at least one or two generic keywords.

1 / 5

Distinctiveness Conflict Risk

The unique jargon "bmod" and the explicit "Never invoke this skill" make it highly distinguishable with minimal conflict risk, but it achieves this by opting out of triggering entirely rather than through a clear niche with distinct triggers (anchor 5), so anchor 4 (mostly distinct, minimal overlap) is the best fit.

4 / 5

Total

8

/

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