feishu-interactive-cards

What This Skill Does

The feishu-interactive-cards skill allows the OpenClaw AI agent to communicate via Feishu (Lark) using rich, interactive UI components rather than simple, passive text messages. By utilizing interactive cards, the agent can provide users with buttons, forms, polls, and checklists. This transforms the agent from a one-way broadcaster into a bidirectional interface, allowing for precise decision-making, task management, and data collection directly within the Feishu chat environment.

Installation

To integrate this skill into your environment, follow these steps:

1. Ensure you have the OpenClaw SDK installed.
2. Run the command: clawhub install openclaw/skills/skills/leecyang/feishu-interactive-cards.
3. Navigate to the local skill directory: cd E:\openclaw\workspace\skills\feishu-interactive-cards\scripts.
4. Initialize the long-polling server by executing: node card-callback-server.js. This component is critical as it enables the agent to listen for button clicks and form submissions via a persistent connection, bypassing the need for a public-facing IP address.

Use Cases

• Confirmation Flows: Whenever the agent is about to perform a destructive or irreversible action (e.g., deleting a file, clearing a database), use an interactive confirmation card to ensure user intent.
• Polls and Surveys: Easily gather team feedback or schedule meetings by embedding polls directly in the message stream.
• Task Management: Display todo lists where users can check off items, which updates the agent's internal state via the callback gateway.
• Complex Input: Replace multi-turn conversations with forms, allowing users to input multiple data fields in a single UI block.

Example Prompts

1. "Check if there are any pending tasks for the marketing team and display them in a checklist card in the Feishu channel."
2. "I'm about to purge the logs in the production folder. Send a confirmation card to the team lead before I proceed."
3. "Create a poll in the project channel asking the team to vote on the preferred time for our next sprint retrospective, offering 10am, 2pm, and 4pm as options."

Tips & Limitations

• Principle of Uncertainty: Always default to an interactive card if there is any ambiguity in user intent. It reduces errors and keeps the conversation flow logical.
• Template Management: Leverage the examples/ directory to build custom JSON card structures. For complex UI needs, refer to references/card-design-guide.md.
• Performance: Keep cards concise. Large forms can be overwhelming on mobile devices. If a workflow involves more than five fields, consider breaking it into multiple steps.
• Maintenance: Ensure the card-callback-server.js script is running in a managed process (like PM2) to ensure it stays online during system reboots.