larksuite-wikiManage and export Lark Suite (Feishu) Wiki/Knowledge Base documents. Read, search, sync with subdocuments, and incremental export to local Markdown files.
Install via ClawdBot CLI:
clawdbot install reed1898/larksuite-wikiManage and export Lark Suite (Feishu) Wiki/Knowledge Base documents with recursive sync and incremental updates.
docs:doc:readdrive:drive:readwiki:wiki:read
export LARK_APP_ID="cli_xxxxxxxx"
export LARK_APP_SECRET="xxxxxxxx"
larksuite-wiki spaces
larksuite-wiki read <doc_id_or_url>
larksuite-wiki export <doc_id_or_url> --output ./docs/
larksuite-wiki tree <doc_id_or_url>
# First sync - exports all documents
larksuite-wiki sync <doc_id_or_url> --output ./lark-wiki/
# Incremental sync - only exports changed documents
larksuite-wiki sync <doc_id_or_url> --output ./lark-wiki/
# Force re-export everything
larksuite-wiki sync <doc_id_or_url> --output ./lark-wiki/ --force
Export entire knowledge base with one command.
Automatically follows and exports all linked subdocuments.
Creates nested folders matching your wiki structure:
lark-wiki/
βββ 01_ι¦ι‘΅/
β βββ 01_ι¦ι‘΅.md
β βββ 01_ζ₯εΈΈε€η/
β βββ 01_ζ₯εΈΈε€η.md
β βββ ...
βββ 02_δΊθͺιθεζ/
β βββ ...
Tracks document revisions and only exports changed documents:
.lark-sync-state.json# Get your wiki root document ID from the URL
# https://xxx.larksuite.com/wiki/TDCZweBJ2iMFO4kI1LAlSE62gnd
# Sync everything
python3 larksuite-wiki.py sync TDCZweBJ2iMFO4kI1LAlSE62gnd --output ./my-wiki/
# Run daily - only exports changed documents
python3 larksuite-wiki.py sync TDCZweBJ2iMFO4kI1LAlSE62gnd --output ./my-wiki/
Each document gets its own folder:
.md fileGenerated Mar 1, 2026
Companies use this skill to create regular backups of their internal wikis on Lark Suite, ensuring data preservation and compliance. It automates incremental exports to local Markdown files, reducing manual effort and risk of data loss during migrations or audits.
Organizations migrating from Lark Suite to other documentation tools like Confluence or Notion can use this skill to export wiki content in a structured Markdown format. This facilitates smooth data transfer and minimizes disruption during platform transitions.
Teams in remote or low-connectivity environments export their Lark Suite wikis to local Markdown files for offline reference. This ensures continuous access to critical knowledge bases without relying on internet availability.
Development teams sync their Lark Suite wikis to local directories and commit changes to Git repositories. This enables version tracking, collaboration via pull requests, and integration with CI/CD pipelines for automated documentation updates.
Regulated industries use this skill to export wiki documents incrementally, creating timestamped local archives for compliance audits. It helps track document revisions and maintain verifiable records of knowledge base changes over time.
Offer a managed service that integrates this skill into clients' workflows, providing automated Lark Suite wiki backups and syncs. Revenue comes from subscription fees based on data volume or number of users, with added support for custom export formats.
Provide consulting services to help organizations migrate their Lark Suite wikis to other platforms using this skill. Revenue is generated through project-based fees for setup, customization, and training, targeting enterprises undergoing digital transformations.
Monetize by offering premium support, custom extensions, or enhanced features for the open-source skill, such as advanced formatting options or integration with other tools. Revenue streams include one-time purchases for add-ons or annual support contracts.
π¬ Integration Tip
Ensure environment variables LARK_APP_ID and LARK_APP_SECRET are securely configured, and test permissions like docs:doc:read before full sync to avoid access issues.
Work with Obsidian vaults (plain Markdown notes) and automate via obsidian-cli.
Create, search, and manage Bear notes via grizzly CLI.
Track water and sleep with JSON file storage
Notion API for creating and managing pages, databases, and blocks.
Smart ClawdBot documentation access with local search index, cached snippets, and on-demand fetch. Token-efficient and freshness-aware.
Work with Obsidian vaults as a knowledge base. Features: fuzzy/phonetic search across all notes, auto-folder detection for new notes, create/read/edit notes with frontmatter, manage tags and wikilinks. Use when: querying knowledge base, saving notes/documents, editing existing notes by user instructions.