agent-comm

跨 Agent 通信。当用户说"问XX"、"让XX做"、"发给XX"、"check agent status"时使用。

227 stars

Best use case

agent-comm is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

跨 Agent 通信。当用户说"问XX"、"让XX做"、"发给XX"、"check agent status"时使用。

Teams using agent-comm should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/agent-comm/SKILL.md --create-dirs "https://raw.githubusercontent.com/hyperlist/feishu-multi-agent/main/skills/agent-comm/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/agent-comm/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How agent-comm Compares

Feature / Agentagent-commStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

跨 Agent 通信。当用户说"问XX"、"让XX做"、"发给XX"、"check agent status"时使用。

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# Agent Communication

通过 sessions_send、sessions_list、sessions_history 实现跨 Agent 通信。

## Session Key 格式

每个 Agent Session 有唯一 key:

```
agent:{agent_id}:{channel}:{peer_kind}:{peer_id}
```

示例:
- `agent:trader:feishu:group:oc_xxx`
- `agent:scout:feishu:group:oc_yyy`

**不要硬编码 sessionKey**,用 `sessions_list` 动态查找。

## 工具

### sessions_list

列出活跃 session,找到目标 Agent 的 sessionKey。

```
sessions_list(limit=10, messageLimit=0)
```

### sessions_send

向另一个 Agent 发送消息,等待回复。

```
sessions_send(sessionKey="agent:coder:feishu:group:oc_xxx", message="你的任务描述")
```

- 成功时返回 `status: "ok"` 和 `reply`
- 超时时返回 `status: "timeout"`

### sessions_history

获取某个 Session 的对话历史。

```
sessions_history(sessionKey="agent:coder:feishu:group:oc_xxx", limit=5)
```

## 工作流程

1. 用户说「问 coder 这个 bug 怎么回事」
2. `sessions_list` → 找到 coder 的 sessionKey
3. `sessions_send(sessionKey, message="这个bug怎么回事: ...")` → 等待回复
4. 将 coder 的回复转发给用户

## 注意事项

- 避免循环调用(A→B→A)
- 超时不代表失败,目标 Agent 可能仍在处理
- 不要在消息中泄露其他 Agent workspace 的敏感信息

Related Skills

Maintenance Skill

227
from hyperlist/feishu-multi-agent

飞书多 Agent 项目维护指南 - 仅供维护 feishu-multi-agent 项目时使用。

feishu-doc-writer

227
from hyperlist/feishu-multi-agent

Feishu document writing skill. Handles known API pitfalls (block ordering, unsupported formats). Activate when writing content into Feishu docs or creating structured documents.

feishu-chat

227
from hyperlist/feishu-multi-agent

飞书群聊管理:创建群、添加/移除成员、修改群信息。需要 exec 权限执行 curl 命令。

delegate-agent

227
from hyperlist/feishu-multi-agent

Delegate tasks to agents asynchronously. Triggers on "让XX做", "delegate to", "assign to", "派发", "布置任务".

Config Update Skill

227
from hyperlist/feishu-multi-agent

OpenClaw 配置安全更新指南。

project-switcher

227
from hyperlist/feishu-multi-agent

多项目管理和目录切换。用户发送 /repo 时列出项目,选择后切换工作目录。 适用于 coder agent 同时维护多个代码仓库的场景。

git-workflow

227
from hyperlist/feishu-multi-agent

Git 工作流规范。管理分支、commit、PR 的标准流程。 用户发送 /git 或涉及版本控制操作时触发。

code-review

227
from hyperlist/feishu-multi-agent

代码审查技能。用户发送 /review 或要求 review 时触发。 自动检查代码质量、安全问题、架构建议。

feishu-multi-agent

227
from hyperlist/feishu-multi-agent

飞书多 Agent 系统搭建指南。当用户要求创建新的功能 Agent、配置飞书群聊绑定、 搭建多 Agent 协作系统时激活此 skill。 触发词:创建 agent、新建 agent、添加 agent、create agent、多 agent、飞书绑定。

discovering-make-commands

44152
from streamlit/streamlit

Lists available make commands for Streamlit development. Use for build, test, lint, or format tasks.

Developer ToolsClaude

addressing-pr-review-comments

44152
from streamlit/streamlit

Address all valid review comments on a PR for the current branch in the streamlit/streamlit repo. Covers both inline review comments and general PR (issue) comments. Use when a PR has reviewer feedback to address, including code changes, style fixes, and documentation updates.

Developer ToolsClaude

internal-comms

31392
from sickn33/antigravity-awesome-skills

Write internal communications such as status reports, leadership updates, 3P updates, newsletters, FAQs, incident reports, and project updates using repeatable internal formats.

Text GenerationClaude