Skills
Instructions the model loads only when the task needs them, from memory books, MCP servers, modules and the built-in assistants.
A skill is a set of instructions the model reads only when it is about to need them. Its name and a one-line when to use are always visible. The body is loaded on demand.
A character profile or a context is paid for on every reply. A skill is not. A support character can carry dozens of how-tos, tens of kilobytes each, and only the one the conversation turns to reaches the prompt.
The format
Skills follow the Agent Skills format, the one Claude Code and Codex load, so a SKILL.md written for one of them works in Voxta:
---
name: reset-password
description: How to reset an account password. Load when someone is locked out.
---
1. Open Settings › Account › Security.
2. …name: lowercase letters, digits and single hyphens, up to 64 characters.description: what the model reads to decide whether to load it. Keep it short and specific.- The body is plain Markdown, any length within reason.
A skill is either one file, Skills/<name>.md, or a folder, Skills/<name>/SKILL.md, with more files beside it. The model can load those extra files one at a time when it needs long reference material.
A file without front matter, a description or a valid name is not a skill. It is skipped and logged.
How the model uses them
The model is offered one tool, load_skill, listing every skill available in this chat. When it loads one, the body stays in the prompt for as long as that turn does. It isn't trimmed like other tool results, since half a manual is worse than none. Once the turn is summarized away, the model loads it again if it still needs it.
Skills need a model and service that can call tools. Without tool calling, chats are offered no skills.
Where skills come from
Memory books
A memory book holds skills as files in its assets, under Skills/, edited from its Assets & Skills tab. A chat offers the skills of the books its characters read. While a character replies, the model sees only the skills of that character's own books. In a group chat, another character's private book is not hers. If two skills share a name, the first one wins and the other is skipped.
A memory entry can point to a skill, so recalling it brings the skill's name up when the conversation turns to that topic.
A skill can be marked explicit (explicit: true under metadata). It is offered only when the character recalls explicit memories, and a PG edition leaves it out.
MCP servers
An MCP server's own instructions become a skill named after its augmentation. They cost nothing until the model is about to use that server.
Modules
A module can embed skills in its build. They are offered in chats running any of that module's augmentations. See Skills and workspaces.
The built-in assistants
The editors' assistants load their own reference material as skills: the scripting API, scenario rooms, button layout and so on. The App Assistant also has the skills of the built-in Voxta memory book, which documents Voxta itself.
Sharing
A memory book's skills are files in its assets, so they travel with it: .voxpak export and import, packages, backups, copies and encryption.