Feishu Card Display

v1.0.0

Use when another skill returns Feishu display payloads or `messageToolCalls`. This skill teaches the agent to use OpenClaw `message` tool to send Feishu card...

0· 99·0 current·0 all-time

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for yqxu/feishu-card-display.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Feishu Card Display" (yqxu/feishu-card-display) from ClawHub.
Skill page: https://clawhub.ai/yqxu/feishu-card-display
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install feishu-card-display

ClawHub CLI

Package manager switcher

npx clawhub@latest install feishu-card-display
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
medium confidence
Purpose & Capability
Name/description match the instructions: the skill's sole job is to instruct the agent to use the OpenClaw message tool to deliver Feishu card/text/media payloads. It does not request unrelated binaries, credentials, or installs.
Instruction Scope
Instructions are narrowly scoped to executing upstream messageToolCalls in order, preserving payloads exactly, and replying with NO_REPLY. This is coherent for a display-forwarding skill, but enforcing verbatim forwarding and a silent final reply increases the risk that upstream or attacker-controlled payloads could be forwarded without user-visible confirmation.
Install Mechanism
Instruction-only skill with no install spec and no code files. This is low-risk from a disk/execution perspective since nothing is downloaded or installed by the skill itself.
Credentials
No environment variables, credentials, or config paths are requested in the registry metadata or SKILL.md. That aligns with the claimed behavior (relies on existing platform message tool to handle transport/auth).
Persistence & Privilege
always is false and the default autonomous invocation is unchanged. The skill does not request persistent system-level privileges or modifications to other skills' configs. Note: autonomous invocation is the platform default and not a unique concern for this skill.
Assessment
This skill simply tells the agent to forward whatever Feishu payloads it receives, verbatim, using the platform's message tool and then respond with NO_REPLY. Before enabling it: (1) ensure you trust the upstream skills or data sources that will produce messageToolCalls (they can cause the agent to send arbitrary content), (2) verify the message tool's configured Feishu account and permissions are appropriate, and (3) be aware the skill suppresses a human-facing reply (NO_REPLY), which can make sends silent. If you need user confirmation, request a change to the skill so it summarizes or prompts before sending.

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

latestvk9775ftxbxhfdqyf91b6kwegxn84080f
99downloads
0stars
1versions
Updated 3w ago
v1.0.0
MIT-0

Feishu Card Display

Use this skill when another tool returns:

  • displaySkill: "feishu-card-display"
  • messageToolCalls
  • Feishu card payloads

This skill has no Python tools. It only tells the agent how to use the existing OpenClaw message tool correctly.

Core Rule

If upstream output says displaySkill: "feishu-card-display", you MUST:

  1. Execute each returned messageToolCalls item in order
  2. Use the OpenClaw message tool for every send
  3. Preserve the payload exactly as returned
  4. After all sends finish, reply with NO_REPLY

Do not:

  • merge multiple product cards into one assistant bubble
  • rewrite the text payload
  • summarize what the cards contain
  • explain the payload structure to the user

Feishu Sending Rules

Card payload

When a call contains:

{
  "action": "send",
  "channel": "feishu",
  "card": { "...": "..." }
}

send it with the message tool as a Feishu card send. Keep the card object unchanged.

Text payload

When a call contains:

{
  "action": "send",
  "channel": "feishu",
  "message": "..."
}

send the text exactly as provided.

Media payload

When a call contains:

{
  "action": "send",
  "channel": "feishu",
  "filePath": "/path/to/file",
  "message": ""
}

send the file as media using the message tool, then continue with later calls.

Image Key Notes

If upstream payload already contains Feishu-ready card payloads or image keys, use them as-is. If upstream payload only contains preview links, keep the preview links as-is. This skill does not invent image keys and does not rewrite card media.

Final Reply

After all upstream messageToolCalls are executed, the assistant must reply with:

NO_REPLY

Version Marker: feishu-card-display@1.0.0

Comments

Loading comments...