feishu-drive
Feishu cloud storage file management. Activate when user mentions cloud space, folders, drive.
76
63%
Does it follow best practices?
Impact
99%
1.70xAverage score across 3 eval scenarios
Risky
Do not use without reviewing
Optimize this skill with Tessl
npx tessl skill review --optimize ./extensions/feishu/skills/feishu-drive/SKILL.mdQuality
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.
The description identifies the platform (Feishu) and provides a basic 'when' clause, which is positive. However, it is too vague on specific capabilities—'file management' tells Claude very little about what actions are available. The trigger terms are limited and could overlap with other storage-related skills.
Suggestions
List specific concrete actions such as 'create folders, upload files, move files, list contents, manage permissions' instead of the generic 'file management'.
Expand trigger terms to include natural user phrases like 'upload to Feishu', 'share file', 'list files', 'Feishu drive', 'cloud storage', 'file permissions'.
Strengthen the 'when' clause with more specific scenarios, e.g., 'Use when user needs to create, move, list, or manage files and folders in Feishu cloud storage.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description says 'file management' which is vague. It does not list specific concrete actions like uploading, downloading, creating folders, moving files, sharing, etc. | 1 / 3 |
Completeness | It has a weak 'what' (file management) and an explicit 'when' clause ('Activate when user mentions cloud space, folders, drive'), but the 'what' is too vague to score a 3. The 'when' clause exists but the trigger terms are limited. | 2 / 3 |
Trigger Term Quality | Includes some relevant keywords ('cloud space', 'folders', 'drive') but misses common variations like 'upload', 'download', 'share files', 'storage', 'Feishu drive', or file-related terms users would naturally say. | 2 / 3 |
Distinctiveness Conflict Risk | 'Feishu cloud storage' provides some specificity to a platform, but 'file management', 'folders', and 'drive' are generic terms that could overlap with other file/storage management 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 single tool with multiple actions. The JSON examples are concrete and actionable, and the content respects Claude's intelligence by avoiding unnecessary explanations. The main weakness is the lack of validation/verification guidance for destructive operations (delete, move), which would benefit from explicit checkpoints or confirmation patterns.
Suggestions
Add a brief workflow or validation note for destructive operations (delete, move) — e.g., recommend listing/confirming the file exists before deleting, or verifying the move succeeded by listing the target folder afterward.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. It doesn't explain what Feishu Drive is or how cloud storage works. Every section provides only the necessary information—action JSON schemas, type tables, and configuration. The Known Limitations section earns its place by documenting a non-obvious bot behavior. | 3 / 3 |
Actionability | Each action has a concrete, copy-paste-ready JSON example with the exact parameters needed. The file types table, permission scopes, and configuration YAML are all specific and directly usable. The token extraction example shows exactly how to derive tokens from URLs. | 3 / 3 |
Workflow Clarity | The individual actions are clear, but there's no explicit workflow sequencing for multi-step operations. For destructive operations like delete and move, there are no validation checkpoints or confirmation steps. The info action note about needing to 'list' first hints at a workflow but doesn't formalize it. | 2 / 3 |
Progressive Disclosure | For a skill of this size and scope (single tool with multiple actions), the content is well-organized with clear sections. No bundle files are provided, and none seem necessary—the content is appropriately self-contained without being a monolithic wall of text. | 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.