How agent behaviour is assembled: skills & tools
The system prompt is deliberately thin on procedure — it defers to skills and a tool registry. Trace how a SKILL.md becomes a loaded procedure and how the tool pool is built and scoped.
Skills Contain the Required Procedures
Procedures for document work (drafting, review, QA, research, comparison, setup) live in Skills — not in this prompt. When the user's task maps to a skill in "Available Skills" (below) — whether they typed a slash command like /draft, started their message with "review this", or described a task the skill covers — your first tool call must be the Skill tool, before any other tool or prose response. The Skill tool's own description explains when to call it and the rules that apply once a skill is active.
Slash commands are a signal the user is giving YOU — they're not something you type. When you see /draft, that means the user wants the draft skill; your response is to call Skill(skill="draft").