Interact with skills to extend capabilities. Skills are defined in SKILL.md files located in workspace/skills (system) or project directory (project-specific).
Actions
activate
Load the full SKILL.md content (instructions, guidelines, examples). Use this first to understand how to use the skill.
{"name": "skill-name", "action": "activate"}
load
Load reference files or assets from the skill directory. Useful for loading templates, examples, or documentation.
{"name": "skill-name", "action": "load", "args": "references/guide.md"}
{"name": "skill-name", "action": "load", "args": "assets/template.json,references/api.md"}
args: Comma-separated paths relative to skill directory
script
Execute a script/command in the skill's directory.
{"name": "skill-name", "action": "script", "args": "python generate.py --input data.json"}
{"name": "skill-name", "action": "script", "args": "node scripts/build.js --env production"}
args: Full command with arguments (executed with 5-minute timeout)- Output is truncated to 15000 chars if too long
- Working directory: The command runs with
cwdset to the skill's root path (shown asskill_pathin activate output). Use paths relative to skill root, or use the absoluteskill_pathdirectly.
Typical Workflow
activate— Read skill instructions to understand usageload— Load any needed references or assetsscript— Execute scripts if the skill provides automation
Notes
- Skill names use kebab-case:
my-skill-name - Available skills are listed in system prompt under
<available_skills>