feishu-doc
Feishu document read/write operations. Activate when user mentions Feishu docs, cloud docs, or docx links.
87
81%
Does it follow best practices?
Impact
100%
1.85xAverage score across 3 eval scenarios
Passed
No known issues
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' could cause conflicts with other document skills.
Suggestions
Expand 'read/write operations' into specific actions, e.g., 'Create, read, update, and delete Feishu documents, retrieve document content, and manage document metadata.'
Qualify the generic trigger terms to reduce conflict risk, e.g., 'Feishu cloud docs' instead of just 'cloud docs', or add context like 'Feishu/Lark platform document links'.
| 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 cover the main variations a user might mention when working with Feishu documents. | 3 / 3 |
Distinctiveness Conflict Risk | 'Cloud docs' and 'docx links' could potentially overlap with other document-related skills (e.g., Google Docs, general document processing). 'Feishu' is distinctive, but the other trigger terms are somewhat generic. | 2 / 3 |
Total | 10 / 12 Passed |
Implementation
79%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 API reference skill with excellent conciseness and actionability — every action has concrete JSON examples and important caveats are noted succinctly. The main weaknesses are the lack of validation/error-handling guidance for destructive operations (write, delete) and the opportunity to split the lengthy action catalog into a more progressive disclosure structure.
Suggestions
Add validation/verification steps for destructive operations like 'write' (which replaces all content) and 'delete_block' — e.g., recommend reading the document first to confirm before overwriting, or checking block existence before deletion.
Consider splitting the detailed action reference (especially table and image operations) into a separate REFERENCE.md file, keeping SKILL.md as a quick-start overview with links to the full catalog.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. It avoids explaining what Feishu is or how APIs work in general. Every section provides only the necessary JSON payloads and brief notes about limitations or important behaviors. No unnecessary padding. | 3 / 3 |
Actionability | Every action includes a complete, copy-paste-ready JSON payload with concrete parameter examples. Key details like owner_open_id rationale, markdown table limitations, and image sizing notes are specific and actionable. | 3 / 3 |
Workflow Clarity | The Reading Workflow section provides a clear 3-step sequence, but there are no validation/error-handling steps for write operations (write replaces entire document, delete_block is destructive). Missing feedback loops for these destructive operations caps this at 2. | 2 / 3 |
Progressive Disclosure | The content is well-structured with clear headings and sections, but it's a fairly long monolithic file. The table-related actions and block manipulation actions could be split into separate reference files with links from the main skill. The configuration and permissions sections are appropriately brief. | 2 / 3 |
Total | 10 / 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
- qsimeon/openclaw-engaging
- Commit
4467e04
- 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.