一键导入
reply-channel
Send an agent-authored message back to a chat channel — used by the chat MVP dispatch loop after processing a `[CHAT:<channelId>]` prompt.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Send an agent-authored message back to a chat channel — used by the chat MVP dispatch loop after processing a `[CHAT:<channelId>]` prompt.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | reply-channel |
| description | Send an agent-authored message back to a chat channel — used by the chat MVP dispatch loop after processing a `[CHAT:<channelId>]` prompt. |
| version | 1.0.0 |
| category | comm |
| skillType | claude-skill |
| tags | ["chat","comm","channel","reply"] |
| execution | {"type":"script","script":{"file":"execute.sh","interpreter":"bash","timeoutMs":15000}} |
Send an agent-authored message back to a chat channel. Used by the chat MVP
dispatch loop: when an agent receives a [CHAT:<channelId>] ... prompt from
the user, it processes the request, then calls this skill to publish its
reply into the same channel.
After you receive a message that begins with [CHAT:<channelId>] from the
dispatch runtime. The reply must be written to the same channel so the
user's chat UI sees it.
bash config/skills/agent/core/reply-channel/execute.sh \
--channel <channelId> \
--content "your reply text" \
[--cmid <clientMessageId>]
Or with JSON:
bash config/skills/agent/core/reply-channel/execute.sh \
'{"channelId":"chan-1","content":"hello back","clientMessageId":"cmid-abc"}'
CREWLY_SESSION_NAME — your agent session id. Auto-set in agent sessions.
The skill attaches it as X-Agent-Session so the backend routes the
reply as senderType:"agent".CREWLY_API_URL — defaults to http://localhost:8787.On success prints {"success":true, "messageId":"..."} to stdout.
On failure prints {"success":false, "error":"..."} to stdout and exits
with a non-zero code.
Plan and create a NESTED team hierarchy (parent coordination team + per-stream child teams) for a complex multi-stream goal. Use INSTEAD of recommend-team/materialize-team when the goal names 2+ parallel work-streams (e.g. frontend + backend + DevOps). Onboarding-only.
Search the live web for a query and return ranked results (title, URL, snippet) as JSON. Works with no API key (DuckDuckGo HTML fallback) and uses the Brave Search API or SerpAPI automatically when BRAVE_API_KEY / SERPAPI_KEY is set. Any agent can call it for research, competitor analysis, market/trend lookups, fact-checking, finding sources to cite, or grounding a non-software goal (marketing, growth, commerce) in real-world information.
Transcribe a local audio (or video) file to text with timestamps using Whisper. Defaults to local whisper.cpp (free, offline, word/segment-level timestamps) and automatically falls back to the OpenAI Whisper API (whisper-1) when the local engine is not installed. Any agent can call it for meetings, podcasts, voice notes, interviews, or video audio tracks.
Accept and take the next available task from the task queue. Use when an agent is idle and ready to pick up the highest-priority unassigned task. For assigning tasks to specific agents, use assign-task instead.
Register the agent as active with the Crewly backend on startup. Use when an agent first launches and needs to join the team and become visible to the orchestrator. For confirming responsiveness after registration, use heartbeat instead.
Analyze git changes and produce a structured code review with automated checks for missing tests, debug statements, potential secrets, large changes, and dependency modifications. Use when reviewing staged changes, unstaged diffs, recent commits, or branch comparisons before submitting a pull request. For task-level quality gates, use check-quality-gates instead.