Feishu Document Collaboration

What it does

When your agent uses it

• Turning a shared Feishu document into a live back-and-forth with an AI agent
• Letting several people and several agents collaborate in one document
• Adding a lightweight task board on top of document-based collaboration

Example prompts

• “Set up Feishu document collaboration for our planning doc.”
• “Reply inline in the roadmap document to the question I just typed.”
• “Add a status flag to my message so the bot knows I'm still editing.”

Requirements

• OpenClaw with a configured Feishu channel (app ID and secret)
• Feishu event subscriptions for drive.file.edit_v1 and, optionally, bitable_record_changed_v1
• Hooks enabled in openclaw.json

Workflow steps

5 steps, taken from the step headings in SKILL.md.

1. 1Enable hooks in openclaw.json
2. 2Apply the monitor patch
3. 3Configure your agent identity
4. 4Restart the gateway
5. 5Set up the Doc Chat Protocol

What it can do on your machine

Read from SKILL.md and the folder at commit e5199b5. It shows what the files ask for, not the result of running them.

• Tool permissions

  Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

  From allowed-tools in the SKILL.md frontmatter.

• Runs code

  Ships 1 file in scripts/ (TypeScript and Shell), which the agent can run.

  Shell commands in SKILL.md call:

  • bash
  • openssl

  From the folder's file list and the shell code blocks in SKILL.md.

• Network

  No URLs in SKILL.md.

  From URLs in SKILL.md, links to its own repository left out.

• Credentials

  Names no API keys, tokens, secrets or passwords.

  From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Feishu Document Collaboration loads about 2k tokens when it runs, and up to ~8.1k if it reads all its reference files. Until then it costs about 201 tokens; SKILL.md has 726 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it

~201

When it runs · the whole SKILL.md, loaded when a task matches

~2k

With references · SKILL.md plus every file in references/, read only if the agent opens them

~8.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from LeoYeAI/openclaw-master-skills at commit e5199b5, republished under its MIT licence (© LeoYeAI). 726 words, ~1,999 tokens.

name

feishu-doc-collab

description

Enable real-time AI collaboration in Feishu (Lark) documents. When a user edits a Feishu doc, the agent automatically detects the change, reads the document, and responds inline — turning any Feishu document into a live human-AI conversation. Features: - Feishu document edit event → triggers isolated agent session automatically - Structured in-doc chat protocol (status flags prevent premature AI responses while user is still typing) - Multi-party support: multiple humans + multiple AI agents in one document - Bitable (spreadsheet) task board integration for collaborative task management - Anti-loop: bot's own edits are automatically ignored Triggers: Feishu doc collaboration, 飞书文档协作, document edit event, in-doc chat, 文档内对话, Lark document AI, feishu doc auto-reply, 飞书文档自动回复

# Generate a random token
TOKEN=$(openssl rand -hex 16)
echo "Your hooks token: $TOKEN"
# Then add to openclaw.json:
# "hooks": { "enabled": true, "token": "<TOKEN>" }

bash ./skills/feishu-doc-collab/scripts/patch-monitor.sh

{
  "agent_name": "MyBot",
  "agent_display_name": "My AI Assistant"
}

openclaw gateway restart

cp ./skills/feishu-doc-collab/assets/DOC_PROTOCOL_TEMPLATE.md ./DOC_PROTOCOL.md

User edits Feishu doc
        ↓
Feishu sends drive.file.edit_v1 event
        ↓
Patched monitor.ts receives event
        ↓
Checks: is this the bot's own edit? → Yes: skip (anti-loop)
        ↓ No
POST /hooks/agent with isolated session instructions
        ↓
Agent reads DOC_PROTOCOL.md for message format
        ↓
Agent reads the document, finds last message block
        ↓
Checks: status=🟢? addressed to me? not from me?
        ↓ Yes
Agent composes reply and appends to document

---
> **Sender Name** → **Receiver Name** | 🟢 完成

Your message content here.

bash ./skills/feishu-doc-collab/scripts/patch-monitor.sh
openclaw gateway restart

bash ./skills/feishu-doc-collab/scripts/patch-monitor.sh
openclaw gateway restart

© LeoYeAI, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 9 other files (scripts, references, assets) in skills/feishu-doc-collab of LeoYeAI/openclaw-master-skills.

• SKILL.md
• .clawhub/origin.json
• _meta.json
• assets/DOC_PROTOCOL_TEMPLATE.md
• config.json
• references/bitable-task-protocol.md
• references/feishu-app-setup.md
• references/manual-patch.md
• references/monitor-full-patched.ts
• scripts/patch-monitor.sh

Open the folder on GitHubat commit e5199b5