Content Collector Skill Guide

What this skill solves

Group chats constantly generate:

• Tutorial links
• Feishu documents
• External articles
• Reference URLs

These sink into history and become hard to find. Content Collector turns "links that flash by in chat" into "searchable, archivable knowledge base entries."

Typical flow:

1. Detect links in messages
2. Fetch content
3. Classify and organize
4. Write to Feishu docs or knowledge base
5. Update multidimensional tables
6. Maintain an index page

Prerequisites before installing

• Feishu OAuth set up and authorized
• Document and table permissions granted to the bot
• A clear knowledge base structure (Space ID, Table ID, etc.)

Install only when your Feishu bot, document writes, and basic skill chain are already stable.

Installation

Prefer the ClawHub registry when available:

openclaw skills install @clawhub/content-collector

If the skill is hosted on GitHub, you can install from the repo:

git clone https://github.com/wuhongchen/content-collector-skill.git
mv content-collector-skill ~/.openclaw/workspace/skills/content-collector
openclaw gateway restart

Configuration

Key parameters (often in workspace config or MEMORY.md, not necessarily openclaw.json):

• Knowledge Base Space ID — Feishu knowledge base identifier
• Table ID — Multidimensional table App Token / ID
• Index Document URL — Where the index page lives

Example prompt to have OpenClaw fill config:

Update the content-collector skill config. My Feishu multidimensional table App Token is [YOUR_TOKEN], knowledge base Space ID is [YOUR_SPACE_ID], index document URL is [YOUR_URL]. Write these into MEMORY.md, replacing existing placeholders.

If you do not know the IDs, share the Feishu table or knowledge base links and ask OpenClaw to help extract them.

Verify the pipeline step by step

Do not expect "send one link and everything works" right away. Validate in order:

1. Link detection — Ensure supported links (Feishu docs, external URLs) are recognized.
2. Classification — Check that categories (tutorials, cases, docs, notes) are sensible.
3. Knowledge base write — Confirm Space ID and bot permissions work.
4. Table and index — Verify multidimensional table fields and index format match expectations.

Common errors

OAuth not completed

Sometimes the error is indirect. If Feishu authorization is missing, the chain fails downstream. Complete the OAuth flow first.

Space ID wrong or no permission

Symptoms: "Cannot access knowledge base space." Check:

• Space ID is correct
• Bot has edit permissions in the space

Table field mismatch

If the table lacks required fields (e.g. "original URL"), collection fails. Fix the table schema instead of reinstalling the skill.

Best practices

• Define a clear classification scheme before heavy use
• Add keywords for important content
• Periodically verify the index page is up to date
• Spot-check critical entries manually

Avoid: dumping many links at once, sending private or sensitive content without filtering, ignoring image-handling errors, leaving dead links unmaintained.

External links

• OpenClaw docs
• OpenClaw GitHub
• Feishu channel
• Config templates