organization

Use only when you need to look up team topology, worker phase, runtime state, or identity that is NOT available from the current message context. Do not use for standard task flows — the coordinator is the message sender, and the task room is in meta.json.room_id.

Quality

87%

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

100%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 tight, actionable, and well-structured: executable CLI commands, a clear lookup sequence with explicit fallbacks, and clean section organization appropriate for a short single-purpose skill.

Dimension	Reasoning	Score
Conciseness	Lean and operational with no padding or explanation of concepts Claude already knows; every line earns its place.	3 / 3
Actionability	Provides concrete, copy-paste-ready commands ('agt get workers ... -o json', the jq TEAM_CR extraction) with an env-var fallback pattern.	3 / 3
Workflow Clarity	A simple lookup skill with a clear sequence (get workers -> extract team CR -> team query) and explicit error-recovery checkpoints ('If team-scoped queries are denied, ask your coordinator'; 'Do not guess').	3 / 3
Progressive Disclosure	Under 50 lines with no need for external references and well-organized sections (Source Of Truth, What To Use It For), meeting the simple-skill allowance for a top score.	3 / 3
	Total	12 / 12 Passed

Description

75%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 specific, complete, and well-differentiated with explicit use/anti-use triggers, but its trigger terms lean on internal jargon rather than natural user phrasing, and the second-person voice costs it a specificity point.

Suggestions

Rewrite in third person to avoid the second-person specificity penalty (e.g., 'Looks up team topology...' instead of 'Use only when you need to look up...').

Soften jargon with more natural trigger phrasing or common variations so the skill is easier to match against ordinary user requests.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete lookup targets ('team topology, worker phase, runtime state, or identity'), which is normally a 3, but the second-person voice ('Use only when you need') triggers the rubric's -1 specificity penalty.	2 / 3
Completeness	Explicitly answers both 'what' (look up topology/phase/state/identity) and 'when' via an explicit 'Use only when...' trigger plus an anti-trigger ('Do not use for standard task flows').	3 / 3
Trigger Term Quality	Relevant domain terms are present (team topology, worker phase, runtime state, identity) but they are jargon-heavy and lack common natural variations a user would naturally phrase.	2 / 3
Distinctiveness Conflict Risk	A clear narrow niche (AgentTeams runtime state lookup) with an explicit anti-trigger ('Do not use for standard task flows') makes it unlikely to fire for the wrong skill.	3 / 3
	Total	10 / 12 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: agentscope-ai/AgentTeams
Path: manager/agent/copaw-worker-agent/skills/organization/SKILL.md
Commit: 785c2db

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