Menu
Send a message to another mngr agent. Use when you need to communicate with a peer agent.
The review-first prompt is selected by default. You can switch to a direct command or download a local copy.
Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
A direct command skips the review prompt. Inspect the source before running it.
npx skills add https://github.com/imbue-ai/mngr-claude-skills --skill message-agentThe command stays on one line. Scroll horizontally to inspect it before copying.
Prefer a local copy? Download the files currently available to SkillsMP.
Based on SOC occupation classification
Showing SKILL.md
| 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(mngr message *), Bash(uv run mngr message *), Write(*), Skill(imbue-mngr-skills: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"
Skip this step if the user seems to have provided the exact name of the agent -- just use the first word of their input directly as the target. Otherwise (for example they pasted a branch name like mngr/foo, or described the agent instead of naming it), run the /imbue-mngr-skills:find-agent skill, which explains how to find the 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 /imbue-mngr-skills: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 /imbue-mngr-skills: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):
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.