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/script-utility/shape.md
View on GitHub# Shape: script utility
A thin `SKILL.md` over a script that does the work. The conversation has reached it when the job is deterministic, success is checkable, and code beats a model doing it by hand.
## Files
| File | From |
|---|---|
| `SKILL.md` | `assets/SKILL-template.md` |
| `scripts/<name>.py` | `assets/script-template.py` |
| `scripts/tests/test_<name>.py` | `assets/test-template.py` |
| `bmod.toml` | `init_skill.py --bmod <record> --source <update_source>` when the skill joins a module; `ship.md` adds its dependency lists; a skill outside BMad has none |
## Rules
- `SKILL.md` says what the script does, the one command that runs it, how to read its output, and what to do when it fails. Nothing the script's `--help` already says.
- The call form is `uv run {skill-root}/scripts/<name>.py ...`.
- When other skills must call the script, add `scripts = ["scripts/<name>.py"]` under `[skill]` in `bmod.toml`, which installs it to `_bmad/scripts/`; it is then called as `uv run {project-root}/_bmad/scripts/<name>.py ...`.
- The script carries a PEP 723 header with `requires-python = ">=3.11"` and uses argparse.
- It prints one JSON object with stable keys when a model reads the result, plain text when a person does.
- On failure it exits non-zero with a one-line reason on stderr, so the agent reports instead of guessing.
- It makes no network calls and bakes in no model ids.
- Judgment stays out of the script: when a result needs interpreting, `SKILL.md` says what each outcome asks the agent to do next.
- The test uses `unittest`, runs the script as a subprocess on a fixture built in a temp directory, and covers the success path and the one-line failure.
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: 471k | 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 |