Summary
On fresh install (reproduced on macOS, Windows, and Linux), the installer prints:
Error: SKILL.md name "{setup-skill-name}" does not match directory name "setup-skill-template" — skipping
The consequence is that the rest of the agent set (CIS pack: brainstorming-coach, creative-problem-solver, design-thinking-coach, innovation-strategist, presentation-master, storyteller; plus bmad-tea) never gets registered in _bmad/_config/agent-manifest.csv, leaving them inactive / un-configured even though their skill files land correctly under .claude/skills/.
Root Cause
The validator is reading skills/bmad-module-builder/assets/setup-skill-template/SKILL.md (from the bmad-builder / bmb module), which is a template scaffold containing unrendered placeholders:
---
name: "{setup-skill-name}"
description: Sets up {module-name} module in a project. ...
---
Because the template hasn't been rendered with real values yet, the name field does not match the parent directory name (setup-skill-template). The validator treats this as a fatal mismatch and skips the rest of the tree — including entries that should be added to the manifest.
Expected
Validation should either:
- Exclude
assets/** directories (template scaffolds are not runnable skills), or
- Treat the mismatch as a non-fatal warning so downstream agents still register, or
- Rename the template directory/file so the placeholder scan never runs against it.
Reproduction
- Fresh install of BMad Method (reproduced on macOS, Windows 11, Ubuntu).
- Observe the error during setup.
- Inspect
_bmad/_config/agent-manifest.csv — only the bmm agents are present; cis/* and tea are missing.
- Confirm the skill files do exist under
.claude/skills/bmad-cis-* and .claude/skills/bmad-tea/, so the skills themselves installed fine — only the manifest registration is broken.
Workaround
Manually copy a known-good agent-manifest.csv from another project into _bmad/_config/.
Environment
- BMad core: v6.3.0
- bmad-builder (bmb) module: v1.6.0
- OS: macOS, Windows, Linux (all reproduce)
Note
Filing here rather than on bmad-code-org/bmad-builder since the failure blocks cross-module manifest registration during core install. Happy to move if you prefer.
Summary
On fresh install (reproduced on macOS, Windows, and Linux), the installer prints:
The consequence is that the rest of the agent set (CIS pack: brainstorming-coach, creative-problem-solver, design-thinking-coach, innovation-strategist, presentation-master, storyteller; plus
bmad-tea) never gets registered in_bmad/_config/agent-manifest.csv, leaving them inactive / un-configured even though their skill files land correctly under.claude/skills/.Root Cause
The validator is reading
skills/bmad-module-builder/assets/setup-skill-template/SKILL.md(from thebmad-builder/bmbmodule), which is a template scaffold containing unrendered placeholders:Because the template hasn't been rendered with real values yet, the
namefield does not match the parent directory name (setup-skill-template). The validator treats this as a fatal mismatch and skips the rest of the tree — including entries that should be added to the manifest.Expected
Validation should either:
assets/**directories (template scaffolds are not runnable skills), orReproduction
_bmad/_config/agent-manifest.csv— only thebmmagents are present;cis/*andteaare missing..claude/skills/bmad-cis-*and.claude/skills/bmad-tea/, so the skills themselves installed fine — only the manifest registration is broken.Workaround
Manually copy a known-good
agent-manifest.csvfrom another project into_bmad/_config/.Environment
Note
Filing here rather than on
bmad-code-org/bmad-buildersince the failure blocks cross-module manifest registration during core install. Happy to move if you prefer.