Feishu permission management for documents and files. Activate when user mentions sharing, permissions, collaborators.
87
81%
Does it follow best practices?
Impact
96%
1.26xAverage score across 3 eval scenarios
Risky
Do not use without reviewing
Quality
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.
The description establishes a clear niche (Feishu permission management) and includes explicit trigger guidance, which are strengths. However, it lacks specificity in the concrete actions it performs and could benefit from more natural trigger term variations that users might use when requesting permission-related tasks.
Suggestions
Add specific concrete actions such as 'grant access, revoke permissions, list collaborators, change permission levels' to improve specificity.
Expand trigger terms to include common variations like 'access control', 'invite', 'share a doc', 'read-only', 'edit access' to improve keyword coverage.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Feishu permission management) and mentions documents/files, but doesn't list specific concrete actions like granting access, revoking permissions, listing collaborators, or changing permission levels. | 2 / 3 |
Completeness | 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 like 'access control', 'share a doc', 'invite', 'read-only', 'edit access', or 'Feishu docs'. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of 'Feishu' and 'permission management' creates a clear niche that is unlikely to conflict with other skills, as it targets a specific platform and a specific function. | 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 clear, actionable JSON examples for Feishu permission management. Its main weakness is the lack of workflow guidance around verification steps—e.g., confirming a collaborator was successfully added/removed, or listing before removing to validate the target exists. For a sensitive operation like permission management, explicit validation checkpoints would strengthen the skill.
Suggestions
Add a recommended workflow sequence (e.g., list collaborators first to verify state, then add/remove, then list again to confirm the change took effect) with explicit validation checkpoints.
Include brief error handling guidance—what common errors look like and how to respond (e.g., invalid token, member not found, insufficient permissions).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. Every section serves a clear purpose—action examples, reference tables for types/members/permissions, and configuration. No unnecessary explanations of what permissions are or how APIs work. | 3 / 3 |
Actionability | Provides fully concrete, copy-paste ready JSON payloads for each action (list, add, remove), complete with realistic token values and field names. The reference tables give all valid enum values needed to construct requests. | 3 / 3 |
Workflow Clarity | The three actions are clearly presented individually, but there's no guidance on sequencing (e.g., list before removing to verify collaborators exist), no validation/verification steps after add/remove operations, and no error handling guidance for a sensitive permission management operation. | 2 / 3 |
Progressive Disclosure | For a single-purpose skill with no bundle files, the content is well-organized with clear sections (Actions, Token Types, Member Types, Permission Levels, Examples, Configuration). The structure is flat and easy to navigate without needing external references. | 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.
ec8d4f8
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.