feishu-wiki
Feishu knowledge base navigation. Activate when user mentions knowledge base, wiki, or wiki links.
74
59%
Does it follow best practices?
Impact
100%
2.00xAverage score across 3 eval scenarios
Risky
Do not use without reviewing
Optimize this skill with Tessl
npx tessl skill review --optimize ./extensions/feishu/skills/feishu-wiki/SKILL.mdQuality
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 is minimal and lacks concrete actions — it only states 'navigation' without specifying what operations the skill performs (e.g., searching, retrieving, linking). While it does include an explicit trigger clause, the trigger terms are somewhat generic and the 'what' portion is too vague to confidently distinguish this skill or help Claude understand its full capabilities.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Searches Feishu knowledge base articles, retrieves wiki page content, resolves wiki links, and browses knowledge base hierarchies.'
Expand trigger terms to include natural variations like 'Feishu docs', 'Lark wiki', 'knowledge base article', 'wiki page', 'Feishu wiki link'.
Strengthen the 'what' portion to clearly describe capabilities beyond just 'navigation' so Claude can distinguish this from other documentation or wiki-related skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description says 'Feishu knowledge base navigation' which is vague — it names a domain but does not describe any concrete actions like 'search articles', 'retrieve pages', 'browse categories', etc. | 1 / 3 |
Completeness | It has a 'when' clause ('Activate when user mentions knowledge base, wiki, or wiki links') but the 'what' is extremely thin — 'navigation' is not a clear description of capabilities. The explicit trigger guidance prevents capping at 1, but the weak 'what' keeps it at 2. | 2 / 3 |
Trigger Term Quality | Includes some relevant trigger terms ('knowledge base', 'wiki', 'wiki links') but misses natural variations like 'Feishu docs', 'Feishu wiki', 'lark wiki', or specific actions users might request. Coverage is partial. | 2 / 3 |
Distinctiveness Conflict Risk | 'Knowledge base' and 'wiki' are fairly generic terms that could overlap with other wiki or documentation skills. The mention of 'Feishu' adds some specificity, but the triggers themselves are broad enough to cause conflicts. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
79%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, concise skill that provides highly actionable JSON examples for every operation. Its main weakness is the lack of validation/verification steps in workflows, particularly for destructive operations like move and create. The structure is clean and efficient, making good use of the single-file format.
Suggestions
Add a verification step after move/create operations (e.g., 'Verify: get the node to confirm it moved successfully') to improve workflow safety.
Consider adding brief error handling guidance for common failure cases (e.g., invalid token, permission denied, node not found).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every section is lean and purposeful. No unnecessary explanations of what a wiki is or how APIs work. Token extraction, actions, and configuration are all presented with minimal prose and maximum information density. | 3 / 3 |
Actionability | Each action includes concrete, copy-paste-ready JSON payloads with realistic parameter examples. The token extraction from URL is specific and immediately usable. The Wiki-Doc workflow provides exact tool calls with parameter names. | 3 / 3 |
Workflow Clarity | The Wiki-Doc Workflow section provides a clear 3-step sequence for the most common multi-step operation, but lacks validation or error handling steps. For operations like move and create that could be destructive or have side effects, there are no verification checkpoints (e.g., confirming the node exists before moving, or verifying the move succeeded). | 2 / 3 |
Progressive Disclosure | The content is well-organized with clear section headers and a logical progression from simple to complex operations. However, with no bundle files, there are no references to external documentation for advanced topics. The configuration and permissions sections are appropriately brief, but the document is somewhat long for a single file with no external references for deeper details. | 2 / 3 |
Total | 10 / 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.
- Repository
- deepgram/dglabs-deepclaw
- Commit
ec8d4f8
- 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.