SkillsMar 30, 2026·1 min read

Lark CLI Skill: Wiki — Knowledge Base Management

Lark/Feishu CLI skill for knowledge base. Create and manage knowledge spaces, organize document nodes and shortcuts.

Agent ready

Safe staging for this asset

This asset is staged first. The copied prompt tells the agent to inspect the staged files and ask before activating scripts, MCP config, or global config.

Stage only · 17/100Policy: stage

Agent surface

Any MCP/CLI agent

Kind

CLI Tool

Install

Stage only

Trust

Trust: Community

Entrypoint

Lark CLI Skill: Wiki — Knowledge Base Management

Safe staging command

npx -y tokrepo@latest install a5eb9344-208c-4032-9cca-2a17f53fc271 --target codex

Stages files first; activation requires review of the staged README and plan.

TL;DR

Create and manage Lark/Feishu knowledge spaces and document nodes from the command line.

§01

What it is

This Lark CLI skill provides programmatic access to Lark/Feishu knowledge bases (Wiki). It lets you create and manage knowledge spaces, organize document nodes, add shortcuts, and query the knowledge base structure. All operations happen from the terminal or through automation scripts.

The skill targets developers and knowledge managers who want to automate wiki organization, bulk create documentation, or integrate knowledge base management into CI/CD pipelines.

§02

How it saves time or tokens

Manual wiki management in Lark requires navigating the web UI for each operation. This CLI skill automates bulk operations: creating multiple knowledge spaces, reorganizing document trees, or adding batch shortcuts. For AI agents, the skill provides the APIs needed to publish generated documentation directly into the team wiki.

Automating wiki structure management saves hours of manual drag-and-drop organization.

§03

How to use

Configure the Lark CLI with your app credentials
Use the wiki commands to create spaces, nodes, and shortcuts
Organize documents with move and reorder operations
Query the knowledge base structure for navigation and auditing

§04

Example

# Create a new knowledge space
lark wiki create-space --name 'Engineering Docs' --description 'Technical documentation'

# Add a document node to the space
lark wiki create-node --space-id 'wiki_abc123' --title 'API Reference' --type 'doc'

# List all nodes in a space
lark wiki list-nodes --space-id 'wiki_abc123'

# Add a shortcut to an existing document
lark wiki create-shortcut --space-id 'wiki_abc123' --target-node 'node_xyz789'

# Move a node to a different parent
lark wiki move-node --node-id 'node_001' --parent-id 'node_002'

§05

Related on TokRepo

Documentation tools -- Knowledge management tools
Automation tools -- Workflow automation

§06

Common pitfalls

Wiki API access requires 'wiki:wiki' scope permissions on your Lark app; missing permissions return 403 errors
Document nodes and shortcuts are different types; moving a shortcut does not move the underlying document
Rate limits apply to batch operations; add delays when creating or moving many nodes in sequence

Frequently Asked Questions

What is a knowledge space in Lark Wiki?+

A knowledge space is a top-level container in Lark Wiki, similar to a workspace or project. It contains document nodes organized in a tree structure. Each space can have its own access permissions.

Can I create documents with content via the CLI?+

The CLI creates document nodes (containers). To add content, you create the node first, then use the Lark Docs API to write content into the document. The wiki skill handles the structural organization.

Does this work with both Feishu and Lark?+

Yes. The skill supports both Feishu (Chinese version) and Lark (international version). The API endpoints differ but the CLI handles the routing based on your app configuration.

Can I export wiki content?+

The wiki skill provides structure queries (list nodes, get node details). Content export requires the Lark Docs API. You can combine both to export complete knowledge bases with structure and content.

How do permissions work for wiki spaces?+

Space permissions are managed through the Lark admin console or the wiki API. The CLI skill can query but not modify permissions. Set permissions in the web UI before automating content creation.