Lark CLI Skill: Wiki — Knowledge Base Management

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.

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.

How to use

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

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'

Related on TokRepo

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

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