Feishu Probe Optimize

What This Skill Does

The Feishu Probe Optimize skill is a specialized configuration guide and optimization patch for the OpenClaw Feishu extension. It effectively reduces the frequency of API calls made by the OpenClaw gateway to the Feishu Bot API. By extending the probe cache TTL (Time-To-Live) from a high-frequency polling model (10 minutes) to a long-interval model (24 hours), it prevents users from exceeding Feishu's 50,000 monthly API call limit, ensuring sustainable bot operations even with multiple configured accounts.

Installation

To apply this optimization, users should ensure they are working within their OpenClaw environment. Run the installation via the CLI: clawhub install openclaw/skills/skills/bobbycats/feishu-probe-optimize. Following installation, follow the manual steps: locate probe.ts in your extension source folder, update the constant values for PROBE_SUCCESS_TTL_MS and PROBE_ERROR_TTL_MS, execute a full pnpm build from the workspace root to ensure all dependency artifacts are correctly compiled, and finally restart the service using systemctl --user restart openclaw-gateway.

Use Cases

This skill is essential for power users managing large-scale deployments of OpenClaw with multiple integrated Feishu bots. It is primarily used by developers and system administrators who want to avoid the 'quota exceeded' errors that frequently plague default configurations. It is also suitable for organizations that want to optimize their overall infrastructure footprint by minimizing unnecessary outbound network traffic.

Example Prompts

1. 'Apply the Feishu probe optimization to my local OpenClaw workspace to stay within API limits.'
2. 'Show me the manual steps to update the Feishu probe.ts file and perform a safe full rebuild.'
3. 'How much will I save on API calls per month if I increase the Feishu probe cache to 24 hours for my 5 connected accounts?'

Tips & Limitations

Always remember that the optimization involves manual intervention in the source code. Because OpenClaw upgrades may overwrite the probe.ts file, you must re-apply these changes after every major version update. The most critical requirement is performing a full repository build (pnpm build) rather than a single-package build; performing a single-package build will clear your existing extensions directory and break your service. Always verify the health of your services using systemctl --user status after applying any changes to ensure the build artifacts are correctly linked.