CtrlK
BlogDocsLog inGet started
Tessl Logo

bmad-build-auto

One iteration of an unattended development loop. Use when invoked by name

58

Quality

66%

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/bmad-build-auto/SKILL.md

The canonical home for this skill is bmad-build in bmad-code-org/BMAD-METHOD

SKILL.md
Quality
Evals
Security

Quality

Content

82%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, actionable delegation: one exact command with explicit conditional flag appends and well-structured success/fallback/halt branches. Its main limitation is that the substantive workflow content is deferred to a script and a stdout-printed file rather than present in the skill itself.

DimensionReasoningScore

Conciseness

The body is lean: one command plus tightly scoped conditional bullets, with no padding or explanation of concepts Claude already knows (e.g., what uv is), matching the 'lean and efficient; every token earns its place' anchor.

5 / 5

Actionability

It provides a concrete executable command with explicit flag appends for the common route/review cases and clear fallback behavior, but the {project-root}/{skill-root} placeholders require substitution before it is copy-paste ready, a minor gap that keeps it just below 5.

4 / 5

Workflow Clarity

The branching is clear: run the command, follow the printed workflow.md on success, fall back to the sibling bmad setup flow if the script is missing (a retry feedback loop), and HALT on any other failure; it stops short of 5 because validation of the actual deferred work lives outside this body.

4 / 5

Progressive Disclosure

This under-50-line delegating skill is well organized with one-level-deep references (the render script, the printed workflow.md, the sibling bmad skill) and no nested indirection; it lacks section headers, which is a minor organization gap versus a clean 5.

4 / 5

Total

17

/

20

Passed

Description

50%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 concise and clearly gated by explicit invocation, which keeps conflict risk low, but it is sparse on concrete capabilities and natural trigger phrases. It states what and when but neither is richly specified.

Suggestions

Enumerate 1-2 concrete actions the loop performs (e.g., 'plans, edits, and verifies code changes') to lift specificity.

Replace or augment 'Use when invoked by name' with natural trigger phrases a user would actually say (e.g., 'Use when the user asks to run an unattended build/development iteration').

Add a synonym or two for 'development loop' so the trigger term coverage reaches common phrasings.

DimensionReasoningScore

Specificity

The phrase "One iteration of an unattended development loop" names the domain but lists no concrete actions, matching the anchor 'Names the domain but actions are minimal or generic'; it is not a 1 because a domain is named, and not a 3 because no specific actions are enumerated.

2 / 5

Completeness

Both a 'what' ("One iteration of an unattended development loop") and an explicit 'Use when...' clause are present, but the trigger guidance is generic and could be more specific, matching the 'both present, when could be more explicit' anchor rather than a fully concrete 5.

4 / 5

Trigger Term Quality

"Use when invoked by name" is a meta-trigger rather than a natural phrase a user would say when they need the skill, and "development loop" is only a single generic keyword; missing common natural variations keeps it below 3.

2 / 5

Distinctiveness Conflict Risk

By-name invocation gating makes accidental triggering unlikely and the domain is niche, but "development loop" still overlaps loosely with general development skills, so it does not reach the minimal-conflict 5.

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

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.