feishu-wiki
Feishu knowledge base navigation. Activate when user mentions knowledge base, wiki, or wiki links.
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.
This description has a proper trigger clause structure but severely lacks specificity about what actions the skill performs. The term 'navigation' is too vague to help Claude understand the skill's capabilities. While it mentions Feishu to distinguish the platform, the generic wiki/knowledge base terms could cause conflicts with similar documentation tools.
Suggestions
Replace 'navigation' with specific concrete actions like 'Search articles, browse folders, retrieve page content, list recent updates' to clarify what the skill actually does.
Add more distinctive trigger terms specific to Feishu such as 'Feishu docs', 'Lark wiki', or specific Feishu terminology to reduce conflict with other wiki tools.
Expand the trigger terms to include common user phrasings like 'find documentation', 'look up in wiki', 'search knowledge base' for better matching.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language ('navigation') without listing concrete actions. It doesn't specify what operations can be performed - no mention of searching, reading, creating, editing, or any specific capabilities. | 1 / 3 |
Completeness | Has an explicit 'Activate when' clause addressing the 'when' question, but the 'what' is extremely weak - 'navigation' doesn't explain what the skill actually does with the knowledge base. | 2 / 3 |
Trigger Term Quality | Includes some relevant keywords ('knowledge base', 'wiki', 'wiki links') but missing common variations users might say like 'Feishu docs', 'documentation', 'articles', or Chinese terms if applicable. | 2 / 3 |
Distinctiveness Conflict Risk | Mentions 'Feishu' which provides some specificity, but 'knowledge base' and 'wiki' are generic terms that could overlap with other wiki/documentation skills (Confluence, Notion, etc.). | 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 that efficiently documents the feishu_wiki tool API. It excels at conciseness and actionability with clear JSON examples for every operation. The main weakness is the lack of validation steps in workflows, particularly for destructive operations like move and rename.
Suggestions
Add a validation/verification step to the Wiki-Doc Workflow (e.g., 'Verify changes: re-read the doc to confirm edits applied')
Consider adding error handling guidance for move/rename operations (e.g., what happens if target doesn't exist or permissions fail)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, providing only essential information. No unnecessary explanations of what wikis or knowledge bases are - it jumps straight to actionable API usage. | 3 / 3 |
Actionability | Every action includes copy-paste ready JSON examples with clear parameter specifications. The token extraction pattern and all API actions are fully concrete and executable. | 3 / 3 |
Workflow Clarity | The Wiki-Doc Workflow section provides a clear 3-step sequence, but lacks validation checkpoints. For operations like move/rename that could affect document organization, there's no verification step or error recovery guidance. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear sections for each action type. For a skill of this size (~80 lines), the structure is appropriate with logical groupings and no need for external file 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.
- 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.