CtrlK
BlogDocsLog inGet started
Tessl Logo

channel-management

Use when determining sender identity in any room, managing trusted contacts, configuring the admin's primary notification channel, handling first-contact from a new channel, or escalating to admin across channels.

68

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

86%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 efficiently structured skill body: terse operational gotchas plus a clear routing table to two well-organized reference files. The only gap is that in-page validation checkpoints are deferred to the references rather than surfaced in the body.

DimensionReasoningScore

Conciseness

The body is lean — terse gotcha bullets and a compact dispatch table — with no padding and no explanation of concepts Claude already knows; every line is operational and earns its place.

5 / 5

Actionability

Concrete, executable specifics appear inline ('--action reset', 'to field maps to target parameter', 'agt get managers -o json', 'copaw channels send'), while the full executable procedures are correctly deferred to the reference docs, leaving only minor gaps in the body itself.

4 / 5

Workflow Clarity

The dispatch table gives a clear situation→doc routing sequence and the gotchas act as guardrails, with the numbered, validated workflows living in the referenced docs; the body lacks an explicit in-page validation checkpoint, keeping it just below the top anchor.

4 / 5

Progressive Disclosure

A clean overview with a well-signaled one-level-deep dispatch table pointing to two real reference files, with the supporting script referenced from within a reference doc — content is appropriately split and easy to navigate.

5 / 5

Total

18

/

20

Passed

Description

80%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-rich description that names five concrete capabilities and opens with an explicit 'Use when' clause. It could be nudged to the top level by separating a standalone 'what' statement and adding a few synonym triggers.

Suggestions

Lead with a short standalone capability sentence (e.g. 'Manages admin communication channels, sender identity, and trusted contacts.') before the 'Use when' clause to make the 'what' fully explicit.

Add a couple of natural synonym triggers (e.g. 'contacts', 'notification channel', 'switching primary channel') to broaden keyword coverage.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'determining sender identity', 'managing trusted contacts', 'configuring the admin's primary notification channel', 'handling first-contact', 'escalating to admin' — giving comprehensive coverage of the skill's capabilities.

5 / 5

Completeness

The 'Use when...' clause gives an explicit, concrete 'when', and the enumerated actions convey the 'what', but the 'what' is folded into the trigger list rather than stated as a standalone capability sentence, leaving it slightly less explicit than the top anchor.

4 / 5

Trigger Term Quality

Good coverage of natural trigger phrases ('sender identity', 'trusted contacts', 'first-contact', 'escalating to admin'), but a few common variations/synonyms are missing and there are no file-extension-style triggers, so it stops short of comprehensive.

4 / 5

Distinctiveness Conflict Risk

The niche (admin identity, trusted contacts, primary notification channel, first-contact) is mostly distinct with clear triggers, though escalation overlaps slightly with the related task-management skill referenced in the body.

4 / 5

Total

17

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
agentscope-ai/AgentTeams
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.