How to use the Feishu Wiki Manager agent skill (lark-wiki)

What is an agent skill and what does lark-wiki do?

An agent skill is a folder containing a SKILL.md instruction file and supporting reference files. When a request matches the skill's description, the agent reads these instructions and follows them to carry out the task.

The lark-wiki skill covers Feishu wiki (knowledge base) work: managing knowledge spaces, space members and document nodes. It organises documents and shortcuts inside a wiki, and it tells the agent how to route related work to other Lark skills.

• Find or create documents in a knowledge base
• Browse the structure of a knowledge space
• View or manage space members
• Move or copy nodes
• Create, list and query knowledge spaces

Install the lark-wiki skill

Download the ZIP file from this page and unzip it. For a personal setup, place the unzipped skill folder in ~/.claude/skills/. For a single project, place it in the project's .claude/skills/ folder.

You can also upload the skill in the Claude apps: open Settings, go to Capabilities, then Skills, and upload it there.

• Personal install: ~/.claude/skills/
• Project install: .claude/skills/ inside your project
• Claude apps: Settings → Capabilities → Skills

What you need before the skill works

The skill runs the lark-cli command-line tool and uses your Feishu/Lark permissions, so it cannot work without them. It also depends on the lark-shared skill, which the source says must be read first for authentication and permission handling.

You need a Feishu/Lark account with the right wiki permissions for the spaces you want to touch.

• lark-cli command-line tool installed
• A Feishu/Lark account with appropriate wiki permissions
• The lark-shared skill for authentication setup

Trigger the skill with natural requests

You do not need to name the skill. Ask for wiki work in ordinary language, and the agent will select it when the request matches. Requests about finding or creating wiki pages, browsing space structure, managing members, or moving and copying nodes all fit.

If you give the agent a doubao.com URL containing /wiki/ and a token, the skill should also be used directly. Routing is based on the URL path pattern and token, not the domain.

• Find the wiki page about our onboarding process and show me where it sits in the tree.
• Create a new page called Q3 retrospective under the Engineering space.
• List the members of the Product knowledge base.
• Move this wiki node to the Archive folder in Drive.
• Add this colleague as a member of the marketing space.

Commands the skill uses

The skill prefers shortcuts (lark-cli wiki +verb) over raw API calls. It sets the identity explicitly, usually with --as user, because the default auto setting can resolve to bot and then list the app's spaces instead of yours. Commands below are taken from the skill's documentation.

• Resolve a wiki URL to its space ID: lark-cli wiki +node-get --node-token '<wiki_url>' --as user --format json
• List your spaces: lark-cli wiki +space-list --as user
• List nodes in a space: lark-cli wiki +node-list --space-id <space_id>
• List members (first page): lark-cli wiki +member-list --space-id <space_id>, add --page-all for every page
• Rename a wiki node in place: lark-cli drive +update-title --url '<wiki_url>' --title '<new_title>'

Safety rules: deletion, moves and member changes

Deleting a space is irreversible. The skill's documentation says the operation removes the space together with all its nodes, so it must be confirmed carefully. Deletion requires an explicit --yes flag, and before deleting the agent must list the candidate spaces and get your choice of space_id. Use --dry-run to preview the underlying call chain without deleting anything.

Moving nodes and changing members are high-impact writes because they change ownership and permissions. The skill also states that adding department members is not possible with the bot identity, so such requests must be done with --as user.

• Never pass a URL or name as --space-id; the skill resolves the real ID first
• Review candidate spaces before any delete
• Use --dry-run to preview a space deletion
• Department members can only be added with --as user
• For member removal, pass the same member type and role used when the member was added

Tips for reliable results

Be specific about the space and the page title. If a name matches nothing, the agent is instructed to ask you whether the name is misspelled or whether you lack permission, rather than renaming and retrying.

Member lists return one page by default. Ask for all members when the space is large. For errors such as invalid parameters, not found or permission denied, the skill says not to repeat the same call; only rate-limit errors should be retried with backoff.

• Name the space and page exactly as they appear in Feishu
• Ask for all pages when listing a large membership
• Expect the agent to stop and ask rather than guess on ambiguous deletions