feishu-wiki

Feishu knowledge base navigation. Activate when user mentions knowledge base, wiki, or wiki links.

2.00x

Quality

59%

Does it follow best practices?

Impact

100%

2.00x

Average score across 3 eval scenarios

Securityby

Risky

Do not use without reviewing

Optimize this skill with Tessl

npx tessl skill review --optimize ./extensions/feishu/skills/feishu-wiki/SKILL.md

Quality

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 too vague about what the skill actually does — 'navigation' could mean many things. While it includes a trigger clause and the Feishu brand name adds some distinctiveness, the lack of concrete actions and limited trigger term coverage weaken its effectiveness for skill selection.

Suggestions

Replace 'navigation' with specific concrete actions, e.g., 'Browses Feishu knowledge base spaces, retrieves wiki page content, resolves wiki node links, and lists child pages.'

Expand trigger terms to include common variations like 'Feishu wiki', 'Feishu docs', 'knowledge space', 'wiki node', 'wiki page', or 'Feishu knowledge base URL'.

Strengthen the 'what' portion by listing 2-4 specific capabilities so Claude can distinguish this skill 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 searching, browsing, linking, creating pages, etc.	1 / 3
Completeness	It has a 'when' clause ('Activate when user mentions knowledge base, wiki, or wiki links') but the 'what' is extremely weak — 'navigation' is too vague to understand what the skill actually does. The 'when' clause exists but the 'what' is insufficient.	2 / 3
Trigger Term Quality	It includes some relevant trigger terms ('knowledge base', 'wiki', 'wiki links') but misses common variations like 'Feishu docs', 'Feishu wiki', 'knowledge space', or specific actions users might mention like 'find a wiki page' or 'link to knowledge base'.	2 / 3
Distinctiveness Conflict Risk	The mention of 'Feishu' provides some distinctiveness, but 'knowledge base' and 'wiki' are generic terms that could overlap with other wiki or documentation skills.	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 dependency on feishu_doc is noted but not linked to any supporting file.

Suggestions

Add verification steps after move/create operations (e.g., 'Verify: get the node again to confirm it moved to the expected location')

Include brief error handling guidance, such as what to do when a token is invalid or permissions are insufficient

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 editing wiki pages, 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 was moved successfully or checking permissions before attempting).	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, the reference to `feishu_doc` as a dependency has no corresponding linked file, and the configuration section could potentially be split out. The skill is moderately sized and handles its scope reasonably inline, but could benefit from linking to a separate reference for obj_type details or error handling.	2 / 3
	Total	10 / 12 Passed

Validation

100%

Warnings & errors only

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: about 2 months ago

Table of Contents

Discovery Implementation Validation

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.