원클릭으로
message-agent
Send a message to another mngr agent. Use when you need to communicate with a peer agent.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
Send a message to another mngr agent. Use when you need to communicate with a peer agent.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Resolve an agent name or description to an exact mngr agent name. Used by other skills that target agents.
Use whenever there's any indication that knowing about mngr would be useful. Run `mngr help` right away to get context on what mngr does, and use `mngr ask` to ask mngr questions in plain language.
Wait for another agent to enter WAITING state, then execute follow-up instructions
| 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.