stevehuang0115
stevehuang0115/crewly
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/stevehuang0115/crewly --skill reply-google-chat命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Assign a task to a worker within the Team Leader's subordinate scope. Validates that the target worker's parentMemberId matches the TL's memberId before delegation. Includes auto-monitoring setup.
Create a new task via the task-management API for autonomous work decomposition.
Mark a task as blocked with a reason and optional questions for the orchestrator.
基于 SOC 职业分类
正在显示 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.