Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
Feishu Card
v1.0.0飞书互动卡片发送技能（国际版 Feishu 兼容）。当需要发送格式丰富的飞书卡片消息时使用。支持标题、Markdown 内容、颜色主题。关键：必须使用 schema 2.0 格式 + 双重 JSON stringify，否则国际版飞书（Feishu）无法渲染。
⭐ 0· 356·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
high confidencePurpose & Capability
Functionality matches the name/description: the code and docs construct a schema 2.0 Feishu interactive card and call Feishu's official endpoints. However, the skill metadata declares no required env vars or config paths while both SKILL.md and scripts/read_card.py require access to the OpenClaw config file (~/.openclaw/openclaw.json). This mismatch (undeclared credential/config requirement) is a material coherence issue.
Instruction Scope
SKILL.md explicitly instructs reading /root/.openclaw/openclaw.json to extract app_secret and provides a curl example that cat's the file into a shell variable — behavior that can leak secrets (shell history, process command lines, logs). The script itself reads ~/.openclaw/openclaw.json and extracts channels.feishu.appSecret. Aside from the secret access, the instructions stay within the stated purpose (obtaining a token and sending a card) and call only Feishu endpoints.
Install Mechanism
No install spec; this is an instruction-only skill with a small included helper script. Nothing is downloaded from external/untrusted URLs and nothing is installed automatically, which is low risk.
Credentials
The skill requires a Feishu app secret to operate, but the registry metadata lists no required environment variables or config paths and no primary credential. The script implicitly reads the user's OpenClaw config file to get the app secret; requesting access to that file (which may contain other secrets) is reasonable for authentication but should be declared. The hard-coded APP_ID is present in the code; that is expected but should be documented. Overall the credential access is reasonable for the task but underdeclared and potentially surprising.
Persistence & Privilege
The skill is not always-included, does not request elevated platform privileges, and does not modify other skills or system-wide settings. It runs as a simple utility script and only performs one-off token fetch and POST to Feishu.
What to consider before installing
This skill appears to do what it claims (construct and send Feishu schema 2.0 interactive cards), but it reads your OpenClaw configuration file (~/.openclaw/openclaw.json) to obtain the Feishu app_secret while the registry metadata declares no required credentials — that's an inconsistency you should address before installing. Recommended actions: 1) Inspect the file ~/.openclaw/openclaw.json to see what secrets it contains and whether you are comfortable the skill can read it. 2) Avoid running the curl example that uses cat to inject the secret into a shell variable (it can leak to logs or process listings); instead supply secrets via a safer mechanism (read-only file with strict permissions or an explicitly declared environment variable). 3) If you do not want the skill to read your OpenClaw config, modify the script to accept APP_SECRET via an environment variable or CLI argument and run it in a restricted account. 4) Verify the hard-coded APP_ID is expected for your environment. 5) If you need stronger assurance, request the author to update skill metadata to declare the required config path/credential and to remove any examples that expose secrets in shell history or logs.Like a lobster shell, security has layers — review code before you run it.
latestvk978e8yyqef0v7bh3sa2tgwhy5829f58
License
MIT-0
Free to use, modify, and redistribute. No attribution required.