feishu-drive
Feishu cloud storage file management. Activate when user mentions cloud space, folders, drive.
82
72%
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
57%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 provides a clear 'when to use' clause with explicit triggers, which is good for completeness. However, it is weak on specificity—listing no concrete actions beyond the vague 'file management'—and the trigger terms, while present, are too generic and could conflict with other cloud storage skills. Adding specific actions and more distinctive trigger terms would significantly improve this description.
Suggestions
Add specific concrete actions such as 'create folders, upload files, list contents, move or delete files in Feishu cloud storage'.
Expand trigger terms with more natural user phrases like 'Feishu drive', 'Feishu files', 'upload to Feishu', 'cloud documents', or 'Feishu storage'.
Differentiate from generic cloud storage skills by emphasizing Feishu-specific features or API capabilities.
| 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 explicitly answers both 'what' (Feishu cloud storage file management) and 'when' ('Activate when user mentions cloud space, folders, drive'), meeting the requirement for explicit trigger guidance. | 3 / 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 sharing'. The term 'Feishu' is specific but 'drive' and 'folders' are generic. | 2 / 3 |
Distinctiveness Conflict Risk | 'Feishu' provides some distinctiveness, but 'file management', 'folders', and 'drive' are generic terms that could easily overlap with other file management or cloud storage skills (e.g., Google Drive, OneDrive). | 2 / 3 |
Total | 8 / 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, concise skill that provides clear, actionable JSON examples for each Feishu Drive operation. Its main weakness is the lack of validation/verification guidance for destructive operations (delete, move) and no explicit workflow for multi-step scenarios like browsing then acting on files. The known limitations section about bot access is a valuable addition that prevents common errors.
Suggestions
Add a validation/confirmation step or warning pattern for destructive operations (delete, move), e.g., 'Before deleting, use `info` to verify the correct file, then proceed with `delete`.'
Add a brief multi-step workflow example showing a common sequence like: list folder → find file → get info → move/delete, with explicit checkpoints.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. It assumes Claude knows what Feishu is and how JSON actions work. Every section serves a purpose—token extraction, action examples, type reference, config, permissions, and known limitations. No unnecessary explanations. | 3 / 3 |
Actionability | Each action has a concrete, copy-paste-ready JSON example with the exact parameters needed. The file types table, configuration YAML, and permission scopes are all specific and directly usable. | 3 / 3 |
Workflow Clarity | Actions are clearly documented individually, but there's no explicit workflow sequence or validation checkpoints for destructive operations like delete and move. The 'Known Limitations' section about bots provides a workaround but lacks a step-by-step recovery flow. Missing validation steps for delete/move operations caps this at 2. | 2 / 3 |
Progressive Disclosure | For a skill of this size and scope (single tool with multiple actions), the content is well-organized into logical sections (actions, file types, config, permissions, limitations) without being monolithic. No bundle files are needed, and the structure is easy to navigate. | 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
- deepgram/dglabs-deepclaw
- Commit
ec8d4f8
- 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.