One skill per installed team

The Claude Code Plugin Shipped

Installing a team regenerates the plugin, so it shows up as its own skill alongside the static roster and config skills.

The myagenticteams plugin surfaces each enabled team as /myagenticteams:<team>, re-rendered from the live registry on every registry mutation. Two static skills ride alongside — roster for team management, config for default reviewer models — plus a pinned code-review skill wired to devteam at risk scope. The CLI is the engine those skills shell out to, so the terminal and the editor run exactly the same pipeline.

Some commands only work from a session

A few things cannot run as a single bare-CLI shot, and they reach that state three different ways. Three are interactive by declaration — teambuilder's create-team and improve-team and brainstormteam's brainstorm carry the flag in their own team data. devteam's build loop is a builtin that prints a pointer instead of starting. And --fix is the narrowest case of all: the review itself runs fine from a terminal, and only the fixing pass redirects, because only a session can dispatch the pinned coder. What none of them do is silently no-op or claim a fix that did not happen.