How do I install the Feishu Perm skill?

Run npx skillmds@latest add grtninja/feishu-perm in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Feishu Perm safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: reads secrets. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Feishu Perm?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Feishu Perm free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Feishu Perm?

grtninja (@grtninja) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Feishu Perm by grtninja — Agent Skill

Name: Feishu Perm
Rating: 4.666666666666667 (3 reviews)
Author: grtninja

Feishu Perm

Manage Feishu file and document permissions via the feishu_perm tool. Use when listing collaborators, granting access, revoking access, or checking whether a file, folder, wiki node, or document has the correct permission level.

grtninja Updated Sep 10, 2026

File contents

Feishu Permission Tool

Single tool feishu_perm for managing file and document permissions across supported Feishu object types.

Workflow

List current collaborators before changing permissions.
Confirm the correct target token and object type.
Apply the minimum permission change needed (add or remove).
Re-list collaborators to verify the final permission state.

Actions Summary

Action	Description
`list`	List collaborators and their current permissions
`add`	Grant a permission level to a member
`remove`	Revoke collaborator access

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)

Key Constraints

Permission changes are sensitive operations; keep this tool explicitly enabled and use the narrowest permission needed.
type, member_type, and member_id must all match the target object and principal format.
full_access can manage permissions and should be granted sparingly.

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

Guardrails

Use local or trusted tools only; avoid untrusted install pipelines.
Do not paste secrets/tokens into chat output.
Keep outputs in deterministic local paths for reproducible review.

---name: feishu-permdescription: Manage Feishu file and document permissions via the feishu_perm tool. Use when listing collaborators, granting access, revoking access, or checking whether a file, folder, wiki node, or document has the correct permission level.---# Feishu Permission ToolSingle tool `feishu_perm` for managing file and document permissions across supported Feishu object types.## Workflow1. List current collaborators before changing permissions.2. Confirm the correct target `token` and object `type`.3. Apply the minimum permission change needed (`add` or `remove`).4. Re-list collaborators to verify the final permission state.## Actions Summary| Action | Description || ------ | ----------- || `list` | List collaborators and their current permissions || `add` | Grant a permission level to a member || `remove` | Revoke collaborator access |## 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) |## Key Constraints- Permission changes are sensitive operations; keep this tool explicitly enabled and use the narrowest permission needed.- `type`, `member_type`, and `member_id` must all match the target object and principal format.- `full_access` can manage permissions and should be granted sparingly.## ExamplesShare document with email:```json{ "action": "add", "token": "doxcnXXX", "type": "docx", "member_type": "email", "member_id": "alice@company.com", "perm": "edit"}```Share folder with group:```json{ "action": "add", "token": "fldcnXXX", "type": "folder", "member_type": "openchat", "member_id": "oc_xxx", "perm": "view"}```## Configuration```yamlchannels: 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.## PermissionsRequired: `drive:permission`## Guardrails- Use local or trusted tools only; avoid untrusted install pipelines.- Do not paste secrets/tokens into chat output.- Keep outputs in deterministic local paths for reproducible review.

Frequently asked questions