CtrlK
BlogDocsLog inGet started
Tessl Logo

proactive-send

向 awada 客户主动发送消息。在 openclaw 消息处理循环之外直接 POST 到 relay 网关 outbound 端点,无需等待客户发起对话。

56

Quality

64%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./crews/sales-cs/skills/proactive-send/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

82%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 tight, actionable single-purpose skill with excellent executable guidance and clean sectioning; its only real gap is the lack of an explicit pre-send validation step for an outward-facing action.

DimensionReasoningScore

Conciseness

The body is lean and assumes competence — a copy-paste command, a tight parameter table, a return-value list, and focused notes — with only minor density in the config-defaults sentence that could be split for readability, so it sits just below the fully lean 5 anchor.

4 / 5

Actionability

Provides a fully executable, copy-paste-ready command with both required arguments populated, a precise parameter table, and concrete success/failure exit behavior, matching the 'specific examples cover the common cases' anchor.

5 / 5

Workflow Clarity

The single action is unambiguous and well-scoped (good for a simple skill), but an outward-facing proactive send has no pre-send validation/confirmation checkpoint despite the cautionary notes, leaving a minor validation gap that holds it below 5.

4 / 5

Progressive Disclosure

Well-organized into clear sections (使用方法, 参数说明, 返回值, 注意事项) with a clearly signaled one-level reference ('契约见 docs/AWADA-CLIENT-TRANSPORT.md §3'); not a 5 because that referenced doc is not present in the bundle, so navigation cannot be fully verified.

4 / 5

Total

17

/

20

Passed

Description

46%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 is technically precise and clearly scoped to a narrow niche, but it is written in implementation jargon rather than natural trigger language and omits any explicit 'when to use' guidance.

Suggestions

Add an explicit 'Use when...' clause naming the business scenarios that call for proactive sending (e.g. 'Use when a sales-cs follow-up is needed outside the active conversation flow').

Replace implementation terms ('relay 网关 outbound 端点', 'POST') with user-facing trigger phrases ('主动给客户发消息', '跟进消息') so the description fires on natural requests.

Trim the transport mechanism detail from the description and keep it in the body, since the frontmatter should describe the capability, not the HTTP contract.

DimensionReasoningScore

Specificity

Names the domain (awada customer messaging) and 1-2 concrete actions ('主动发送消息', '直接 POST 到 relay 网关 outbound 端点'), but coverage is limited to essentially one operation, so it is not comprehensive enough for a 4.

3 / 5

Completeness

There is a clear 'what' (proactively POST messages to awada customers) but no 'Use when...' clause; 'when' is only weakly implied by '无需等待客户发起对话', which per the guidelines caps completeness at 3.

3 / 5

Trigger Term Quality

Only one or two generic keywords ('主动发送消息') are present; the rest is technical jargon ('openclaw 消息处理循环', 'relay 网关 outbound 端点', 'POST') with no natural trigger phrases a user would actually say.

2 / 5

Distinctiveness Conflict Risk

The niche is narrow and specific (proactive awada outbound POST via relay), making it mostly distinct with only minor overlap risk against a generic send-message skill; not a 5 because it lacks distinct trigger phrases that would prevent misfiring.

4 / 5

Total

12

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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
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.