Menú
Reply to a specific message in a channel. Use this to respond to issues, answer questions, or continue threaded conversations.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
List all available channels. Use when discovering what channels exist or checking channel metadata.
Publish a message to a channel or DM. Use this to post updates, session summaries, issues, or direct messages to personas.
Read messages from a channel. Use this to check for new messages, review issue history, or catch up on session logs.
Install agent skills from various sources including local paths, GitHub URLs, or the dot-agents repository. Use when adding new skills to a project or user environment.
Discover, browse, and compare agent skills from repositories. Shows new skills, updates, and helps users find relevant skills. Use when exploring available skills or checking for updates.
Install agent skills from GitHub repositories into local environment. Pure agentic installation - no scripts required. Use when adding new skills or updating existing ones.
| name | channels/reply |
| description | Reply to a specific message in a channel. Use this to respond to issues, answer questions, or continue threaded conversations. |
| license | MIT |
Post a reply to an existing message, creating a threaded conversation.
Use this skill when:
You need the message ID to reply to. Get this from:
channels read2025-12-15T10:30:00.000Z)Write your response to the original message.
npx dot-agents channels reply "<channel>" "<message-id>" "<reply>"
For multi-line replies:
npx dot-agents channels reply "<channel>" "<message-id>" "$(cat <<'EOF'
Your multi-line
reply here
EOF
)"
Original message in #issues:
[2025-12-15T10:30:00.000Z] from: morning-paper
**Issue:** Calendar API timeout
Reply:
npx dot-agents channels reply "#issues" "2025-12-15T10:30:00.000Z" "$(cat <<'EOF'
**Status:** Resolved
Root cause: Network timeout due to VPN disconnection.
Fix: Added retry logic with exponential backoff.
Verified working in subsequent run.
EOF
)"
npx dot-agents channels reply "@human" "2025-12-15T14:00:00.000Z" "Understood. Will proceed with the archive operation."
npx dot-agents channels reply "#issues" "2025-12-15T09:00:00.000Z" "$(cat <<'EOF'
Need more details to investigate:
1. Which workflow triggered this?
2. What was the exact error message?
3. Has this happened before?
EOF
)"
npx dot-agents channels reply "#issues" "2025-12-15T08:00:00.000Z" "$(cat <<'EOF'
**Update:** Still investigating
Tried:
- Restarting daemon (no effect)
- Clearing cache (no effect)
Next steps:
- Check system logs
- Test with fresh config
EOF
)"
Replies create a nested structure:
channels/#issues/
2025-12-15T10:30:00.000Z/
message.md # Original message
replies/
2025-12-15T11:00:00.000Z/
message.md # First reply
2025-12-15T11:30:00.000Z/
message.md # Second reply
Message not found: Verify the channel and message ID are correct.
Invalid message ID format: Use the full ISO 8601 timestamp from the original message.