Feishu Upload Image

Upload a local image to Feishu and get its image_key. Use when you need to send an image via Feishu IM but first need the image_key returned by the upload AP...

Security Scan

The skill does what it says (upload a local image to Feishu) but its runtime demands are not fully declared and it reads a platform config file by default, which is an incoherence you should review before installing.

Purpose & Capability

The skill's purpose (upload a local image to Feishu and return image_key) matches the script's behavior. However, the registry metadata declares no required config paths, env vars, or primary credential, while the SKILL.md and script read credentials from an OpenClaw config file (default /root/.openclaw/openclaw.json) or FEISHU_APP_ID/FEISHU_APP_SECRET. This mismatch between declared requirements and actual needs is incoherent.

Instruction Scope

SKILL.md and the script are narrowly scoped (local file -> Feishu image_key) and use only Feishu's API. But the instructions (and script) explicitly read a platform config file for credentials and cache an app token in /tmp. The SKILL.md does not declare the dependency on reading that config path, nor does it declare required binaries (curl, python3) that the script uses.

Install Mechanism

No install spec; this is an instruction-only skill with an included shell script. No packages are downloaded or extracted during install, so the install mechanism itself is low-risk.

Credentials

Requesting Feishu appId/appSecret is proportionate to the task. However: (1) the skill did not declare these as required credentials in metadata (no primary credential), (2) it reads the OpenClaw config file by default which may contain other sensitive data on the host, and (3) required binaries (python3, curl) are not declared. The use of a default path (/root/.openclaw/openclaw.json) is a surprise capability that increases the risk surface.

Persistence & Privilege

The skill is not always-enabled, does not modify other skills, and only writes a short-lived token cache to /tmp/feishu_app_token.cache. It does not request elevated or persistent system privileges.

What to consider before installing

This skill's functionality is straightforward, but there are a few red flags you should address before installing: (1) The script reads credentials from /root/.openclaw/openclaw.json by default — the registry metadata did not declare this config path. Verify that file only contains the expected Feishu credentials or instead set FEISHU_APP_ID and FEISHU_APP_SECRET in the environment. (2) The script requires curl and python3 but the skill metadata doesn't declare required binaries; ensure those binaries are available in the runtime. (3) The script caches an app token in /tmp; ensure that caching policy is acceptable in your environment. (4) Confirm the skill source and owner (no homepage/origin provided). If you proceed, run the script in a least-privileged environment (isolated container or dedicated runner), review the openclaw.json contents, and consider updating the skill metadata to declare the config path and primary credential so the requirement is explicit.

Upload a local image file to Feishu and receive the image_key needed for sending via feishu_im_user_message.

只做一件事：本地文件 → image_key

Usage

bash <skill-dir>/scripts/upload-image.sh /path/to/image.png

Environment variables

export FEISHU_IMAGE_PATH="/path/to/image.png"
bash <skill-dir>/scripts/upload-image.sh

Output

img_v3_02104_xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxxg

Complete Workflow

# 1. Upload → get image_key
IMAGE_KEY=$(bash <skill-dir>/scripts/upload-image.sh /path/to/image.png)

# 2. Send via feishu_im_user_message tool (OpenClaw-native, user token auto-managed)
#    action=send, msg_type=image, content="{\"image_key\":\"<IMAGE_KEY>\"}"

Credentials

Reads appId and appSecret from openclaw.json at channels.feishu. Can be overridden with env vars FEISHU_APP_ID and FEISHU_APP_SECRET.