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:Hung-Reo/hungreo-openclaw --skill feishu-doc91
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/skillValidation 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 description is functional with good trigger terms and explicit 'when to use' guidance. 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 Feishu documents.
Suggestions
Replace 'read/write operations' with specific actions like 'create, edit, read, and format Feishu documents' to improve specificity
| 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', etc. | 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 natural keywords users would say: 'Feishu docs', 'cloud docs', 'docx links'. These are realistic terms users would mention when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | Clearly targets Feishu-specific documents with distinct triggers ('Feishu docs', 'cloud docs', 'docx links'). Unlikely to conflict with generic document or other cloud platform 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 well-crafted skill document that efficiently documents a tool API with concrete JSON examples for every action. The content is appropriately concise and highly actionable. The main weakness is the lack of error handling guidance and validation steps for write/delete operations, which are potentially destructive.
Suggestions
Add error handling guidance for write/delete operations (e.g., what errors might occur, how to verify success)
Include a validation step in write workflows (e.g., 'After write, use read action to verify content was applied correctly')
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean and efficient. No unnecessary explanations of what Feishu is or how APIs work. Every section delivers actionable information with minimal prose. | 3 / 3 |
Actionability | All actions have complete, copy-paste ready JSON examples. Token extraction pattern is concrete. Limitations (markdown tables not supported) are explicitly stated. | 3 / 3 |
Workflow Clarity | The 'Reading Workflow' section provides a clear 3-step sequence, but lacks validation/error handling guidance. No feedback loops for write operations or guidance on what to do if operations fail. | 2 / 3 |
Progressive Disclosure | Well-organized with clear sections. Appropriate length for a single SKILL.md file (~80 lines). Configuration and permissions are properly separated at the end. No need for external references given the scope. | 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.