Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Manage and export Lark Suite (Feishu) Wiki/Knowledge Base documents. Read, search, sync with subdocuments, and incremental export to local Markdown files.
Manage and export Lark Suite (Feishu) Wiki/Knowledge Base documents. Read, search, sync with subdocuments, and incremental export to local Markdown files.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run.
Manage and export Lark Suite (Feishu) Wiki/Knowledge Base documents with recursive sync and incremental updates.
Create a Lark/Feishu app at https://open.larksuite.com/console Enable permissions: docs:doc:read drive:drive:read wiki:wiki:read Publish the app and authorize it to access your wiki Set environment variables (or edit script defaults): 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: Saves sync state to .lark-sync-state.json Compares revision IDs Skips unchanged documents
# 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: Main .md file Subfolders for child documents Numbered prefixes for ordering (01_, 02_, etc.)
Lark Open Platform: https://open.larksuite.com/ Wiki API: https://open.larksuite.com/document/uAjLw4CM/ukTMukTMukTM/reference/wiki-v1/space/overview Docx API: https://open.larksuite.com/document/uAjLw4CM/ukTMukTMukTM/reference/docx-v1/document/overview
Documents must be explicitly shared with your app Some block types may not convert perfectly to Markdown Large wikis with many subdocuments may take time to sync Sync state is saved locally for incremental updates
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.