feishu-perm
Feishu permission management for documents and files. Activate when user mentions sharing, permissions, collaborators.
Install with Tessl CLI
npx tessl i github:Hung-Reo/hungreo-openclaw --skill feishu-perm84
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
67%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 adequately covers the 'what' and 'when' with explicit trigger guidance, which is its main strength. However, it lacks specific concrete actions (what permission operations can be performed) and could benefit from more comprehensive trigger terms to better capture user intent and distinguish from similar skills on other platforms.
Suggestions
Add specific concrete actions like 'grant access, revoke permissions, add/remove collaborators, set view/edit rights'
Expand trigger terms to include variations like 'access', 'invite', 'share with', 'view access', 'edit access', 'who can see'
| 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 natural keywords ('sharing', 'permissions', 'collaborators') but misses common variations like 'access', 'share document', 'invite', 'view access', 'edit access', or Feishu-specific terms users might say. | 2 / 3 |
Distinctiveness Conflict Risk | Feishu-specific context helps distinguish it, but 'sharing' and 'permissions' are generic terms that could overlap with other document/file sharing skills for different platforms. | 2 / 3 |
Total | 9 / 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 and comprehensive reference tables. The main weakness is the lack of verification steps for permission operations—given that permission management is explicitly noted as sensitive, guidance on confirming changes were applied correctly would strengthen the workflow.
Suggestions
Add a verification step after add/remove operations, such as 'After modifying permissions, use the list action to confirm the change was applied correctly'
Consider noting what error responses look like so Claude can handle failures appropriately
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, using tables for reference data and minimal prose. No unnecessary explanations of what permissions or collaborators are—assumes Claude understands these concepts. | 3 / 3 |
Actionability | Provides complete, copy-paste ready JSON examples for all three actions (list, add, remove). Reference tables give all valid values for token types, member types, and permission levels. | 3 / 3 |
Workflow Clarity | Actions are clearly documented individually, but there's no validation/verification guidance for permission changes. For sensitive operations like permission management, a feedback loop (verify permissions after change) would be appropriate. | 2 / 3 |
Progressive Disclosure | For a skill of this scope (~80 lines), the content is well-organized with clear sections: Actions, Reference Tables, Examples, Configuration. No need for external files; everything is appropriately contained. | 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.