Feishu Api Cache Fix

The name/description (reduce Feishu API calls by caching probe results) align with the included script, which replaces probe.ts with a caching implementation. However, the skill does not declare that it will write to OpenClaw's installation path (/usr/local/lib/node_modules/openclaw/extensions/feishu/src/probe.ts) or that it requires elevated privileges to do so. That mismatch between claimed 'no requirements' and the script's filesystem modification is noteworthy.

SKILL.md tells the user to run sudo bash fix_feishu_cache.sh. The script makes an unconditional backup and then overwrites the feishu probe.ts file at a hardcoded global node_modules path. It does not validate the existing file's contents, confirm compatibility, or limit changes to a local/test environment. While the change is narrowly scoped (no network/exfiltration), overwriting another extension's source file is broad in impact and could break or subvert the Feishu integration.

This is an instruction-only skill with no install spec (low install-surface). However, the included shell script writes to a system-installed node_modules path and requires sudo, so although there is no packaged installer, the script will persist changes on disk — treat as higher-risk than a purely read-only instruction.

The skill declares no required environment variables or credentials, which fits the simple caching change. But it implicitly requires filesystem write access to OpenClaw's installation and root privileges (the SKILL.md calls sudo). The absence of any declared config paths or privilege requirement is an omission that reduces transparency.

The script modifies another extension's source file in the global node_modules tree — this is persistent and changes behavior of the Feishu integration beyond the skill's own files. The skill does not request 'always: true', but its disk modification of other component code is a privilege/impact that should be highlighted and approved explicitly by the operator.