feishu-perm
Feishu permission management for documents and files. Activate when user mentions sharing, permissions, collaborators.
85
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
75%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 has good structure with explicit 'what' and 'when' components, and the Feishu-specific context provides clear distinctiveness. However, it lacks specific concrete actions (what permission operations can be performed) and could benefit from additional natural trigger terms users might use when requesting permission-related help.
Suggestions
Add specific actions like 'grant access, revoke permissions, add collaborators, set view/edit rights, manage sharing links'
Expand trigger terms to include variations like 'access', 'invite', 'share link', 'who can see', 'view-only', 'edit access'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Feishu permission management) and general scope (documents and files), but lacks specific concrete actions like 'grant access', 'revoke permissions', 'add collaborators', or 'set view/edit rights'. | 2 / 3 |
Completeness | Clearly answers both what (Feishu permission management for documents and files) and when (Activate when user mentions sharing, permissions, collaborators) with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes some relevant keywords ('sharing', 'permissions', 'collaborators') but misses common variations users might say like 'access', 'share link', 'invite', 'view-only', 'edit access', or 'who can see'. | 2 / 3 |
Distinctiveness Conflict Risk | The Feishu-specific context combined with permission-focused triggers creates a clear niche that is unlikely to conflict with generic document or file management skills. | 3 / 3 |
Total | 10 / 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 Feishu permission management. The reference tables are efficient and the examples are executable. The main weakness is the lack of validation steps for these sensitive permission operations—no guidance on verifying changes or handling errors.
Suggestions
Add a verification step after add/remove operations (e.g., 'After adding a collaborator, use the list action to confirm the permission was applied correctly')
Include error handling guidance or common failure scenarios for permission operations
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, using tables for reference data and minimal prose. No unnecessary explanations of what permissions are or how APIs work—assumes Claude's competence throughout. | 3 / 3 |
Actionability | Provides complete, copy-paste ready JSON examples for all three actions (list, add, remove). The examples include realistic tokens and member IDs, making them immediately executable. | 3 / 3 |
Workflow Clarity | Actions are clearly documented individually, but there's no validation/verification guidance for these permission operations. For sensitive operations like permission management, missing feedback loops (e.g., 'verify the collaborator was added by listing again') caps this at 2. | 2 / 3 |
Progressive Disclosure | For a skill under 50 lines with no need for external references, the content is well-organized with clear sections (Actions, Token Types, Member Types, Permission Levels, Examples, Configuration). Easy to navigate and find specific information. | 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.