CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

communication

Use before sending @mentions, deciding whether to reply, TASK_COMPLETED, BLOCKED, QUESTION, direct answers, loop prevention, or suppressing low-information acknowledgements.

Quality

83%

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

SKILL.md
Quality
Evals
Security

Quality

Content

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

An exemplary instruction-only skill body: concrete templates, explicit do/don't rules, a pre-send validation heuristic, and a loop cutoff, all in a tight 44 lines. The only nit is slight redundancy across the low-information acknowledgment examples.

DimensionReasoningScore

Conciseness

Lean and substantive throughout with no concept over-explanation; minor trimming possible in the acknowledgment examples ("Got it", "Thanks", "ok", "done", "收到", "好的" overlap in intent).

4 / 5

Actionability

Copy-paste-ready message templates ("@coordinator:domain TASK_COMPLETED: <summary>"), concrete do/don't lists, and an executable pre-send filter ("remove all Matrix IDs… send only if the remaining text contains a concrete completion, blocker, question, requested answer, or decision").

5 / 5

Workflow Clarity

The pre-send filter is an explicit validation checkpoint and the two-round loop safeguard bounds the process; as a simple single-purpose skill, the decision flow is unambiguous with no validation gaps.

5 / 5

Progressive Disclosure

Under 50 lines with no need for external references; content is fully inlined with clean, well-organized sections (Routing, Coordinator Identity, @Mention Rules, History Context, Loop Safeguard) that make navigation trivial.

5 / 5

Total

19

/

20

Passed

Description

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

A strong trigger-focused description with specific, distinctive terms, but it is entirely a "when" clause with no "what" — a reader cannot tell the skill contains reply-routing and @mention rules. Adding a brief capability statement would raise completeness and specificity.

Suggestions

Lead with a what-clause, e.g. "Defines @mention and reply rules for worker-to-coordinator communication" before the "Use before…" trigger list.

Add natural synonyms such as "mention the coordinator", "status updates", or "acknowledging tasks" to broaden trigger coverage.

State the outcome the rules produce (noise-free, decision-only messages) so the description answers both what and when explicitly.

DimensionReasoningScore

Specificity

Enumerates several concrete trigger actions — "sending @mentions", "TASK_COMPLETED", "BLOCKED", "QUESTION", "suppressing low-information acknowledgements" — but never states what the skill prescribes, leaving minor gaps in coverage.

4 / 5

Completeness

An explicit "Use before…" trigger clause is present and detailed, but the "what" is only implied — the description never says it defines reply/@mention rules for worker-coordinator communication. Not 2 because the when-clause is concrete, not vague; not 4 because a real what-clause is absent.

3 / 5

Trigger Term Quality

Good natural keywords users would say ("@mentions", "reply", "acknowledgements", "loop prevention") plus distinctive signal tokens; a few natural variations like "mention the coordinator" or "status update" are missing.

4 / 5

Distinctiveness Conflict Risk

Distinctive protocol tokens (TASK_COMPLETED, BLOCKED, QUESTION) carve out a clear niche with minimal conflict risk; minor overlap remains with any generic communication or messaging skill.

4 / 5

Total

15

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

agentscope-ai/AgentTeams

Path

manager/agent/copaw-worker-agent/skills/communication/SKILL.md

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.