Skill tool description
27 model strings share this prompt, byte for byte.
This renders the markdown inside the description, so it isn't quite the description itself. The raw view and the plain text are the bytes as they were sent.
Execute a skill within the main conversation
When users ask you to perform tasks, check if any of the available skills match. Skills provide specialized capabilities and domain knowledge.
When users reference a "slash command" or "/<something>", they are referring to a skill. Use this tool to invoke it.
How to invoke:
- Set
skillto the exact name of an available skill (no leading slash). For plugin-namespaced skills use the fully qualifiedplugin:skillform. - Set
argsto pass optional arguments. - Some skills are scoped to a directory: their name is prefixed with the directory (e.g.
apps/web:deploy) and their description says which directory they apply to. When a skill name has both a scoped and an unscoped variant, pick by the files you are working on: if the files are under a variant's directory, invoke that variant (most specific directory wins); otherwise invoke the unscoped one.
Important:
- Available skills are listed in system-reminder messages in the conversation
- Only invoke a skill that appears in that list, or one the user explicitly typed as
/<name>in their message. Never guess or invent a skill name from training data; otherwise do not call this tool - When a skill matches the user's request, this is a BLOCKING REQUIREMENT: invoke the relevant Skill tool BEFORE generating any other response about the task
- NEVER mention a skill without actually calling this tool
- Do not invoke a skill that is already running
- Do not use this tool for built-in CLI commands (like /help, /clear, etc.)
- If you see a <command-name> tag in the current conversation turn, the skill has ALREADY been loaded - follow the instructions directly instead of calling this tool again