本文へ移動
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(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

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.

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

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/AgentTeams5,7432026年10月12日 更新

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

日本語の概要は準備中です。原文の説明を表示しています。

agentscope-ai/AgentTeams5,7432026年10月12日 更新

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/AgentTeams5,7432026年10月12日 更新

将编码工作委托给 Manager 持有的 AI CLI 工具(Claude Code / Gemini CLI / qodercli)执行

日本語の概要は準備中です。原文の説明を表示しています。

agentscope-ai/AgentTeams5,7432026年10月12日 更新

Execute AI coding CLI tools (Claude Code / Gemini CLI / qodercli) on behalf of Workers. Use when a Worker sends a coding-request: message, asking Manager to run coding operations in their workspace.

日本語の概要は準備中です。原文の説明を表示しています。

agentscope-ai/AgentTeams5,7432026年10月12日 更新

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/AgentTeams5,7432026年10月12日 更新

agentscope-ai のスキルをすべて見る

このスキルの問題を報告する