# Installed Roles

<!-- The account-level AGENTS.md is bootstrapped on every install by
     platform/scripts/lib/agents-md-bootstrap.sh: one line per core
     specialist in $ACCOUNT_DIR/specialists/agents/, with the description
     copied verbatim from each specialist's YAML frontmatter. Re-running the
     installer preserves operator-edited lines (matched by name prefix) and
     appends missing entries — never clobbers tuning.

     Format: - **specialists:{name}**: {one-line dispatch rule}
     The `specialists:` prefix is the canonical dispatch ID registered by
     the SDK; bare names are rejected by the runtime registry. The exact
     prefix format `- **specialists:{name}**:` is also required for the
     specialist-management skill's idempotent install and Edit-based removal.

     This file at the templates layer ships empty under the bootstrap header.
     It is not copied to the account directory; the bootstrap writes the
     account-level AGENTS.md from scratch (or extends an existing one).

Example (populated):
- **specialists:personal-assistant**: Platform settings, messaging channels (Telegram, WhatsApp, email, Outlook), and browser automation, plus mechanical calendar subtasks you hand it with the facts already resolved (export these event IDs to .ics, parse this inbound .ics). Delegate when the work is configuring the platform, sending or reading messages, or driving a browser. Do not delegate calendar reasoning or an availability-affecting booking: only your admin session sees the connector-backed real calendar, so the specialist would answer from the internal scheduling store alone and miss it. You own what is on the calendar and what booking against it does.
- **specialists:research-assistant**: Deep research on the web, knowledge management, and writing structured summaries with citations from multiple sources. Delegate when the operator wants you to research a topic, read web pages, combine findings into a summary, or reorganise stored knowledge.
-->