feishu-doc
Feishu document read/write operations. Activate when user mentions Feishu docs, cloud docs, or docx links.
Install with Tessl CLI
npx tessl i github:qsimeon/openclaw-engaging --skill feishu-doc92
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillEvaluation — 100%
↑ 1.85xAgent success when using this skill
Validation for skill structure
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a solid skill description with clear trigger guidance and good distinctiveness for the Feishu platform. The main weakness is the vague 'read/write operations' which could be more specific about concrete capabilities like creating, editing, formatting, or extracting content from documents.
Suggestions
Expand 'read/write operations' to list specific actions like 'create documents, edit content, extract text, manage permissions, format sections'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Feishu documents) and mentions 'read/write operations' as actions, but doesn't list specific concrete actions like 'create documents, edit content, extract text, format sections'. | 2 / 3 |
Completeness | Explicitly answers both what ('Feishu document read/write operations') and when ('Activate when user mentions Feishu docs, cloud docs, or docx links') with clear trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes good natural trigger terms users would say: 'Feishu docs', 'cloud docs', 'docx links'. These cover the product name and common variations users might mention. | 3 / 3 |
Distinctiveness Conflict Risk | Clearly targets Feishu-specific documents with distinct triggers like 'Feishu docs' and 'cloud docs'. Unlikely to conflict with generic document skills or other platform-specific skills. | 3 / 3 |
Total | 11 / 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 high-quality API reference skill that excels at conciseness and actionability. Every action has executable JSON examples with realistic values and clear parameter documentation. The main weakness is the lack of validation/verification steps for destructive operations like full document replacement and block deletion.
Suggestions
Add a validation step after 'write' action (e.g., 'After write, use read action to verify content was applied correctly')
Include a warning or confirmation pattern for destructive operations like delete_block and write (replace all)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean and efficient. No unnecessary explanations of what Feishu is or how APIs work. Every section provides only the essential JSON examples and brief notes. Token extraction example is minimal yet clear. | 3 / 3 |
Actionability | Fully actionable with copy-paste ready JSON examples for every action. Each operation has concrete, executable payloads with realistic field values. Optional parameters and edge cases are clearly noted. | 3 / 3 |
Workflow Clarity | The 'Reading Workflow' section provides a clear 3-step sequence, but lacks validation checkpoints for write operations. Destructive actions like 'write' (replace all) and 'delete_block' have no verification steps or rollback guidance. | 2 / 3 |
Progressive Disclosure | Well-organized with clear sections for each action type. Content is appropriately structured in a single file given its reference nature. Cross-references to feishu_wiki dependency and configuration are clearly signaled. | 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.
- 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.