What problem does it solve? Running many coding agents across multiple repositories makes it hard to know which sessions need attention, how to message or spawn sessions correctly, and which CLI tools are available. This Skill orients an agent to the installed DevThrottle product so it can supervise the fleet through the cc-devthrottle command instead of guessing at HTTP endpoints. ## Core Features & Use Cases - Fleet and session management: List, spawn, rename, message, and gracefully close sessions with cc-devthrottle, including naming conventions, permission presets, and cleanup of child sessions. - cc- tool suite orientation*: Discover installed CLI tools for documents (cc-pdf, cc-word), email (cc-gmail, cc-outlook), media (cc-voice, cc-whisper), desktop automation (cc-click, cc-trisight), and reporting (cc-dev-reports). - Signed-in browser profiles: Drive real browser profiles the user signed into once via cc-devthrottle browser, avoiding the failure mode of launching an unsigned browser. - Use Case: An agent finishes a task in an unattended session, publishes its findings with cc-dev-reports, then runs cc-devthrottle session done to reap itself cleanly from Mission Control. ## Quick Start Ask the agent to list the current DevThrottle sessions and available cc-* tools using the cc-devthrottle command.