larksync-feishu-local-cache

What This Skill Does

The larksync-feishu-local-cache skill enables OpenClaw to mirror your Feishu (Lark) documentation into a local cache directory. By shifting the primary document source from live cloud API calls to a local file system, it drastically reduces dependency on Feishu's external API. This ensures that when OpenClaw needs to analyze, summarize, or answer questions about your documents, it consumes significantly fewer tokens and experiences lower, more stable retrieval latency. The skill supports configurable synchronization cycles, defaulting to a low-frequency daily download to keep local content fresh without overwhelming your network or API quota.

Installation

To integrate this skill into your environment, use the OpenClaw command-line interface. Run the following command in your terminal:

clawhub install openclaw/skills/skills/gooderno1/larksync-feishu-local-cache

Ensure that you have the LarkSync service installed on your Windows machine, as this skill interacts with the local service to bridge the gap between your cloud data and OpenClaw's processing engine. For WSL users, the skill includes a specific helper utility (larksync_wsl_helper.py) to manage cross-environment file system pathing and connectivity.

Use Cases

• Token Optimization: Ideal for heavy users of document-based AI who wish to minimize costs associated with external API lookups.
• Performance Tuning: Critical for scenarios where cloud API responsiveness is unstable or rate-limited, ensuring OpenClaw always has the data it needs.
• Data Sovereignty/Availability: Provides a local offline backup of your critical Feishu documents, allowing the agent to function even during temporary cloud connectivity interruptions.
• Unified Knowledge Management: Syncs diverse project documentation into a standardized local markdown structure for seamless processing by OpenClaw.

Example Prompts

1. "Set up a daily 01:00 sync for the Project X folder to my local directory to save on API costs."
2. "Check the status of my current LarkSync authorization and verify if the latest document version was successfully cached."
3. "Evaluate the risks of switching my documentation sync to bidirectional mode and then proceed with the configuration."

Tips & Limitations

• Default Strategy: Stick to download_only for the best balance of safety and performance. Only enable bidirectional or upload_only if your workflow specifically requires pushing changes back to Feishu.
• WSL Considerations: If you are running OpenClaw in WSL, always run python larksync_wsl_helper.py diagnose first to ensure the path mapping between Linux and the Windows file system is correctly configured.
• Resource Management: Regularly monitor your local cache disk space, especially if you are syncing large media-heavy Feishu docs. The tool is designed to be lightweight, but consistent growth of document volume over time should be reviewed periodically.