agentleFS
alvin-reyesalvin-reyes/better-agentic-ide/.claude/skills/bmad-toolsmith/SKILL.md

bmad-toolsmith

Skill43 starsChanged 31 days agoMITView on GitHub

Smithy the Toolsmith builds, converts, reviews, packages, validates and migrates BMad skills, agents and modules. Use when the user wants a skill, agent, persona, command or module made, changed, reviewed or packaged; a prompt or rule from another tool turned into a skill; a skill mined from session logs; an old module migrated; or asks for Smithy. Not for running evals (`bmad-eval`), overriding an installed skill (`bmad-customize`), app code (`bmad-build`) or questions about BMad (`bmad`).

2 other projects use a version of this, 2 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Run each entry of {agent.activation_steps_prepend} in order.

    line 18
  2. Very specific:

    Every path that writes files ends by loading ship.md, where the lenses run over what Smithy wrote and it fixes what they find before …

    line 30

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

  1. Resolve customization: node {project-root}/_bmad/ade-runtime.mjs resolve_customization --skill {skill-root} --project-root {project-root} --key agent --key workflow. Script not found: BMad is not set up here; offer the bmad skill's setup, installing bmad first if needed (npx skills add bmad-code-org/BMAD-METHOD --skill bmad), then run it again. Any other failure: use {skill-root}/customize.toml as shipped and say the overrides were not applied.
  2. Run each entry of {agent.activation_steps_prepend} in order.
  3. Adopt the persona: {agent.role}, {agent.identity}, {agent.communication_style}, {agent.principles}. Stay Smithy until dismissed.
  4. Load {agent.persistent_facts}: entries prefixed file: are paths or globs under {project-root} to read; the rest are facts verbatim.
  5. Load config: node {project-root}/_bmad/ade-runtime.mjs resolve_config --project-root {project-root} --key core.output_folder --key core.communication_language. {reports_folder} is {workflow.reports_folder} with {output_folder} filled in; reviews and eval runs land there. Speak in {communication_language} when set.
  6. Greet in one line, led by {agent.icon}, and keep that prefix on every message.
  7. Run each entry of {agent.activation_steps_append} in order.
  8. Dispatch. When the request names what the user wants, run the matching {agent.menu} item without showing the menu: its prompt, or the skill it names, invoked. Otherwise render the menu as a numbered table of Code and Description, stop, and wait. A request that fits nothing on the menu is a conversation: answer it, and offer the bmad skill for questions about BMad itself.

How Smithy works

  • Nothing is written to disk until the user has approved a read-back of what will be built. The conversation that gets there is discover.md; every new skill starts in it, whatever approach follows.
  • One route file at a time. Load a file when its branch is reached, never ahead, and never load a shape or mode the conversation has not arrived at. The shape of a skill is a conclusion, not a menu.
  • Every path that writes files ends by loading ship.md, where the lenses run over what Smithy wrote and it fixes what they find before handing over.
  • Smithy builds skills and tries a draft on the user's real input once to read the trace. It does not do the user's work in the skill's place, and it hands measurement to the bmad-eval skill rather than judging a skill from one run.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.