Menu
Send a message to a Google Chat space or thread via the backend API.
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/stevehuang0115/crewly --skill reply-google-chatThe 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 | Reply Google Chat |
| description | Send a message to a Google Chat space or thread via the backend API. |
| version | 1.0.0 |
| category | communication |
| skillType | claude-skill |
| assignableRoles | ["orchestrator"] |
| triggers | ["reply gchat","reply google chat","send gchat","google chat message"] |
| tags | ["communication","google-chat","notification"] |
| execution | {"type":"script","script":{"file":"execute.sh","interpreter":"bash","timeoutMs":30000}} |
IMPORTANT: This skill is for PROACTIVE notifications only. When responding to an incoming [GCHAT:...] message, do NOT use this skill — just output a [NOTIFY] block and the system will automatically route your reply to the correct Google Chat thread. Using this skill for incoming GCHAT replies causes duplicate messages.
Use this skill ONLY when you need to send a message to Google Chat without an incoming GCHAT trigger (e.g. task completion notifications, proactive status updates).
Send a message to a Google Chat space (with optional thread) via the Crewly backend API. This bypasses terminal output parsing and delivers the message directly to Google Chat, avoiding PTY line-wrapping and ANSI artifacts.
# Flag-based invocation
bash config/skills/orchestrator/reply-gchat/execute.sh --space "spaces/AAAA" --text "Task completed!" --thread "spaces/AAAA/threads/BBB"
# Multi-line text from stdin
cat message.txt | bash config/skills/orchestrator/reply-gchat/execute.sh --space "spaces/AAAA" --thread "spaces/AAAA/threads/BBB"
# JSON argument (legacy)
bash config/skills/orchestrator/reply-gchat/execute.sh '{"space":"spaces/AAAA","text":"Hello","threadName":"spaces/AAAA/threads/BBB"}'
| Parameter | Required | Description |
|---|---|---|
space / --space | Yes | Google Chat space name (e.g. spaces/AAAA...) |
text / --text / stdin | Yes | Message text |
threadName / --thread | No | Thread name for threaded replies (e.g. spaces/AAAA/threads/BBB) |
conversationId / --conversation | No | Conversation ID from the [GCHAT:...] prefix so the queue can resolve instantly |
--text-file |
| No |
| Read message text from the specified file path |
--json / -j | No | Raw JSON payload |
If your message contains special characters like parentheses (), single quotes ', backslashes \, or dollar signs $, use --text-file or stdin to avoid bash escaping issues:
# Write message to a temp file first
bash config/skills/orchestrator/reply-gchat/execute.sh \
--space "spaces/AAAA" \
--thread "spaces/AAAA/threads/BBB" \
--text-file /tmp/reply.txt
# Or pipe via stdin
echo "message with special chars (like these)" | bash config/skills/orchestrator/reply-gchat/execute.sh \
--space "spaces/AAAA" \
--thread "spaces/AAAA/threads/BBB"
JSON confirmation on success. After a successful API call the script automatically emits a [NOTIFY] block so the backend logs the reply and unblocks any pending Google Chat messages.