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.

Quality

93%

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

Quality

Content

87%Weight 40%Scale 1-3

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 routing skill: terse gotchas with specific flags and commands, plus a clean operation-reference table linking to two genuine one-level-deep reference files. Its only gap is workflow clarity — guardrails exist as scattered gotchas but no explicit multi-step workflow with validation checkpoints is laid out for the riskier contact/escalation operations.

Suggestions

Add a short sequenced workflow (identify sender -> verify trusted-contact status -> act/escalate) with an explicit validation checkpoint before mutating trusted contacts, so workflow_clarity reaches the top anchor.

Cross-link the manage-primary-channel.sh script from the body (e.g. in the Operation Reference table) so the bundled executable helper is discoverable alongside the reference docs.

Make the first-contact protocol's 'ask in admin's language' rule a concrete step with a verification prompt rather than only a gotcha, to pair the guardrail with an actionable sequence.

Dimension	Reasoning	Score
Conciseness	The body is lean: a one-line overview, terse gotcha bullets, and a routing table — it assumes Claude's competence and explains no background concepts, so every token earns its place. Not 2 because there is no padded explanation to tighten.	3 / 3
Actionability	Concrete, executable specifics throughout — '--action reset', explicit 'channel' and 'target' params, 'to field maps to target', 'agt get managers -o json', 'copaw channels send' — give copy-paste-ready guidance for an instruction-oriented skill. Not 2 because the guidance names exact flags, fields, and commands rather than pseudocode.	3 / 3
Workflow Clarity	The Operation Reference table sequences 'situation -> read this doc' and the gotchas act as guardrails (e.g. 'silently ignored until admin explicitly approves'), but there is no explicit multi-step workflow with validation checkpoints for operations like trusted-contact management. Not 3 because checkpoints are scattered as gotchas rather than an explicit validate/fix/retry sequence; not 1 because a clear routing sequence and guardrails are present.	2 / 3
Progressive Disclosure	A concise overview plus a well-signaled situation->doc table points to two real one-level-deep references (references/identity-and-contacts.md, references/primary-channel.md, both verified present), with detail appropriately split out. Not 2 because references are clearly signaled, single-level, and real rather than nested or inline.	3 / 3
	Total	11 / 12 Passed

Description

100%Weight 40%Scale 1-3

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, specific, and uses an explicit 'Use when' trigger clause that simultaneously conveys capability and trigger conditions. It names five concrete operations with natural trigger language and a clear niche that is unlikely to conflict with other skills.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'determining sender identity', 'managing trusted contacts', 'configuring the admin's primary notification channel', 'handling first-contact', 'escalating to admin across channels' — matching the 'lists multiple specific concrete actions' anchor.	3 / 3
Completeness	An explicit 'Use when...' clause enumerates triggers while the trigger verbs simultaneously state what the skill does, so both 'what' and 'when' are answered explicitly. Not capped at 2 because the 'Use when' trigger guidance is present.	3 / 3
Trigger Term Quality	Natural trigger phrases a manager would voice — 'sender identity', 'trusted contacts', 'primary notification channel', 'first-contact', 'escalating to admin' — give good coverage, not jargon. Not scored 2 because it goes well beyond a single vague keyword.	3 / 3
Distinctiveness Conflict Risk	The niche — admin channel identity, trusted contacts, primary notification channel, cross-channel escalation — is distinct with specific triggers unlikely to fire for unrelated skills. Not 2 because it is far more specific than a generic 'works with document files' example.	3 / 3
	Total	12 / 12 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: agentscope-ai/AgentTeams
Path: manager/agent/skills/channel-management/SKILL.md
Commit: 785c2db

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