/skill-name slash
commands, or programmatically through SkillManager.invoke().
This page covers the invocation layer added in v1.5+. For how to author
skills, see Agent Skills.
How invocation works
Auto-trigger
Skill
description is included in the system prompt. The LLM decides
when to follow it.Slash command
/deploy staging renders the skill body with $ARGUMENTS
substituted and short-circuits the LLM call path.Argument substitution
InsideSKILL.md bodies you can reference arguments passed after the
skill name:
- $ARGUMENTS
- Indexed
- Shorthand
- Context vars
/deploy staging prod becomes Deploy staging prod now.Inline shell substitution
Inline backtick form
Inline backtick form
Fenced block form
Fenced block form
Invocation policy
When
true the skill is hidden from the system-prompt listing, so
the LLM cannot auto-trigger it. Users can still invoke it via
/skill-name. Use for side-effecting commands like /deploy.When
false the slash-router ignores the skill. Use for background
knowledge you want auto-triggered by the LLM but not exposed as a user
command.Allowed tools pre-approval
Space-separated string (
Read Grep) or YAML list. When a user invokes
the skill, those tool names are pre-approved via the approval
registry for the current agent so the LLM can run them without the
interactive confirmation prompt.Python API
YAML
CLI
Precedence
Skills are discovered in this order (first wins on name collision):Collisions are logged at INFO level so you can see which skill won.
See also
- Agent Skills — authoring format, SKILL.md structure
- Approval Protocol — how
allowed-toolsplugs in - Configuration —
SkillsConfigoptions

