feishu-troubleshoot

Original：🇨🇳 Chinese

Translated

Feishu Plugin Troubleshooting Tool. Includes frequently asked questions (FAQ) and in-depth diagnostic command (/feishu_doctor). FAQs can be accessed at any time. The diagnostic command is used to troubleshoot complex issues (such as repeated authorization failures, unresolved automatic authorization, etc.), which checks account configuration, API connectivity, application permissions, user authorization status, and generates detailed diagnostic reports and solutions.

2installs

Sourcelarksuite/openclaw-lark

Added on2026-03-18

NPX Install

npx skill4agent add larksuite/openclaw-lark feishu-troubleshoot

SKILL.md Content (Chinese)

View Translation Comparison →

Feishu Plugin Troubleshooting

❓ Frequently Asked Questions (FAQ)

Card Button Unresponsive

Symptom: No response after clicking the card button, followed by an error prompt.

Cause: The application has not enabled the "Card Callback Interaction" permission.

Resolution Steps:

Log in to Feishu Open Platform: https://open.feishu.cn/app
Select your application → Events & Callbacks
In callback settings, change the subscription method to "Long Polling" and add the callback "Card Callback Interaction" (card.action.trigger)
Create app version → Submit for review → Publish

🔍 Diagnostic Command (In-depth Tool)

Note: The diagnostic command is only used to troubleshoot complex/difficult permission-related issues. Regular permission issues will trigger the authorization process automatically, no manual diagnosis required.

When to Use Diagnosis:

Errors persist after multiple authorization attempts
Issues that cannot be resolved by the automatic authorization process
Need to view the complete permission configuration status

Usage:

Directly enter it in a Feishu chat session (send as a user message):

/feishu doctor

The diagnostic command will check:

📋 Diagnostic Summary (displayed first):
- Overall status (✅ Normal / ⚠️ Warning / ❌ Failed)
- List of detected issues and brief descriptions
Environment Information:
- Plugin version
Account Information:
- Credential integrity (masked appId, appSecret)
- Account activation status
- API connectivity test
- Bot information (name and openId)
Application Identity Permissions:
- Number of required permissions enabled for the application
- List of missing required permissions
- One-click application link (automatically includes parameters for missing permissions)
User Identity Permissions:
- Statistics of user authorization status (✓ Valid / ⟳ Need refresh / ✗ Expired)
- Token auto-refresh status (whether offline_access is included)
- Permission comparison table (enabled application permissions vs authorized user permissions, item-by-item comparison)
- Application guidelines and links when permissions are missing
- Re-authorization method when user authorization is insufficient