Skills
Skills are reusable instruction sets — markdown files that teach Dynamo how to perform specific tasks.
/skill # browse available skills
/skill commit # run a specific skill
/skill create-skill # create a new skill interactively
/commit # shortcut for /skill commit
/debug # shortcut for /skill systematic-debuggingBuilt-in Skills
Dynamo ships with 8 built-in skills inspired by the Superpowers methodology:
| Skill | Activation | What it does |
|---|---|---|
| commit | manual | Conventional commits with Unity .meta awareness |
| brainstorming | auto | Design-first — explore options before writing code |
| systematic-debugging | auto | 4-phase root cause investigation |
| tdd | auto | RED-GREEN-REFACTOR enforced cycle |
| code-review-request | manual | Structured review dispatch with git scope |
| code-review-receive | manual | Evaluate review feedback on technical merit |
| create-skill | manual | Guided skill creation flow |
| unity-project-config | auto | Helps you tune project indexing (skip dirs, custom scene loaders, singleton attributes) |
Auto skills list their name and trigger in the system prompt and load their full body on demand when your message matches. Manual skills only fire when you invoke them by name or with a shortcut.
Custom Skills
Skills live in .dynamo/skills/ (project) or your personal config dir (~/.config/dynamo/skills/). Local skills override personal, and both override built-ins of the same name.
Each skill is a directory with a SKILL.md file and optional resource subdirectories:
my-skill/
├── SKILL.md # instructions + frontmatter (required)
├── references/ # docs the model loads on-demand
├── scripts/ # executable helpers the model can run
└── assets/ # templates, config filesSKILL.md opens with YAML frontmatter:
---
description: One-line summary shown in the /skill picker # required
when-to-use: Detailed trigger scenarios for auto-activation # optional
activation: auto # always | auto | glob | manual (default auto)
globs: ["**/*.shader"] # for activation: glob — fires when a matching file is touched
allowed-tools: [read_file, list_files] # auto-approve these while the skill runs
tools: [read_file, edit_file] # optional — restrict the visible tool catalog
model: anthropic/claude-opus-4-6 # optional — swap model while active
argument-hint: "[file-or-pr]" # optional — autocomplete hint
---Activation modes: `always` injects the full body every turn (reserve for critical discipline), `auto` loads on keyword match, `glob` loads when a matching file is touched, `manual` only on explicit invoke. In the body, reference bundled resources with ${DYNAMO_SKILL_DIR} and inject runtime values with $ARGUMENTS / $1 / ${DYNAMO_PROJECT_ROOT}.
allowed-tools is an auto-approve allow-list — it suppresses the permission prompt for those tools while the skill runs, but the blocked-command list and dangerous-tier prompts still apply. A skill can't grant itself anything you couldn't already do.
Creating Skills
Use /skill create-skill for a guided flow that asks what the skill should do, sets permissions, and generates the SKILL.md.