How skills work
- System prompt injection — the server builds an
<available_skills>XML block listing every enabled skill with its name, description, and file path. - Model reads
SKILL.md— before starting a task the AI opens the relevant skill’s instructions via theviewtool. - Scripts and references — skills can bundle Python/bash helpers and reference docs that the AI invokes with
bash_tool.
/mnt/skills/.
Built-in skills (13 public)
Always available, baked into the Docker image:Example skills (14)
Optional, in the image at/mnt/skills/examples/:
web-artifacts-builder, copy-editing, social-content, canvas-design, algorithmic-art, theme-factory, mcp-builder, product-marketing-context, writing-skills, internal-comms, single-cell-rna-qc, slack-gif-creator, skill-creator (example variant).
Creating a skill
A skill is a folder withSKILL.md at the root:
SKILL.md format
skills/public/ in the repo for real examples.
Per-user skill management
In the production Yambr setup we built a skill registry (settings-wrapper):- The AI manages skills through a dedicated
settings-managerskill. - Users enable/disable skills per account.
- Custom skills are uploaded as ZIPs and cached on the server.
Related
- Skills reference — deeper per-skill details
- Dynamic skills — under-the-hood injection
- Creating skills — publishing your own
