Feishu Fallback

What This Skill Does

The Feishu Fallback skill is a resilient messaging utility designed for the OpenClaw AI ecosystem to ensure that critical communications reach their destination even when primary formatting methods fail. Developed by 2233admin, this skill acts as a middleware wrapper for Feishu (Lark) API interactions. It intelligently handles common messaging errors—such as unsupported markdown formatting, invalid card structures, or API-level content rejection—by automatically cascading the message through a predefined hierarchy of formats. By attempting rich text first, then falling back to cards, and finally resolving to plain text, it guarantees high delivery rates without requiring manual intervention from the end user.

Installation

To integrate this skill into your environment, run the following command within your terminal or OpenClaw interface:

clawhub install openclaw/skills/skills/2233admin/feishu-fallback

Ensure that you have appropriate API permissions configured for your Feishu application bot, as the skill will rely on existing messaging scopes to perform these operations.

Use Cases

This skill is ideal for teams relying on OpenClaw to broadcast automated reports or alerts into Feishu groups. It is particularly useful when the generated output contains dynamic content that might occasionally breach Feishu's strict schema requirements. Instead of failing silently or throwing a hard error, the skill ensures the core information is delivered as plain text, maintaining business continuity.

Example Prompts

1. "Send the system status report to the DevOps channel, use Feishu Fallback if the rich text formatting isn't supported."
2. "Broadcast the Q3 marketing update to the team; trigger feishuformaterror handling if the card template fails to render."
3. "Deliver the raw server logs to my manager via Feishu; if markdown_render_failed occurs, just send it as a clean text block."

Tips & Limitations

To maximize effectiveness, ensure that your stripMarkdown utility is correctly configured, as the final fallback relies on producing a clean string. Note that this skill is reactive; it operates on an exception-handling loop. While it provides high reliability, it may slightly increase message latency due to the serial try-catch execution flow. We recommend using this for non-critical formatting where the content delivery is prioritized over visual aesthetic.