sales-cs-enablement

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

Quality

80%

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

85%

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, concise enablement SOP with strong sequencing and validation checkpoints, undermined only by a couple of non-executable spots — a placeholder plugin name and a bare wrapper invocation in Step 5.

Suggestions

Resolve the literal placeholder in Step 3 ("启用openclaw内置plugin：<...>") with the actual plugin identifier so the IT-engineer subtask is fully copy-paste ready.

Replace the bare ```bash sales-cs-enablement``` block in Step 5 with the actual command the wrapper forwards to (e.g., the explicit python3 symlink_business_knowledge.py invocation), matching Step 1's concrete command style.

Add the expected exit-code/success signal for the Step 5 symlink command so the main agent can confirm the link landed before reporting completion in Step 6.

Dimension	Reasoning	Score
Conciseness	The body is a lean SOP that assumes Claude's competence — concrete commands, exit-code tables, and a numbered delegation block — with no padding explaining concepts Claude already knows, so every section earns its tokens.	3 / 3
Actionability	Most guidance is executable (explicit python3 script paths, exit codes, numbered IT-engineer subtasks), but Step 5's ```bash sales-cs-enablement``` block is a bare wrapper invocation without the real command, and Step 3 contains a literal unfilled placeholder "启用openclaw内置plugin：<...>", leaving key details incomplete.	2 / 3
Workflow Clarity	A clear six-step sequence with explicit checkpoints — exit-code branching in Step 1, a consent checkpoint before the Gateway restart, and a verification step ("验证 channel 状态 + customerDB hook 生效") — provides the feedback loop the destructive config/restart operations require.	3 / 3
Progressive Disclosure	Content is split across well-organized sections with one-level-deep, clearly signaled script references — both scripts/check_awada_channel.py and scripts/symlink_business_knowledge.py are real present bundle files — and there is no deep reference nesting, so navigation is straightforward.	3 / 3
	Total	11 / 12 Passed

Description

75%

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 concise, uses third person, and provides an explicit when-trigger with a distinct niche, but its "what" is a single terse verb and trigger-term coverage is thin relative to the natural phrasings users would actually use.

Suggestions

Expand the "what" beyond a single verb by listing concrete enablement actions (e.g., channel selection, openclaw.json merge, gateway restart, workspace symlink) so specificity reaches the multiple-actions anchor.

Broaden trigger terms to the natural variations already in the body — 销售客服、公开接待客户、对外接待 — so the description matches how users actually phrase the request.

Add a one-line capability summary (e.g., "配置对外 channel 并启用 sales-cs crew") to strengthen the "what does this do" answer without padding.

Dimension	Reasoning	Score
Specificity	Description names the domain and one action — "启用对外客服（sales-cs）" — but lists only the single verb "启用" rather than multiple concrete enablement actions, matching the 'names domain and some actions, but not comprehensive' anchor.	2 / 3
Completeness	It explicitly answers both "what" (启用/enable the sales-cs crew) and "when" ("当用户要求…时使用" is an explicit trigger clause), so it is not subject to the missing-trigger cap; the explicit 'Use when…' equivalent lifts it above the anchor-2 case where 'when' is only implied.	3 / 3
Trigger Term Quality	It surfaces "对外客服" and "sales-cs" as natural terms, but common variations that users would actually say (销售客服、公开接待、客户接待) appear only in the body and are absent from the description, leaving relevant keyword coverage incomplete.	2 / 3
Distinctiveness Conflict Risk	The trigger is a clear niche — enabling a specific external customer-service crew — and its "启用/enable" trigger is distinct from the sibling skill sales-cs-review, making false-triggering unlikely.	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/main/skills/sales-cs-enablement/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.