2.2Phase 2: Discovery

On every conversation turn, the system:

1. Scans all skill locations for SKILL.md files
2. Reads the YAML frontmatter from each
3. Filters to skills that have a description field
4. Formats all skill names + descriptions into a text block
5. Injects this block into the Skill tool's description

The formatted block looks approximately like:

Available skills:
- playwright-cli: Browser automation via CLI. Navigate pages, click elements,
  fill forms, take snapshots and screenshots, extract page state.
- commit: Create well-formatted git commits with conventional commit messages.
- pdf: Convert documents to PDF format.

This is embedded in the tools array sent with every API request. It consumes tokens, but far fewer than MCP tool schemas — a skill contributes ~50-100 tokens to the tool description vs 500-2000 per MCP tool.

Token Budget

The system enforces a ~15,000 character budget for the available skills listing. If you install too many skills, some may be truncated or omitted. This is why skill descriptions should be concise.