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 is too vague on capabilities, offering only 'file management' without specifying concrete actions. While it includes an explicit trigger clause and the 'Feishu' qualifier adds some distinctiveness, the lack of specific actions and limited trigger terms weaken its effectiveness for skill selection among many options.
Suggestions
List specific concrete actions such as 'create folders, upload files, move files, list contents, manage permissions' to replace the vague 'file management'.
Expand trigger terms to include more natural user phrases like 'upload to Feishu', 'Feishu drive', 'cloud files', 'file sharing', 'storage space', or Chinese equivalents if applicable.
Add more context to the 'when' clause to differentiate from other cloud storage skills, e.g., 'Use when user needs to manage files in Feishu cloud storage, including creating folders, uploading, downloading, or organizing files in Feishu drive.'
| 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 'what' is insufficiently detailed. | 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-specific terms. The term 'Feishu' helps narrow the domain. | 2 / 3 |
Distinctiveness Conflict Risk | 'Feishu' provides some distinctiveness from generic file management skills, but 'cloud storage file management' and triggers like 'folders' and 'drive' could overlap with other cloud storage skills (Google Drive, OneDrive, etc.). | 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-structured, concise skill that provides actionable JSON examples for each drive operation. Its main weakness is the lack of validation/verification steps for destructive operations (delete, move), and no guidance on error recovery or confirming success. The Known Limitations section about bot access is a valuable addition that prevents common pitfalls.
Suggestions
Add a verification step after delete and move operations (e.g., 'After deleting, use `list` on the parent folder to confirm the file is removed')
Consider adding a brief workflow example for a common multi-step scenario like 'find a file and move it to a new folder' showing the sequence of actions with validation
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. Every section serves a purpose—no explanations of what cloud storage is or how APIs work. The JSON examples are minimal and the file type table is a compact reference. | 3 / 3 |
Actionability | Provides concrete, copy-paste ready JSON payloads for every action. Token extraction from URLs is shown with a clear example. File types are enumerated explicitly, and configuration is given in exact YAML format. | 3 / 3 |
Workflow Clarity | Actions are clearly listed individually, but there's no validation or error-handling guidance for destructive operations like delete and move. The 'Known Limitations' section about bots is helpful but the delete action lacks any confirmation/verification step, which should cap this at 2. | 2 / 3 |
Progressive Disclosure | For a skill of this size (~80 lines), the content is well-organized into logical sections (actions, file types, configuration, permissions, limitations) with clear headers. No need for external file 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.
- Repository
- attilaczudor/Test
- Commit
b3cef5f
- 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.