بنقرة واحدة
find-agent
// Resolve an agent name or description to an exact mngr agent name. Used by other skills that target agents.
// Resolve an agent name or description to an exact mngr agent name. Used by other skills that target agents.
End-to-end dev workflow for the minds app stack -- first-time bring-up, every-startup vendor/mngr sync, and the iteration loop against a running Docker agent. Use this when starting or restarting the dev Electron app, or after changing any minds component (mngr, the system interface, the FCT template).
Create a new PRIVATE GitHub repo that is a full-history copy of imbue-ai/forever-claude-template's current main branch, clone it to <parent-dir>/<repo-name> (default $HOME/project), and push. Use when the user asks to "spin up a new forever-claude clone", "fork the forever-claude template as a private repo", "make me a new private copy of forever-claude-template", or similar.
Cut a new "production" release of the minds app. Pushes a release branch in the mngr clone at ~/project/minds_prod, syncs vendor/mngr in ~/project/forever-claude-template to match, pushes the same-named branch there, and merges the release branch into FCT main. Use when the user asks to "release a new version of minds", "cut a minds release", "update the vendored mngr in forever-claude-template to track <branch>", or anything of that shape.
Send a message to another mngr agent. Use when you need to communicate with a peer agent.
Wait for another agent to enter WAITING state, then execute follow-up instructions
Match tutorial script blocks to e2e pytest functions and add missing tests
| name | find-agent |
| argument-hint | <agent_name_or_description> |
| description | Resolve an agent name or description to an exact mngr agent name. Used by other skills that target agents. |
| allowed-tools | Bash(uv run mngr list *) |
The user's input is an agent name or description. Resolve it to an exact agent name.
The user may paste a git branch name like mngr/some-agent instead of the bare agent name. In that case, strip the mngr/ prefix to get the actual agent name (e.g. mngr/better-tabcomplete -> better-tabcomplete).
Verify the target agent exists by running:
uv run mngr list --format '{name}'
If the extracted name doesn't match any agent exactly, check if the user's input was a description (e.g. "the agent working on X") rather than a name, and try to match against the listed agents and their git branches. If there's an unambiguous match, use it. Otherwise, use AskUserQuestion to ask the user which agent they meant, presenting the plausible candidates.
Report the resolved agent name back to the caller.