ClawHub

飞书API接口调用次数优化

v1.0.0

优化飞书扩展的 probe 缓存配置，将健康检查缓存延长至成功24小时、失败1小时，显著降低API调用次数。

⭐ 1· 263·0 current·0 all-time
byBobbyCat@bobbycats
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
✓
Purpose & Capability
The skill's name/description match the runtime instructions: it tells you to edit the Feishu probe TTL constants, rebuild the OpenClaw workspace, and restart the user service. All required actions are directly related to reducing probe frequency.
ℹ
Instruction Scope
Instructions require modifying a source file under ~/.openclaw/workspace and running a full pnpm build plus systemctl user restart. These steps are in-scope for changing probe behavior but carry operational risk (service downtime, build mistakes). The doc explicitly warns about compilation pitfalls and directs use of journalctl for troubleshooting; it does not request unrelated files, secrets, or external data exfiltration.
✓
Install Mechanism
This is an instruction-only skill with no install spec, no downloads, and no code files. Nothing will be written or installed by the skill itself; actions are manual commands the operator runs.
✓
Credentials
The skill requests no environment variables, credentials, or config paths. It does require write access to the user's workspace and permission to run systemctl --user, which is proportional to the task of updating and restarting the local service.
ℹ
Persistence & Privilege
The skill does not request persistent special privileges or set always:true. However, the recommended workflow modifies local source and restarts a user service — this requires filesystem write access and the ability to control the user systemd service. Those are expected but carry operational impact if done incorrectly.
Assessment
This instruction set is coherent with the goal, but follow safe operational practices before applying: 1) Back up or commit the original probe.ts and any important config (openclaw.json). 2) Test changes in a staging environment if possible. 3) Ensure pnpm and build dependencies are available and be prepared for a full rebuild time/cost. 4) Edit the source file (not dist/compiled files) and verify the compiled output in dist/extensions before restarting. 5) Expect possible service downtime if the dist directory becomes incomplete; keep access to logs (journalctl) and a recovery plan. 6) Consider filing a PR or asking the OpenClaw maintainer for a configurable TTL as a safer long-term fix so updates don't revert your change.

Like a lobster shell, security has layers — review code before you run it.

latestvk974we4153zg2b1vg38pzp905982bnjv

License

MIT-0
Free to use, modify, and redistribute. No attribution required.
Termshttps://spdx.org/licenses/MIT-0.html

Comments