// Send a message to another mngr agent. Use when you need to communicate with a peer agent.
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.
Resolve an agent name or description to an exact mngr agent name. Used by other skills that target agents.
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 | message-agent |
| argument-hint | <agent_name> <description of what to say> |
| description | Send a message to another mngr agent. Use when you need to communicate with a peer agent. |
| allowed-tools | Bash(echo "$MNGR_AGENT_NAME"), Bash(uv run mngr message *), Write(*), Skill(find-agent) |
The user's message contains a target agent name (the first word) and a description of what to communicate. Extract the agent name and treat everything after it as the intent/content of the message.
Your agent name is: !echo "$MNGR_AGENT_NAME"
Use the /find-agent skill with the first word of the user's input to resolve it to an exact agent name.
Based on the user's description, compose the full message. Every message you send MUST:
[from: !echo "$MNGR_AGENT_NAME"].To reply, use the /message-agent skill.Example message (for an agent named refactor-auth):
[from: refactor-auth]
Hey -- I just finished refactoring the auth middleware on my branch. You'll want to rebase before merging since I changed the SessionStore interface. The new method is `get_session_by_token()` instead of `lookup()`.
To reply, use the /message-agent skill.
Write the composed message to a temporary file using the Write tool, then send it with --message-file. Name the temp file /tmp/mngr-message-from-YOUR_NAME-to-AGENT_NAME.txt (using your agent name and the resolved target name):
uv run mngr message AGENT_NAME --message-file /tmp/mngr-message-from-YOUR_NAME-to-AGENT_NAME.txt
Use --message-file for all messages -- it avoids shell quoting issues and preserves formatting.
Report to the user what you sent and to whom. If the send command fails, report the error.