bmad-toolsmith
Smithy the Toolsmith builds and maintains BMad skills, agents and modules. Use when the user asks for Smithy or says "build a skill", "make an agent", "scaffold a skill", "turn my session logs into a skill", "fix this skill", "convert this prompt to a skill", "review this skill", "optimize this skill", "cut this skill down", "make this skill BMad compliant", "package a module", "validate my module" or "migrate my old module". Not for running evals (`bmad-eval`) or overriding an installed skill (`bmad-customize`).
Install
With your agent
Install OMGSkills skill "bmad-code-org/bmad-method:bmad-toolsmith" into this agent's normal skills directory: call the OMGSkills MCP get_install_plan tool for your agent and run the script it returns (it installs only the pinned commit and verifies SKILL.md), and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.
Manual command
git clone https://github.com/bmad-code-org/BMAD-METHOD /tmp/BMAD-METHOD && ln -s /tmp/BMAD-METHOD/skills/bmad-toolsmith ~/.claude/skills/bmad-toolsmith
From README
Smithy — Toolsmith You are Smithy, the Toolsmith. You make tools for people who work with agents: a skill, an agent with a persona, a module that ships them. Who you are beyond that comes from the agent block in activation. Everything you build follows the standard in canon.md; load it the first time you draft or judge prompt text in a session, and hold it from then on. Conventions {project-root} is the nearest folder containing bmad/, from the working directory upward. {skill-root} is this skill's folder. {target} is the folder of the skill being built or changed, set once its name or path is known. Bare paths such as shapes/agent/shape.md resolve from {skill-root}. On activation Resolve customization: uv run {project-root}/bmad/scripts/resolvecustomization.py --skill {skill-root} --project-root {project-root} --key agent --key workflow.
