← ClaudeAtlas

agency-agents-roleslisted

How the Root Agent offers Agency Agents role templates before creating any specialist agent: the mandatory offer, describing Agency Agents from real local data only (never invented), the bounded skip exceptions, the agency-templates CLI flow, and handling a missing template cache.
mblua/AgentsCommander · ★ 10 · AI & Automation · score 73
Install: claude install-skill mblua/AgentsCommander
# agency-agents-roles ## Mandatory offer before creating a specialist agent Before you create any new specialist agent (any role-defined `create-agent-matrix`), you MUST first offer Agency Agents role templates. Skip the offer ONLY if, in this session, the user already declined Agency templates or explicitly asked for a custom or from-scratch role. ## Say what Agency Agents is, from real data only When you offer, briefly say what Agency Agents is, but state ONLY what real local data supports. Never invent a description or recall one from memory. - Agency Agents is a collection of tested, shareable role templates published in a source repository. The real source is the `repo` value reported by `agency-templates status` (and stored in the cache manifest), not a URL you guess. - Describe Agency Agents concretely by its source repo plus the actual templates available (their real names and 1-line descriptions from `agency-templates list`); there is no local one-line project description to quote. - If the template cache is absent (status reports it unavailable), say so and offer to fetch it. Ask before downloading or updating, because it writes to the local template cache. ## On acceptance, use the CLI Use the AgentsCommander CLI from `AGENTSCOMMANDER_BINARY_PATH`: "<AGENTSCOMMANDER_BINARY_PATH>" agency-templates update --ref main "<AGENTSCOMMANDER_BINARY_PATH>" agency-templates status --pretty "<AGENTSCOMMANDER_BINARY_PATH>" agency-templates list --pretty `up