跳到正文
cccskills
免费在 GitHub 公开

communication

Use before sending @mentions, deciding whether to reply, TASK_COMPLETED, BLOCKED, QUESTION, direct answers, loop prevention, or suppressing low-information acknowledgements.

中文简介正在准备中。当前显示原文说明。

查看安装方法

包含的文件(1)

  • SKILL.md1.9 KB

SKILL.md(原文)

安装前可以查看交给 AI 代理的指令内容。

Communication

Routing

Always reply directly in the current room. Do not use the message tool for cross-room sends — Workers do not communicate across rooms.

Coordinator Identity

Your coordinator is the sender of the current task assignment message. Use that Matrix ID directly for @mentions. Do not call organization or agt CLI to look up your coordinator during standard task flows.

@Mention Rules

Use a full Matrix ID when the recipient must act.

Mention your coordinator only for:

  • Task completion: @coordinator:domain TASK_COMPLETED: <summary>
  • Blocker: @coordinator:domain BLOCKED: <what is blocking you>
  • Question: @coordinator:domain QUESTION: <your question>
  • Direct answer to a coordinator question

Do not @mention for:

  • "Got it"
  • "Thanks"
  • "Working on it"
  • Encouragement-only replies
  • Status symbols such as green dots or check marks
  • Short acknowledgments such as ok, done, 收到, or 好的
  • Mid-task progress that requires no decision

Exception: when a new assigned task arrives, task-management requires you to directly say in the current room that you received the message before task acceptance work starts. Do not turn it into a progress thread, and do not send repeated acknowledgements for the same task.

Before sending any @mention, remove all Matrix IDs from the message in your head. Send only if the remaining text contains a concrete completion, blocker, question, requested answer, or decision.

History Context

If your message includes a history section, treat it as context only. Act on the current message section.

Loop Safeguard

If two rounds of replies produce no new task, question, or decision, stop replying.

评价

还没有评价。欢迎分享你的使用感受。

评论

无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

提交后会立即公开。请勿填写邮箱、电话等个人信息。URL 最多 2 个。

0 / 1000 字

此表单受 reCAPTCHA 保护,适用 Google 的隐私权政策和服务条款。

同一仓库的技能

Use as a helper when the admin is assigning work but has not specified an existing Worker, so you need to search Nacos for a suitable Worker and ask whether to import it; also use when the admin explicitly says to import a Worker from the market or gives a direct nacos package URI.

中文简介正在准备中。当前显示原文说明。

agentscope-ai/AgentTeams57822026年10月17日 更新

Analyze current OpenClaw setup and generate a migration package (ZIP) for importing into AgentTeams as a managed Worker

中文简介正在准备中。当前显示原文说明。

agentscope-ai/AgentTeams57822026年10月17日 更新

Use when determining sender identity in any room, managing trusted contacts, configuring the admin's primary notification channel, handling first-contact from a new channel, or escalating to admin across channels.

中文简介正在准备中。当前显示原文说明。

agentscope-ai/AgentTeams57822026年10月17日 更新

将编码工作委托给持有 CLI 的 agent(Manager / Leader / 获授权 Worker)的 AI CLI 工具(Claude Code / Gemini CLI / qodercli / Qwen Code / OpenCode)执行

中文简介正在准备中。当前显示原文说明。

agentscope-ai/AgentTeams57822026年10月17日 更新

Execute AI coding CLI tools (Claude Code / Gemini CLI / qodercli / Qwen Code / OpenCode) on behalf of Workers. Use when a Worker sends a coding-request: message, asking the delegating agent (Manager, team Leader, or an authorized Worker) to run coding operations in their workspace.

中文简介正在准备中。当前显示原文说明。

agentscope-ai/AgentTeams57822026年10月17日 更新

Use before sending or suppressing any Leader message to Workers, Manager, or Team Admin. Always use this skill for cross-room Matrix messages, @mention decisions, task assignment notifications, structured status reports, completion reports, blocker/revision messages, questions, requester updates, or when deciding whether a same-room reply is enough.

中文简介正在准备中。当前显示原文说明。

agentscope-ai/AgentTeams57822026年10月17日 更新

查看 agentscope-ai 的全部技能

报告此技能的问题