m3taz-ahmed/aizee / skills/bmad-toolsmith
bmad-toolsmith
VerifiedSmithy 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`).
shapes/rendered-agent/shape.md
View on GitHub# Shape: rendered agent
A persona with a menu whose capabilities are rendered sources, so a team changes a rule inside a capability without forking.
Reach it when the user wants someone to talk to who does several related things, and teams must change what those things do, not only add facts. A persona whose capabilities ship as they are: `shapes/agent/shape.md`. Must remember between sessions: `shapes/memory-agent/shape.md`, which stays on the resolver bootloader.
The model is `bmad-build`'s form with the agent shape's content.
## Files
| File | From | Holds |
|---|---|---|
| `SKILL.md` | `assets/SKILL-template.md` | description, the render command, the invocation words mapped to `--set` |
| `workflow.md` | `assets/workflow.md` | the activation from `{{ agent.* }}`: persona, facts, dispatch |
| `references/<capability>.md` | `assets/capability.md` | one internal capability each |
| `customize.toml` | `assets/customize-template.toml` | `[agent]` as the agent shape has it; `[workflow]`: every customization point |
Build-time tokens: `{skill}` (folder name), `{name}`, `{title}`, `{icon}`, `{description}`, the persona and menu fields; `{project-root}` and `{skill-root}` are runtime.
The agent shape's Capabilities, Persona and Roster sections hold, except that the persona paragraph, the activation and "How <Name> works" live in `workflow.md` and there are no numbered activation steps.
## Rules
- `SKILL.md` only runs `uv run --no-cache "{project-root}/_bmad/scripts/render_skill.py" --project-root "{project-root}" --skill "{skill-root}"`, maps the words of the invocation to `--set workflow.<key>=<value>`, follows the printed `workflow.md`, and halts on any failure. It holds no Jinja, because the renderer excludes it.
- Jinja (`{{ agent.key }}`, `{{ workflow.key }}`, `{% if %}`, `rendered("references/<capability>.md")`) lives only in `workflow.md` and the capabilities. `agent` is the `[agent]` table and `workflow` the `[workflow]` table, both through the same layers.
- An agent-facing `{{placeholder}}` sits inside `{% raw %}...{% endraw %}`; a single-brace `{placeholder}` passes through untouched.
- The agent's documents go under `{{ initiative_folder }}`.
- A customization value the templates cannot act on, such as a misspelled selector, is rejected at the top of `workflow.md` with `{{ halt("...") }}`, one guard per selector.
- A capability item's prompt is `Read `{skill-root}/references/<capability>.md` fully and follow it.`, as the agent shape has it; the renderer binds `{skill-root}` in a customization value to the generation, so the path is the rendered capability. A capability that hands to another file names it as `{{ rendered("references/<file>.md") }}`.
- Dispatch shows no menu: a request that names its intent runs the matching item, a request that fits nothing is a conversation, and asked what it does the agent answers in a sentence or two from the menu in its own voice. Codes stay valid shortcuts.
- A customization point is a `[workflow]` key inserted with `{{ workflow.<key> }}` at the one spot where it acts, named `<capability>_<point>`.
- Every point is declared before any team asks: a before and after instruction per capability, each selector, each instruction block a team would replace whole. A key no source inserts is not declared.
- An instruction a team may replace whole is a `"""` block scalar, a selector is a scalar with its allowed values in the comment above it, and halts on any other value, and an empty default renders nothing. Every key's comment says where it lands.
- `activation_steps_prepend`, `activation_steps_append` and `persistent_facts` stay in `[agent]`; `[workflow]` holds only the capability points.
- Teams override in `{project-root}/_bmad/custom/<name>.toml` or `<name>.user.toml`; a single run overrides with `--set`.
- No file whose name contains `template` carries `{{ config.* }}`, `{{ workflow.* }}` or `{{ agent.* }}`.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |