feishu-troubleshoot

飞书插件问题排查工具。包含常见问题 FAQ 和深度诊断命令（/feishu_doctor）。常见问题可随时查阅。诊断命令用于排查复杂问题（多次授权仍失败、自动授权无法解决等），会检查账户配置、API 连通性、应用权限、用户授权状态，并生成详细的诊断报告和解决方案。

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./资料/feishu-openclaw-plugin/package/skills/feishu-troubleshoot/SKILL.md

Quality

Content

65%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is lean and well-structured for a simple skill, but the diagnostic section is more descriptive than actionable and the FAQ workflow lacks validation checkpoints for its consequential publish step. These gaps keep actionability and workflow clarity at the midpoint.

Suggestions

Convert the diagnostic section from a description of what /feishu_doctor checks into concrete, executable guidance Claude can follow (or clearly mark it as user-facing content not intended for Claude to act on).

Add a validation/checkpoint step to the FAQ publish workflow (e.g., verify the new app version is live before confirming resolution) to support the consequential publish operation.

Include an explicit feedback loop for the diagnostic flow (run /feishu doctor → read the summary → apply the indicated fix → re-run to confirm) to lift workflow clarity above 3.

Dimension	Reasoning	Score
Conciseness	The body is efficient and well-organized with minimal padding, assuming the reader understands Feishu concepts; only minor instances (the long bullet list of what diagnostics checks) could be trimmed, matching the 'efficient; minor over-explanation' anchor.	4 / 5
Actionability	The FAQ gives concrete numbered steps with a URL and menu path, but the diagnostic section largely describes what the command checks rather than giving Claude executable instructions to act on, leaving guidance incomplete and fitting the 3 anchor.	3 / 5
Workflow Clarity	The FAQ has a clear sequence (登录→选择应用→修改配置→创建版本→提交审核→发布) but there are no validation checkpoints or feedback loops, and publishing app versions is a consequential operation; per the destructive/batch cap, this cannot exceed 3.	3 / 5
Progressive Disclosure	The skill is under 50 lines with no bundle files and is cleanly split into well-signaled FAQ and diagnostic sections, so the simple-skill exception applies and structure earns a 5.	5 / 5
	Total	15 / 20 Passed

Description

78%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific and distinct, clearly identifying the Feishu plugin troubleshooting niche with concrete capabilities and trigger conditions. The main gap is the absence of an explicit 'Use when...' clause and a few natural trigger synonyms, which keeps completeness and trigger quality at 4 rather than 5.

Suggestions

Add an explicit 'Use when...' clause (e.g., 'Use when troubleshooting Feishu plugin issues, especially repeated authorization failures') to lift completeness to 5.

Include more natural trigger synonyms users might say (e.g., '飞书授权失败', 'Feishu plugin not working') to broaden trigger-term coverage.

Tighten the capability list into a single crisp sentence so the what/when pairing reads as cleanly as the 5-anchor example.

Dimension	Reasoning	Score
Specificity	Names the domain and several concrete actions ('检查账户配置、API 连通性、应用权限、用户授权状态' plus '生成详细的诊断报告和解决方案'), with only minor coverage gaps, matching the 'several specific actions; minor gaps' anchor.	4 / 5
Completeness	Clearly states both what ('常见问题 FAQ 和深度诊断命令') and when ('诊断命令用于排查复杂问题（多次授权仍失败、自动授权无法解决等）'); the 'when' is explicit with concrete triggers but lacks a clean 'Use when...' phrasing, matching the 4 anchor rather than 5.	4 / 5
Trigger Term Quality	Includes natural terms a user would say ('飞书插件', '问题排查', '多次授权仍失败', '自动授权') and the /feishu_doctor trigger; good keyword coverage but a few natural synonyms/variations are missing, fitting the 'good coverage; a few natural terms missing' anchor.	4 / 5
Distinctiveness Conflict Risk	A clear niche (飞书插件 troubleshooting) with distinct triggers (/feishu_doctor, 授权失败) and minimal overlap with other skills, matching the 'clear niche with distinct triggers; minimal conflict risk' anchor.	5 / 5
	Total	17 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: op7418/CodePilot
Path: 资料/feishu-openclaw-plugin/package/skills/feishu-troubleshoot/SKILL.md
Commit: ff26f22

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.