Use when the task is to inspect or operate a live desktop application, native window, browser accessibility tree, menu, dialog, button, list, toggle, or text input through the built-in computer_use tool. Prefer this for host UI focus, snapshot, click, type, select, toggle, scroll, screenshot, or chat-style message flows. Prefer scenario actions `message|type|select|click|toggle` over generic `act` whenever the user goal is already clear.
Use when the task centers on a workspace .pdf file and needs native PDF reading, creation, filling, or reformatting. Supports read_mode presets for speed vs coverage.
Use when writing or reviewing Golang code in this project. Triggers: database schema design, architecture decisions, high-availability implementation, code review, bug fixing, performance optimization, command execution, goroutine management. This project follows TDD (Test-Driven Development) - always write tests first.
Perform administrative/system operations: provider management, settings, channel/skill/tool toggles, user controls, health/version, and proxy stats. Use for ops/admin tasks, diagnostics, and runtime configuration changes.
Live web interaction skill. Use Browser when the task needs an actual browser session for login, JS-heavy pages, clicking, typing, scrolling, screenshots, or challenge handling.
Use when the task centers on a workspace .docx file and needs native Word-style creation, editing, templating, or validation.
Run the external email CLI through exec for real IMAP/SMTP/Notmuch mailboxes. Use when the user explicitly wants a real terminal email workflow instead of the built-in benchmark email surfaces.
Generate images or videos through the built-in media pipeline. Use explicit `blue media generate` / `blue media status` commands when the user wants media creation, task polling, or model/category control.