Feishu Perm
- 259 installs
- 4.3k repo stars
- Updated March 29, 2026
- m1heng/clawdbot-feishu
feishu-perm is an agent skill that manages Feishu document and file collaborator permissions through the feishu_perm tool for developers who need least-privilege sharing on docx, sheet, folder, and wiki tokens.
About
feishu-perm is an agent skill in the m1heng/clawdbot-feishu plugin that exposes a single feishu_perm tool for listing, adding, and removing collaborators on Feishu Drive objects. Developers pass JSON actions with a file token, type (docx, sheet, bitable, folder, wiki, and 3 more), member_type (email, openid, openchat, and 3 more), and perm level (view, edit, full_access). The tool returns member_type, member_id, perm, and name on list calls, and requires the drive:permission scope. Permission management is disabled by default in channel config (perm: true must be set explicitly) because sharing changes are sensitive. Reach for feishu-perm when a Feishu bot or OpenClaw agent must grant edit access to a docx, share a folder with a group chat, or audit who already has access—without hand-crafting Feishu Open API permission payloads.
- Feishu scope mapping
- Least-privilege defaults
- Tenant grant workflows
- API capability checks
- Auth failure diagnostics
Feishu Perm by the numbers
- 259 all-time installs (skills.sh)
- +2 installs in the week ending Aug 2, 2026 (Skillselion tracking)
- Ranked #1,454 of 4,348 Backend & APIs skills by installs in the Skillselion catalog
- Data as of Aug 2, 2026 (Skillselion catalog sync)
npx skills add https://github.com/m1heng/clawdbot-feishu --skill feishu-permAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 259 |
|---|---|
| repo stars | ★ 4.3k |
| Last updated | March 29, 2026 |
| Repository | m1heng/clawdbot-feishu ↗ |
How do you manage Feishu document permissions from a bot?
Configure Feishu app scopes, tenant/user grants, and least-privilege permission models so bots and APIs can access docs, chats, and admin APIs safely.
Who is it for?
Developers integrating Feishu bots or OpenClaw agents who must programmatically share docs, sheets, folders, and wiki nodes with emails or chat groups.
Skip if: Teams not on Feishu/Lark or projects that only need message sending without Drive permission changes.
When should I use this skill?
User mentions Feishu sharing, collaborators, document permissions, or granting view/edit access on a Feishu file token.
What you get
JSON collaborator lists and updated view, edit, or full_access grants on Feishu docx, sheet, folder, and wiki tokens.
- Collaborator permission lists
- Updated Feishu Drive ACL grants
By the numbers
- Exposes 3 feishu_perm actions: list, add, and remove
- Supports 8 Feishu token types including docx, sheet, folder, and wiki
- Defines 3 permission levels: view, edit, and full_access
Files
Feishu Permission Tool
Single tool feishu_perm for managing file/document permissions.
Actions
List Collaborators
{ "action": "list", "token": "ABC123", "type": "docx" }Returns: members with member_type, member_id, perm, name.
Add Collaborator
{ "action": "add", "token": "ABC123", "type": "docx", "member_type": "email", "member_id": "user@example.com", "perm": "edit" }Remove Collaborator
{ "action": "remove", "token": "ABC123", "type": "docx", "member_type": "email", "member_id": "user@example.com" }Token Types
| Type | Description |
|---|---|
doc | Old format document |
docx | New format document |
sheet | Spreadsheet |
bitable | Multi-dimensional table |
folder | Folder |
file | Uploaded file |
wiki | Wiki node |
mindnote | Mind map |
Member Types
| Type | Description |
|---|---|
email | Email address |
openid | User open_id |
userid | User user_id |
unionid | User union_id |
openchat | Group chat open_id |
opendepartmentid | Department open_id |
Permission Levels
| Perm | Description |
|---|---|
view | View only |
edit | Can edit |
full_access | Full access (can manage permissions) |
Examples
Share document with email:
{ "action": "add", "token": "doxcnXXX", "type": "docx", "member_type": "email", "member_id": "alice@company.com", "perm": "edit" }Share folder with group:
{ "action": "add", "token": "fldcnXXX", "type": "folder", "member_type": "openchat", "member_id": "oc_xxx", "perm": "view" }Configuration
channels:
feishu:
tools:
perm: true # default: false (disabled)Note: This tool is disabled by default because permission management is a sensitive operation. Enable explicitly if needed.
Permissions
Required: drive:permission
Related skills
Lark Openapi ExplorerInstantly explore, test, and generate calls against the full Lark (Feishu) OpenAPI surface without leaving their agent workflow.493k
Lark EventConsume real-time events from Lark/Feishu as structured NDJSON streams inside AI agent workflows.387k16kLark Openapi ExplorerWhen an existing Lark/Feishu skill or CLI command cannot fulfill a specific requirement and they need to discover and invoke the exact native OpenAPI endpoint.386k16k
Just ScrapeQuickly search, crawl, extract structured JSON, or monitor web pages without writing custom scraping code.245k41Lark AppsQuery the current visibility and permission scope of a Lark (Feishu) app without writing HTTP client code.235k16k
Design An InterfaceGenerate multiple radically different interface or API designs in parallel before committing to one.188k198kHow it compares
Pick feishu-perm over generic API docs when an agent must perform list/add/remove collaborator calls on Feishu Drive tokens with typed member identifiers.
FAQ
What actions does feishu-perm support?
feishu-perm exposes one feishu_perm tool with three actions: list to return collaborators, add to grant view, edit, or full_access, and remove to revoke a member by token, type, member_type, and member_id.
Why is the Feishu perm tool disabled by default?
feishu-perm treats permission changes as sensitive operations. The clawdbot-feishu channel keeps tools.perm false until a developer explicitly sets channels.feishu.tools.perm to true and supplies the drive:permission scope.
Which Feishu file types accept collaborator grants?
feishu-perm accepts eight token types: doc, docx, sheet, bitable, folder, file, wiki, and mindnote. Each add or remove call requires the token, type, member_type, member_id, and desired perm level.