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 specificity about what concrete actions the skill performs beyond vague 'navigation'. It does include an explicit trigger clause which is positive, but the 'what' portion needs significantly more detail about specific capabilities. The Feishu branding provides some distinctiveness but the generic terms risk overlap with other documentation skills.
Suggestions
Add specific concrete actions such as 'Browse Feishu wiki spaces, search knowledge base articles, retrieve document content, and follow wiki links to related pages'.
Expand trigger terms to include natural variations like 'Feishu wiki', 'Feishu docs', 'knowledge base article', 'wiki space', 'wiki page', or Feishu-specific terminology users might use.
Strengthen the 'what' portion by describing the types of outputs or results the skill provides (e.g., 'returns article content, lists wiki nodes, resolves wiki links to document IDs').
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description says 'knowledge base navigation' which is vague. It does not list any concrete actions like 'search articles', 'retrieve documents', 'browse wiki pages', or 'follow wiki links'. 'Navigation' is abstract. | 1 / 3 |
Completeness | It has a weak 'what' (knowledge base navigation) and an explicit 'when' clause ('Activate when user mentions knowledge base, wiki, or wiki links'). However, the 'what' is too vague to fully satisfy completeness, though the 'when' clause prevents it from being a 1. | 2 / 3 |
Trigger Term Quality | Includes some relevant keywords like 'knowledge base', 'wiki', and 'wiki links', but misses natural variations users might say such as 'Feishu wiki', 'docs', 'articles', 'knowledge base search', or specific Feishu terminology. | 2 / 3 |
Distinctiveness Conflict Risk | Mentioning 'Feishu' provides some distinctiveness, but 'knowledge base' and 'wiki' are generic terms that could overlap with other wiki or documentation skills. The Feishu-specific context helps somewhat but the actions are too vague to clearly carve out a niche. | 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-structured, concise API reference skill that provides clear, actionable JSON examples for each wiki operation. Its main weakness is the lack of validation/verification steps in workflows—particularly for destructive operations like move and create. The progressive disclosure is adequate for the skill's size but could benefit from linking to feishu_doc documentation.
Suggestions
Add a verification step after move/create operations (e.g., 'Verify: get the node to confirm it was moved/created successfully') to improve workflow safety.
Add a brief note or link to feishu_doc skill documentation so users can navigate to the related tool's capabilities without searching.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every section is lean and purposeful. No unnecessary explanations of what a wiki or knowledge base is. Token extraction is shown by example in one line. JSON payloads are minimal and illustrative. | 3 / 3 |
Actionability | All actions are shown with concrete, copy-paste-ready JSON payloads. Parameters are clearly demonstrated with variations (e.g., with/without parent). The wiki-doc workflow gives exact tool calls with specific parameter names. | 3 / 3 |
Workflow Clarity | The Wiki-Doc Workflow section provides a clear 3-step sequence for editing wiki pages, but lacks validation or error handling steps. For operations like move/create that could fail or have side effects, there are no verification checkpoints (e.g., confirming the move succeeded or checking node existence before operating). | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear sections and headers, but everything is inline in a single file. The configuration and permissions sections could be separated, and there's no reference to external docs for advanced usage or the feishu_doc tool's capabilities. However, for a skill of this size (~80 lines), the inline approach is reasonable. | 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
- qsimeon/openclaw-engaging
- Commit
4467e04
- 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.