Feishu cloud storage file management. Activate when user mentions cloud space, folders, drive.
71
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.
The description identifies the platform (Feishu) and includes trigger guidance, which is positive. However, it fails to specify concrete actions beyond generic 'file management' and lacks comprehensive trigger terms that users would naturally use when working with cloud storage.
Suggestions
Add specific concrete actions like 'upload files, create folders, share documents, manage permissions, organize cloud storage'
Expand trigger terms to include common user phrases like 'upload', 'download', 'share files', 'storage space', 'file sharing', or Feishu-specific terminology
Clarify what distinguishes this from other cloud storage skills by mentioning Feishu-specific features or workflows
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description says 'file management' which is vague and abstract. It does not list any concrete actions like 'upload files', 'create folders', 'share documents', or 'organize files'. | 1 / 3 |
Completeness | Has a weak 'what' (file management) and does include an 'Activate when' clause with triggers, but the 'what' portion is too vague to fully satisfy completeness requirements. | 2 / 3 |
Trigger Term Quality | Includes some relevant keywords ('cloud space', 'folders', 'drive') but missing common variations users might say like 'upload', 'download', 'share', 'storage', 'files', or Feishu-specific terms. | 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, OneDrive, 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 with excellent conciseness and actionability. The JSON examples are concrete and immediately usable, and the file type reference table is helpful. The main weakness is the lack of explicit workflow guidance for common multi-step scenarios like navigating folder hierarchies or handling the bot permission limitations.
Suggestions
Add a brief workflow example showing how to navigate folders (list root → find folder → list subfolder → get file info) with explicit steps
Include error handling guidance for common failures like the 400 error when bots try to create folders without folder_token
| 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.
Table of Contents
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.