OpenParable
Skip to content
← Back to skills

Communication

Productivity
communication

Communication is an Agent Skill for productivity published in the agentscope-ai/AgentTeams repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

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

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/agentscope-ai/AgentTeams/blob/HEAD/manager/agent/copaw-worker-agent/skills/communication/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/communication, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

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 hiclaw 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.