feishu-troubleshoot
The feishu-troubleshoot skill provides diagnostic tools for resolving Feishu (Lark) plugin issues, particularly those related to message card interactions and permissions. Use this skill when card buttons are unresponsive, when standard authorization flows fail repeatedly, or when troubleshooting complex permission problems. The `/feishu doctor` command generates comprehensive diagnostics including credential status, required application permissions, user authorization states, and provides automated links for permission requests and reauthorization.
git clone --depth 1 https://github.com/nexu-io/nexu /tmp/feishu-troubleshoot && cp -r /tmp/feishu-troubleshoot/nexu-skills/skills/feishu-troubleshoot ~/.claude/skills/feishu-troubleshootSKILL.md
# 飞书插件问题排查 ## ❓ 常见问题(FAQ) ### 卡片按钮点击无反应 **现象**:点击卡片按钮后没有任何反应,然后提示报错. **原因**:应用未开通「消息卡片回传交互」权限。 **解决步骤**: 1. 登录飞书开放平台:https://open.feishu.cn/app 2. 选择您的应用 → **事件与回调** 3. 在回调配置中,修改订阅方式为"长链接"并添加回调 "卡片回传交互"(card.action.trigger) 4. 创建应用版本 → 提交审核 → 发布 --- ## 🔍 诊断命令(深度工具) **注意**:诊断命令仅用于排查复杂/疑难的**权限相关问题**。常规权限问题会自动触发授权流程,无需手动诊断。 **何时使用诊断**: - 多次授权后仍然报错 - 自动授权流程无法解决的问题 - 需要查看完整的权限配置状态 **使用方法**: 在飞书聊天会话中直接输入(作为用户消息发送): /feishu doctor 诊断命令会检查: - **📋 诊断摘要**(首先展示): - 总体状态(✅ 正常 / ⚠️ 警告 / ❌ 失败) - 发现的问题列表和简要描述 - **环境信息**: - 插件版本 - **账号信息**: - 凭证完整性(appId, appSecret 掩码) - 账户启用状态 - API 连通性测试 - Bot 信息(名称和 openId) - **应用身份权限**: - 应用已开通的必需权限数量 - 缺失的必需权限列表 - 一键申请链接(自动带上缺失权限参数) - **用户身份权限**: - 用户授权状态统计(✓ 有效 / ⟳ 需刷新 / ✗ 已过期) - Token 自动刷新状态(是否包含 offline_access) - 权限对照表(应用已开通 vs 用户已授权,逐项对比) - 应用权限缺失时的申请指引和链接 - 用户授权不足时的重新授权操作方法
Use the ClawHub CLI to search, install, update, and publish agent skills from clawhub.com. Use when you need to fetch new skills on the fly, sync installed skills to latest or a specific version, or publish new/updated skill folders with the npm-installed clawhub CLI.
Delegate coding tasks to Codex, Claude Code, or Pi agents via background process. Use when: (1) building/creating new features or apps, (2) reviewing PRs (spawn in temp dir), (3) refactoring large codebases, (4) iterative coding that needs file exploration. NOT for: simple one-liner fixes (just edit), reading code (use read tool), thread-bound ACP harness requests in chat (for example spawn/run Codex or Claude Code in a Discord thread; use sessions_spawn with runtime:"acp"), or any work in ~/clawd workspace (never spawn agents here). Claude Code: use --print --permission-mode bypassPermissions (no PTY). Codex/Pi/OpenCode: pty:true required.
Use when the user says "check Datadog", "查 Datadog", "查日志", "check logs", "crash logs", "查 crash", "gateway crash", "查告警", "check alerts", "check metrics", or needs to investigate production issues via Datadog Logs API.
|
Send feedback to the Nexu team. Use when the user says /feedback followed by their message.
|
|
|