larksuite-wiki

What This Skill Does

The larksuite-wiki skill provides a robust command-line and programmatic interface to manage, explore, and export your Feishu (Lark Suite) Knowledge Base. It serves as a bridge between cloud-hosted enterprise documentation and local Markdown files. The skill features a powerful recursive synchronization engine that maps the complex tree structure of a Wiki directly into your local file system, creating nested folders and preserving document hierarchy. It is designed for knowledge workers who want to maintain a local backup of their wiki content, integrate documentation into static site generators, or perform version control on enterprise knowledge using Git.

Installation

To integrate this skill into your environment, use the OpenClaw CLI tool. Run the following command in your terminal: clawhub install openclaw/skills/skills/ryanhong666/larksuite-wiki After installation, ensure you have created an app in the Lark Developer Console with the required permissions (docs:doc:read, drive:drive:read, and wiki:wiki:read). Finally, export your LARK_APP_ID and LARK_APP_SECRET as environment variables to enable authenticated access to your documents.

Use Cases

• Offline Backup: Create a local, searchable copy of your team's knowledge base to ensure data availability without internet access.
• Documentation Migration: Export complex Wiki trees into Markdown files to move content to platforms like Obsidian, Jekyll, or Docusaurus.
• Version Control: Track changes to internal policies or technical specifications by syncing the wiki to a local Git repository and observing changes over time.
• Content Auditing: Use the tree command to visualize the depth and structure of your Wiki to identify orphaned documents or broken organizational logic.

Example Prompts

1. "Sync my entire team wiki from URL https://larksuite.com/wiki/doc123 to my local './docs/backup' folder using the larksuite-wiki skill."
2. "Show me the tree structure for the Engineering Wiki root document to verify if the documentation subfolders are correctly organized."
3. "Perform an incremental sync on the Marketing Knowledge Base to download only the documents that have been updated since yesterday."

Tips & Limitations

• Incremental Efficiency: Always use the sync command for daily operations. It creates a .lark-sync-state.json file, significantly reducing API usage by skipping unchanged documents.
• Permissions: Ensure the specific document tree you are syncing has been shared with your Lark app user/service account; otherwise, the skill will return an access denied error.
• Markdown Conversion: Since Lark documents use a specialized block-based format, some complex interactive elements or advanced formatting may require manual cleanup after export.
• API Rate Limits: For massive wikis, the recursive export might take time. Consider the potential for Lark API rate limiting if you have thousands of nested documents.