Feishu Api Cache Fix

What This Skill Does

The Feishu API Cache Fix skill, developed by @bryan-chx, is a targeted utility designed to resolve performance bottlenecks and rate-limiting issues encountered when interacting with the Feishu (Lark) API suite. In many automated gateway environments, constant polling or redundant requests made every minute can quickly exhaust API quotas. This skill addresses that specific issue by implementing a robust 2-hour caching mechanism directly within the probe.ts file of the affected infrastructure. By caching API responses, the system significantly reduces outbound network traffic, stabilizes service availability, and prevents the frequent 429 Too Many Requests errors that disrupt business workflows.

Installation

To integrate this fix into your environment, ensure you have the OpenClaw agent running. Execute the following command in your terminal to fetch and install the skill from the central repository:

clawhub install openclaw/skills/skills/bryan-chx/feishu-api-cache-fix

Once installation is complete, navigate to your project root and execute the provided shell script to apply the patch:

sudo bash fix_feishu_cache.sh

Verify the integration by checking your logs to confirm that API requests are now hitting the cache rather than triggering immediate external calls.

Use Cases

This skill is essential for DevOps engineers and automation developers who rely on Feishu for real-time notifications, group management, or attendance tracking. It is particularly useful in environments where multiple microservices query the Feishu API concurrently. By enforcing a 2-hour cache, you effectively throttle excessive traffic while ensuring that the data retrieved remains reasonably fresh for standard operational needs. It is ideal for monitoring scripts, bot integration, and internal reporting tools that query Feishu status periodically.

Example Prompts

• "OpenClaw, please install the Feishu API cache fix to resolve my gateway rate limit issues."
• "Run the feishu-api-cache-fix script to optimize my system performance and stop the 429 errors."
• "Can you help me implement the 2-hour cache fix for my Feishu integration using the bryan-chx skill?"

Tips & Limitations

While this cache significantly reduces API load, it introduces a 2-hour lag for data updates. Ensure your application logic is prepared to handle stale data during this window. If your use case requires absolute real-time precision for specific events, consider bypassing the cache for those specific endpoints. Always backup your probe.ts before running the patch script to ensure you can revert changes if necessary.