work-channel-binding

Guide Feishu or WeCom work channel binding for Main Agent managed crews, including dry-run config plans, safe openclaw.json updates, Gateway restart followup, and binding checks.

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

High

Do not use without reviewing

Fix and improve this skill with Tessl

tessl review fix ./crews/it-engineer/skills/work-channel-binding/SKILL.md

Quality

Content

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is highly actionable with a clear, well-gated multi-step workflow. Weaknesses are moderate verbosity in the rationale section and dead doc references that undermine progressive disclosure.

Suggestions

Add the referenced docs/feishu.md and docs/wecom.md files (or update the paths) so the signaled tutorial references resolve.

Tighten the Chinese rationale block to instruction-only guidance and de-duplicate the WeCom install command and Gateway-restart warning.

Dimension	Reasoning	Score
Conciseness	Mostly lean and command-driven, but the Chinese rationale section ("飞书 / 企业微信的交互界面体验与功能丰富度都比微信强太多...") adds persuasion rather than instruction, and the WeCom install command and Gateway-restart warning are each repeated.	2 / 3
Actionability	Provides fully executable, copy-paste-ready commands with concrete argument flags (e.g. the prepare/apply python3 invocations and the WISEFLOW_CONFIRM_* env-var scripts), leaving no ambiguity about what to run.	3 / 3
Workflow Clarity	The 12-step "Required Flow" is clearly sequenced with explicit validation checkpoints (binding check in step 5, redacted-summary confirmation in step 7, apply-only-after-confirmation in step 8, Gateway restart confirmation in steps 9/11) covering a risky config mutation and restart.	3 / 3
Progressive Disclosure	The body is structured as an overview with one-level-deep references to docs and scripts, but the referenced tutorial files (docs/feishu.md, docs/wecom.md) do not exist in the bundle, breaking navigation, while the scripts directory is present.	2 / 3
	Total	10 / 12 Passed

Description

67%

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 specific and distinctive, clearly scoping a narrow niche with concrete sub-tasks. Its main weakness is the absence of an explicit "Use when..." trigger and limited natural-language trigger term coverage.

Suggestions

Add an explicit trigger clause, e.g. ".Use when the user wants to bind or configure a Feishu or WeCom work channel."

Broaden trigger terms to include natural phrasings like "connect", "set up", or "configure a work channel" in addition to "binding".

Dimension	Reasoning	Score
Specificity	Names the domain ("Feishu or WeCom work channel binding") and lists multiple concrete actions: "dry-run config plans", "safe openclaw.json updates", "Gateway restart followup", and "binding checks".	3 / 3
Completeness	Clearly states what the skill does, but there is no "Use when..." clause or equivalent explicit trigger, so per the rubric guideline completeness is capped at 2.	2 / 3
Trigger Term Quality	Includes relevant product terms a user would say ("Feishu", "WeCom", "work channel binding") but omits common natural variations like "connect", "configure", or "set up", and leans on internal jargon ("Main Agent managed crews", "openclaw.json").	2 / 3
Distinctiveness Conflict Risk	The niche is narrow and specific (binding Feishu/WeCom work channels for Main Agent managed crews), making it unlikely to trigger for unrelated skills.	3 / 3
	Total	10 / 12 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning

	Total	14 / 16 Passed

Repository: TeamWiseFlow/xiaobei
Path: crews/it-engineer/skills/work-channel-binding/SKILL.md
Commit: bcef823

Reviewed: 3 days 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.