2.5k
GitHub Stars
2
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill openclaw/skills --skill feishu-im- _meta.json280 B
- SKILL.md8.2 KB
Overview
This skill integrates with Feishu IM to send messages and manage group chats and group features. It exposes 25+ IM capabilities including sending text and interactive cards, creating and managing chats, pinning and urgent messaging, and configuring group menus, tabs, widgets, and announcements. Use it when you need reliable programmatic control of Feishu conversations and group tooling.
How this skill works
The skill calls Feishu IM REST endpoints under https://open.feishu.cn/open-apis/im/v1 using tenant access tokens in the Authorization header. It serializes message content as required (notably card JSON must be stringified and escaped), supports multiple receive_id types, and exposes endpoints for pins, reactions, urgent messaging, batch sends, chat creation and membership management, and group UI features like menus, tabs and widgets. It also returns standard Feishu error codes to guide retries and permission fixes.
When to use it
- Send structured notifications or interactive cards to users or chats.
- Create project or team group chats and ensure members can see them immediately.
- Pin important messages or set top notices for a chat.
- Urgently notify on-call users for P0 incidents (use sparingly).
- Add menus, tabs, or widgets to turn a chat into a lightweight project workspace.
- Batch-send announcements to many chats while respecting rate limits.
Best practices
- Always stringify the content field for messages; escape nested quotes in interactive card JSON.
- Prefer interactive cards for structured info; use lark_md for formatting and @ mentions when needed.
- After creating a chat, explicitly call the add-members API to avoid visibility/caching delays.
- Limit batch sends to ~200 chats per request and implement exponential backoff for 429/230014 errors.
- Reserve urgent_app calls for true P0 events because it consumes quota.
- Keep pinned items minimal and pin only core cards or status messages.
Example use cases
- Automated incident alerts: send urgent card to on-call members and mark message as urgent.
- Project onboarding: create project chat, add members, post welcome card, and add project menu and tabs.
- Weekly report: post interactive summary card and set it as top notice for the group.
- Feature rollout: batch-send release notes cards to multiple team chats with controlled pacing.
- Monitoring dashboard: add a widget in chat displaying real-time metrics or feed cards.
FAQ
Always stringify the card JSON as the content field and escape internal double quotes; validate card structure if delivery fails.
Can the bot recall any message?
No — a bot can only recall messages it sent and only within Feishu's allowed recall window; check message ownership and timing before delete.
How to handle rate limit errors?
Respect 230014 and 429 responses: back off, retry with exponential delay, and reduce batch sizes per request.