feishu-doc
Feishu document read/write operations. Activate when user mentions Feishu docs, cloud docs, or docx links.
87
84%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Quality
Discovery
82%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 functional and covers the basics well, with explicit trigger guidance and relevant keywords. Its main weakness is the lack of specific concrete actions beyond the generic 'read/write operations', and some trigger terms like 'cloud docs' and 'docx links' could cause overlap with other document skills.
Suggestions
Expand the capability description with specific actions, e.g., 'Create, read, update, and delete Feishu documents, retrieve document content, and manage block elements.'
Qualify the potentially overlapping trigger terms to reduce conflict risk, e.g., 'Feishu cloud docs' instead of just 'cloud docs', or add a note like 'Not for Google Docs or general .docx files.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Feishu documents) and mentions 'read/write operations' as actions, but does not list specific concrete actions like 'create documents, update content, extract text, manage permissions'. | 2 / 3 |
Completeness | Clearly answers both 'what' (Feishu document read/write operations) and 'when' (explicitly states 'Activate when user mentions Feishu docs, cloud docs, or docx links'). | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'Feishu docs', 'cloud docs', 'docx links'. These are terms a user working with Feishu would naturally mention, covering common variations. | 3 / 3 |
Distinctiveness Conflict Risk | 'Cloud docs' and 'docx links' could overlap with other document-related skills (e.g., Google Docs, general document processing). 'Feishu' is distinctive, but the other trigger terms introduce some conflict risk. | 2 / 3 |
Total | 10 / 12 Passed |
Implementation
87%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-crafted skill that is concise, actionable, and well-structured. Each action is documented with executable JSON examples and the content respects Claude's intelligence throughout. The main weakness is the lack of validation or confirmation steps for destructive operations like write (full replace) and delete_block, which could lead to data loss.
Suggestions
Add a validation/confirmation workflow for destructive operations (write replaces entire document, delete_block) — e.g., recommend reading before writing to confirm the target, or checking the response status after write operations.
Consider adding a brief 'Writing Workflow' section parallel to the Reading Workflow that includes a read-before-write verification step to prevent accidental content loss.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every section is lean and purposeful. No unnecessary explanations of what Feishu is or how APIs work. Token extraction is shown by example rather than explained verbally. The markdown limitation is noted concisely. | 3 / 3 |
Actionability | Each action has a concrete, copy-paste-ready JSON example with the exact parameter structure. Return values are briefly described, and supported markdown features are enumerated. The tool invocation format is unambiguous. | 3 / 3 |
Workflow Clarity | The 'Reading Workflow' section provides a clear 3-step sequence with a conditional branch, but there are no validation/error-handling steps for write operations (which replace entire documents — a destructive operation). Missing feedback loops for destructive write/delete actions caps this at 2. | 2 / 3 |
Progressive Disclosure | For a skill of this size (~80 lines), the content is well-organized with clear section headers. Actions are individually documented, the reading workflow is separated out, and configuration/permissions are appropriately placed at the end. No need for external file references at this length. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- Hung-Reo/hungreo-openclaw
- Commit
a5bf5e0
- Reviewed
Table of Contents
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.