Skip to content
TrustedSkillsbeta
Back to all skills

Feishu Perm

Checked
m1heng·vlatest·security·MIT

This skill automates Feishu permission management, streamlining user access and enhancing security for seamless workflows.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add m1heng/clawdbot-feishu --skill feishu-perm -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

m1heng

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned m1heng/clawdbot-feishu at b07885b756.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
b07885b756
Manifest
skills/feishu-perm/SKILL.md
Scanned
1 file, 79 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill, Feishu Perm, automates permission management within Feishu (Lark's messaging and collaboration platform). It allows an AI agent to list collaborators on files/documents, add new collaborators with specific permissions, and remove existing collaborators. The tool supports various file types including documents, spreadsheets, tables, folders, and more, streamlining user access control and enhancing security. It is disabled by default due to the sensitivity of permission management operations.

When to use it

  • Granting edit access to a document for a specific team member.
  • Removing read-only access from a folder after a project phase concludes.
  • Listing all collaborators on a shared spreadsheet to audit permissions.
  • Adding a group chat as a viewer to a file.
  • Managing permissions on various Feishu resources like documents, spreadsheets, and folders.

Key capabilities

  • List Collaborators: Retrieves a list of users with access to a specified document or folder, including their member type, ID, permission level, and name.
  • Add Collaborator: Adds a new user as a collaborator on a file/document, specifying the user's identifier (email, open_id, etc.) and desired permission level (view, edit, full access).
  • Remove Collaborator: Removes an existing user from a file/document’s collaborators.
  • Supports various document types: doc, docx, sheet, bitable, folder, file, wiki, mindnote.
  • Handles different member identifiers: email, openid, userid, unionid, openchat, opendepartmentid.
  • Offers permission levels: view, edit, full_access.

Example prompts

  • "List the collaborators on document with token ABC123."
  • "Add user [email protected] to the document with token doxcnXXX and give them edit permissions."
  • "Remove user [email protected] from the folder with token fldcnXXX."

Tips & gotchas

  • The skill is disabled by default; you must explicitly enable it in your configuration (perm: true).
  • Permission management is a sensitive operation, so ensure appropriate safeguards are in place before enabling and using this tool.
  • You need the correct "token" for each file/document to manage permissions.