Menu
Reply to a message
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.
Based on SOC occupation classification
Multi-agent coordination via messaging, groups, and shared context. Use when agents need to communicate, delegate work, or coordinate across worktrees.
Send a message to an agent
Main Thrum entry point for multi-agent coordination, messaging, session context, and command routing in Codex.
Multi-agent coordination via messaging, groups, and shared context. Use when agents need to communicate, delegate work, or coordinate across worktrees.
Multi-agent coordination via messaging, groups, and shared context. Use when agents need to communicate, delegate work, or coordinate across worktrees.
Save a comprehensive 16-section restart snapshot and prepare for session restart. Use for designer/architect-grade handoffs needing wire contracts, capability matrix, anticipated Q&A, and design rationale that the standard $thrum-restart compact format cannot carry.
| name | thrum-reply |
| description | Reply to a message |
Use this skill when the user explicitly wants the reply Thrum workflow. Prefer
the umbrella thrum skill when the request spans multiple commands or needs
broader coordination judgment.
Reply to a message with the same audience as the original.
If arguments are provided, use them. Otherwise ask for the message ID and reply content.
thrum reply <msg-id> "response text"
The reply inherits the original message's audience (direct or group).
If the body has backticks, $(...), $VAR, or quotes, pass it via a quoted
heredoc so the shell doesn't corrupt it (thrum-d3fp):
thrum reply <msg-id> --stdin <<'EOF'
Done — see `internal/foo.go`. Cost was $(estimate).
EOF
--body-file <path> reads from a file; the response argument - is a stdin
alias.