Choose and invoke a skill
Learn how AFK discovers skills and when to use a slash command or a model-invoked skill.
Skills are named procedures for recurring tasks. Some are built into AFK, some ship as bundled plugin workflows, and you can write your own SKILL.md. Use a slash command when you know the workflow you want, or let the model choose a visible skill from its manifest.
Find and run one
/skills to inspect available workflows and /skills review for details about a specific one./review --staged. You can also ask the agent to run a skill by name.The model-facing skill tool invokes visible registered skills directly. A manually hidden skill stays slash-invocable. Skill availability can differ by installed plugins, project directory, and session startup state.
Sources and execution
| Origin | Location or registration |
|---|---|
| Core built-in | Registered by AFK's TypeScript runtime, such as /get-started and /mint. |
| Bundled | Public SKILL.md workflows shipped with the awa-bundled plugin. |
| User | ~/.afk/skills/<name>/SKILL.md. |
| Project | <cwd>/.afk/skills/<name>/SKILL.md. |
| Installed plugin | The plugin's skills/<name>/SKILL.md directory. |
Skills can load instructions into the current agent (context: load) or run in a fresh child session (context: fork). Core TypeScript handlers may execute in process. Forking gives a separate context window, but does not make a skill automatically safe to run without reviewing its effects. Skills that collide across origins may have qualified alternatives such as user:review.
A SKILL.md can declare when-to-use for routing. disable-model-invocation: true or the operator's skills.hidden list keeps a skill out of the model manifest while preserving explicit invocation. See Custom skills for authoring and arguments.