feishu-drive
Feishu cloud storage file management. Activate when user mentions cloud space, folders, drive.
Install with Tessl CLI
npx tessl i github:Hung-Reo/hungreo-openclaw --skill feishu-drive75
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
40%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 identifies the platform (Feishu) and includes trigger guidance, which are positives. However, it fails to specify concrete actions the skill can perform and uses overly generic trigger terms that could conflict with other cloud storage skills. The description needs more specific capabilities and Feishu-specific terminology.
Suggestions
Add specific actions the skill can perform, e.g., 'Upload files, create folders, manage permissions, share documents, search cloud storage'
Include more Feishu-specific trigger terms like 'Feishu drive', 'Lark', '飞书', 'Feishu docs' to improve distinctiveness
Expand the trigger term list with common user phrases like 'upload to cloud', 'share file', 'storage space', 'file permissions'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language like 'file management' without listing concrete actions. It doesn't specify what operations can be performed (upload, download, organize, share, delete, etc.). | 1 / 3 |
Completeness | Has a 'when' clause ('Activate when...') which is good, but the 'what' portion is weak - 'file management' is too vague to understand the skill's actual capabilities. | 2 / 3 |
Trigger Term Quality | Includes some relevant keywords ('cloud space', 'folders', 'drive') but misses common variations users might say like 'files', 'storage', 'upload', 'download', 'share', or the Chinese term '飞书'. | 2 / 3 |
Distinctiveness Conflict Risk | 'Feishu' provides some distinctiveness from generic cloud storage skills, but 'cloud space, folders, drive' are generic terms that could overlap with Google Drive, Dropbox, or other cloud storage skills. | 2 / 3 |
Total | 7 / 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 efficiently documents a tool API with concrete examples and clear organization. The content excels at actionability and conciseness, providing exactly what Claude needs to use the feishu_drive tool. Minor improvement could be made by adding workflow guidance for common multi-step scenarios like 'find and move a file' or error handling patterns.
Suggestions
Add a brief workflow example showing a common multi-step operation (e.g., 'To move a file from one folder to another: 1. List source folder, 2. Note file_token and type, 3. Move with target folder_token')
Include error handling guidance for common failure cases beyond the bot root folder limitation
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, presenting only essential information without explaining concepts Claude already knows. Every section serves a clear purpose with minimal verbosity. | 3 / 3 |
Actionability | Provides concrete, copy-paste ready JSON examples for every action. Each operation has specific parameters and expected behavior clearly documented. | 3 / 3 |
Workflow Clarity | Actions are clearly documented individually, but lacks explicit workflow sequencing for multi-step operations. The 'info' action note about browsing folders first hints at a workflow but doesn't provide explicit validation steps or error recovery guidance. | 2 / 3 |
Progressive Disclosure | Well-organized with clear sections (Actions, File Types, Configuration, Permissions, Limitations). Content is appropriately structured for a single-file skill under 100 lines with logical groupings. | 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.