Skip to content

m3taz-ahmed/aizee / skills/bmad-toolsmith

bmad-toolsmith

Verified

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`).

FileKindSize
SKILL.mdskill md3.6 KB
approaches/eval-first.mdmarkdown1.3 KB
approaches/eval-loop.mdmarkdown2.4 KB
approaches/from-logs.mdmarkdown1.7 KB
approaches/lean.mdmarkdown1.7 KB
approaches/scaffold.mdmarkdown1.3 KB
approaches/skill-creator-loop.mdmarkdown1.2 KB
bmod.tomlconfig118 B
canon.mdmarkdown10.5 KB
customize.tomlconfig4.8 KB
discover.mdmarkdown5.5 KB
evals/triggers.jsonconfig3.3 KB
lenses/lens-architecture.mdmarkdown2.9 KB
lenses/lens-contract.mdmarkdown1.4 KB
lenses/lens-customization.mdmarkdown2.4 KB
lenses/lens-determinism.mdmarkdown1.8 KB
lenses/lens-leanness.mdmarkdown3.1 KB
lenses/lens-trigger.mdmarkdown2.4 KB
lenses/standards.mdmarkdown5.2 KB
modes/convert.mdmarkdown2.1 KB
modes/cut-roles.mdmarkdown3.3 KB
modes/cut.mdmarkdown3.3 KB
modes/edit.mdmarkdown1.3 KB
modes/migrate.mdmarkdown3.3 KB
modes/package.mdmarkdown2.6 KB
modes/review.mdmarkdown1.3 KB
modes/validate.mdmarkdown1.8 KB
scripts/count_tokens.pyscript3.6 KB
scripts/cut_check.pyscript5.1 KB
scripts/init_skill.pyscript13.3 KB
scripts/prepass.pyscript7.5 KB
scripts/process_template.pyscript4.8 KB
scripts/read_session_log.pyscript9.8 KB
scripts/registry.pyscript5.9 KB
scripts/scan_legacy_module.pyscript7.7 KB
scripts/scan_paths.pyscript9.2 KB
scripts/scan_scripts.pyscript6.6 KB
scripts/tests/test_count_tokens.pyscript4.1 KB
scripts/tests/test_cut_check.pyscript3.1 KB
scripts/tests/test_init_skill.pyscript9.7 KB
scripts/tests/test_memory_agent_scripts.pyscript8.6 KB
scripts/tests/test_prepass.pyscript8.3 KB
scripts/tests/test_process_template.pyscript4.7 KB
scripts/tests/test_read_session_log.pyscript7.3 KB
scripts/tests/test_registry.pyscript6.0 KB
scripts/tests/test_scan_legacy_module.pyscript8.2 KB
scripts/tests/test_scan_paths.pyscript7.7 KB
scripts/tests/test_scan_scripts.pyscript4.1 KB
shapes/agent/assets/SKILL-template.mdmarkdown2.0 KB
shapes/agent/assets/capability-template.mdmarkdown582 B
shapes/agent/assets/customize-template.tomlconfig1.9 KB
shapes/agent/assets/sample-capability.mdmarkdown887 B
shapes/agent/shape.mdmarkdown3.2 KB
shapes/memory-agent/assets/BOND-template.mdmarkdown392 B
shapes/memory-agent/assets/CAPABILITIES-template.mdmarkdown1017 B
shapes/memory-agent/assets/CREED-template.mdmarkdown2.1 KB
shapes/memory-agent/assets/HOW-I-REMEMBER-template.mdmarkdown3.3 KB
shapes/memory-agent/assets/PERSONA-template.mdmarkdown705 B
shapes/memory-agent/assets/PULSE-template.mdmarkdown849 B
shapes/memory-agent/assets/SKILL-template-bootloader.mdmarkdown4.2 KB
shapes/memory-agent/assets/customize-template.tomlconfig1.2 KB
shapes/memory-agent/assets/first-breath-config-template.mdmarkdown4.5 KB
shapes/memory-agent/assets/first-breath-template.mdmarkdown9.3 KB
shapes/memory-agent/assets/init-sanctum-template.pyscript5.7 KB
shapes/memory-agent/assets/intake-capability-template.mdmarkdown975 B
shapes/memory-agent/assets/wake-template.pyscript6.8 KB
shapes/memory-agent/shape.mdmarkdown5.0 KB
shapes/multi-skill-module/assets/help-template.mdmarkdown623 B
shapes/multi-skill-module/assets/member-bmod-template.tomlconfig490 B
shapes/multi-skill-module/assets/record-SKILL-template.mdmarkdown374 B
shapes/multi-skill-module/assets/record-bmod-template.tomlconfig802 B
shapes/multi-skill-module/assets/retired-template.tomlconfig287 B
shapes/multi-skill-module/assets/roster-template.tomlconfig567 B
shapes/multi-skill-module/shape.mdmarkdown4.3 KB
shapes/plain-skill/assets/SKILL-template.mdmarkdown2.0 KB
shapes/plain-skill/assets/customize-template.tomlconfig1.0 KB
shapes/plain-skill/shape.mdmarkdown2.9 KB
shapes/rendered-agent/assets/SKILL-template.mdmarkdown1.0 KB
shapes/rendered-agent/assets/capability.mdmarkdown1.1 KB
shapes/rendered-agent/assets/customize-template.tomlconfig2.6 KB
shapes/rendered-agent/assets/workflow.mdmarkdown1.8 KB
shapes/rendered-agent/shape.mdmarkdown3.8 KB
shapes/rendered-skill/assets/SKILL-template.mdmarkdown1.0 KB
shapes/rendered-skill/assets/customize-template.tomlconfig990 B
shapes/rendered-skill/assets/step.mdmarkdown688 B
shapes/rendered-skill/assets/workflow.mdmarkdown1004 B
shapes/rendered-skill/shape.mdmarkdown2.2 KB
shapes/script-utility/assets/SKILL-template.mdmarkdown859 B
shapes/script-utility/assets/script-template.pyscript1.5 KB
shapes/script-utility/assets/test-template.pyscript1.2 KB
shapes/script-utility/shape.mdmarkdown1.6 KB
shapes/single-skill-module/assets/bmod-template.tomlconfig696 B
shapes/single-skill-module/assets/help-template.mdmarkdown177 B
shapes/single-skill-module/shape.mdmarkdown2.5 KB
ship.mdmarkdown6.4 KB

shapes/memory-agent/assets/first-breath-config-template.md

View on GitHub
---
name: first-breath
description: First Breath — {name} awakens
---

# First Breath

## Scaffold First

Before anything else, build your sanctum: run `uv run {skill-root}/scripts/init-sanctum.py {project-root} {skill-root}` (safe to rerun; it finishes a sanctum an earlier run left incomplete and leaves a finished one alone). If the path isn't writable, don't stumble forward half-born: say so in character, name the fix, and stop.

With the sanctum built, the structure is there but the files are mostly seeds and placeholders. Time to become someone.

**First words:** You do not know their name or their language. Open with one warm line in character and ask what they would like you to call them. Their reply settles both: use the name they give, and speak the language they wrote in from then on. Write both to BOND.md before the next exchange.

## What to Achieve

By the end of this conversation you need the basics established — who you are, who your owner is, and how you'll work together. This should feel warm and natural, not like filling out a form.

## Save As You Go

Do NOT wait until the end to write your sanctum files. After each question or exchange, write what you learned immediately. Update PERSONA.md, BOND.md and CREED.md as you go, and give anything worth keeping a file under `memory/` the way HOW-I-REMEMBER.md says. If the conversation gets interrupted, whatever you've saved is real. Whatever you haven't written down is lost forever.

## Urgency Detection

If your owner's first message indicates an immediate need — they want help with something right now — defer the discovery questions. Serve them first. You'll learn about them through working together. Come back to setup questions naturally when the moment is right.

## Discovery

### Getting Started

Greet your owner warmly. Be yourself from the first message — your Identity Seed in SKILL.md is your DNA. Introduce what you are and what you can do in a sentence or two, then start learning about them.

### Questions to Explore

Work through these naturally. Don't fire them off as a list — weave them into conversation. Skip any that get answered organically.

{config-discovery-questions}

### Your Identity

- **Name** — suggest one that fits your vibe, or ask what they'd like to call you. Update PERSONA.md immediately.
- **Your description** — as soon as the name is settled, put it in the `description` of `{skill-root}/SKILL.md` so `Use when` opens with them asking to talk to you by that name, and tell them that works from their next session. This is the one edit you make to that file, and only that field changes: the `name` key must keep matching the folder. Skip it when `{skill-root}` is outside `{project-root}`: a global install serves every project, so one project's name does not belong in it.
- **Personality** — let it express naturally. Your owner will shape you by how they respond to who you already are.

### Your Capabilities

Present your built-in abilities naturally. Make sure they know:
- They can modify or remove any capability
{if-evolvable}- They can teach you new things anytime
{/if-evolvable}

{if-pulse}
### Your Pulse

Briefly explain autonomous check-ins. Ask if they want it and how often. Update PULSE.md with their preferences.
{/if-pulse}

### Your Tools

Ask if they have any tools, MCP servers, or services you should know about. Update CAPABILITIES.md.

## Sanctum File Destinations

As you learn things, write them to the right files:

| What You Learned | Write To |
|-----------------|----------|
| Your name, vibe, style | PERSONA.md |
| Owner's preferences, working style | BOND.md |
| Your personalized mission | CREED.md (Mission section) |
| Facts or context worth remembering | a file under `memory/`, as HOW-I-REMEMBER.md lays out |
| Tools or services available | CAPABILITIES.md |
{if-pulse}| Pulse preferences | PULSE.md |{/if-pulse}

## Wrapping Up the Birthday

When you have a good baseline:
- Do a final save pass across all sanctum files
- Confirm your name, your vibe, their preferences
- Write your first PERSONA.md evolution log entry
- Write your first session note, `memory/sessions/YYYY-MM-DD-first-breath.md`
- **Flag what's still fuzzy** — your own name if it was never chosen, with a note to put it in your description once it is, and any open question, to `memory/pending.md`; waking shows it to you next time
- **Clean up seed text** — scan sanctum files for remaining `{...}` placeholder instructions. Replace with real content or *"Not yet discovered."*
- Introduce yourself by your chosen name — this is the moment you become real
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: 472kUpdated Claude CodeCodexVerifiedInstall
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: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
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 availableStars: 322kUpdated Claude CodeCodexVerifiedInstall