sales-cs-enablement

当用户要求启用对外客服（sales-cs）时使用

Quality

57%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./crews/main/skills/sales-cs-enablement/SKILL.md

Quality

Content

75%Weight 40%Scale 1-5

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

The body is a well-structured, actionable orchestration SOP with concrete commands, explicit branching, and gating checkpoints, appropriately splitting mechanical config into bundled scripts and sibling skills. Its main weaknesses are an unresolved placeholder, a missing failure-recovery loop for the final verification, and one slightly ambiguous wrapper invocation.

Suggestions

Resolve the '<...>' placeholder in Step 3 (name the specific openclaw built-in plugin to enable) so the IT-enginever task is fully executable.

Add an explicit failure-recovery branch for Step 3's verification ('验证 channel 状态 + customerDB hook 生效') — what IT engineer should do if the check fails — to lift workflow_clarity to 5.

Clarify the Step 5 invocation: show the actual command (e.g. 'python3 ./skills/sales-cs-enablement/scripts/symlink_business_knowledge.py') or explicitly note 'sales-cs-enablement' is the wrapper command, to remove script-vs-skill ambiguity.

Dimension	Reasoning	Score
Conciseness	The body is a dense, task-focused SOP that assumes Claude's competence — it does not explain what openclaw or a channel is — with only minor trimmable prose (the user-facing channel rationale in Step 2). It is tighter than the anchor-3 example but not perfectly lean.	4 / 5
Actionability	It gives concrete executable commands (check_awada_channel.py with exit-code mapping), exact file paths, and delegated skill names, but has minor gaps: the '<...>' plugin placeholder in Step 3 and the open-ended Step 4 fill-in guidance.	4 / 5
Workflow Clarity	Six steps are clearly sequenced with exit-code branching, a gating checkpoint ('等 IT engineer 报平安后进 Step 4'), consent-before-restart, and a verification step; the gap is no explicit failure-recovery path if the Step 3 channel/hook verification fails.	4 / 5
Progressive Disclosure	SKILL.md is an orchestration overview that delegates mechanical work to two real scripts (referenced by exact path, verified present) and to external skills, one level deep and well-signaled; the minor gap is the bare 'sales-cs-enablement' wrapper shown as a command in Step 5, which blurs script-vs-skill signaling.	4 / 5
	Total	16 / 20 Passed

Description

40%Weight 40%Scale 1-5

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 functions as a trigger clause only — it tells Claude when to invoke the skill but not what the skill actually does. It is distinguishable and uses a natural trigger phrase, but lacks any statement of capability or action.

Suggestions

Add a 'what' clause stating the concrete action, e.g. '启用并配置对外客服 crew sales-cs：检查 channel、派 IT engineer 配置、软链业务知识。当用户要求启用对外客服/sales-cs 时使用。'

Broaden trigger-term coverage with synonyms users might say (销售客服、公开接待客户、客服 agent) so the skill surfaces for more natural phrasings.

Name 1-2 concrete actions (检查 awada channel、配置 channel、软链 business_knowledge) to lift specificity above a pure trigger statement.

Dimension	Reasoning	Score
Specificity	The description names a specific domain ('对外客服（sales-cs）') but states no concrete actions — there is no verb describing what the skill does (e.g. configures, enables, sets up), only a trigger clause.	2 / 5
Completeness	It provides only the 'when' ('当用户要求启用对外客服时使用') with no 'what' — the mirror of anchor 2 ('only when is present without what'); it does not reach 3 because there is no clear statement of what the skill does.	2 / 5
Trigger Term Quality	It includes the natural phrase '当用户要求启用对外客服' plus 'sales-cs', which a user would plausibly say, but misses common synonyms/variations like 销售客服, 公开接待客户, or 客服 agent.	3 / 5
Distinctiveness Conflict Risk	The trigger '启用对外客服' is a clear, distinct niche with minimal conflict risk, but a closely related sibling skill ('sales-cs-review') creates minor overlap risk, fitting anchor 4 rather than a clean 5.	4 / 5
	Total	11 / 20 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/main/skills/sales-cs-enablement/SKILL.md
Commit: fdc03d6

Reviewed: 23 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.