CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

organization

Use before any Leader action that depends on current team topology, worker list, worker phase, runtime, room ID, Matrix ID, Team Admin, human identity, or lifecycle state. Always use this skill when assigning tasks, sending cross-room messages, recovering projects, handling heartbeat, waking/sleeping workers, or when any worker/room/identity value might be stale.

Quality

85%

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.

A tight, highly actionable skill body: executable commands, a critical name-resolution gotcha, and explicit failure handling with no wasted tokens. Only minor gaps — an example value extraction and a concrete way to perform the pre-lifecycle check — keep actionability and workflow clarity at 4.

DimensionReasoningScore

Conciseness

Lean and efficient with zero padding: every sentence is an instruction, constraint, or executable command, and no space is spent explaining concepts Claude already knows.

5 / 5

Actionability

The Team CR resolution block is copy-paste executable with jq extraction, and lifecycle commands are concrete agt invocations; a minor gap is that the 'What To Read' list gives no example of extracting a specific value (e.g., a Matrix ID) from the JSON output.

4 / 5

Workflow Clarity

Clear sequence (resolve Team CR before any team-scoped query, then lifecycle gated on prior checks) with error-recovery guidance and a stop-and-report rule; the 'checking active project and task files' checkpoint is asserted but not shown how to perform, keeping it below anchor 5.

4 / 5

Progressive Disclosure

Under 50 lines, no external references needed, and cleanly organized into well-labeled sections (Source Of Truth, What To Read, Lifecycle) — per the simple-skill guideline, well-organized sections alone warrant top marks.

5 / 5

Total

18

/

20

Passed

Description

78%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 explicit, natural 'when' guidance and a distinct niche vocabulary. Its main weakness is that the 'what' — the skill resolves current AgentTeams topology/runtime state — is implied rather than stated.

Suggestions

Add one explicit 'what' clause, e.g. 'Resolves current AgentTeams topology and runtime state (room IDs, Matrix IDs, worker phases) via the agt CLI' before the 'Use before...' sentence.

Include a synonym or two for common phrasings (e.g. 'team structure', 'check team state') to broaden natural trigger coverage toward anchor 5.

DimensionReasoningScore

Specificity

Names the domain and several concrete operations ("assigning tasks, sending cross-room messages, recovering projects, handling heartbeat, waking/sleeping workers") with minor gaps — it never explicitly states what the skill does (resolve current state via the agt CLI), only when to invoke it.

4 / 5

Completeness

The 'when' is exceptionally explicit and stated twice ("Use before any Leader action that depends on...", "Always use this skill when..."), while the 'what' is only implied by the dependency clause rather than explicitly named, falling between anchors 3 and 4.

4 / 5

Trigger Term Quality

Rich natural trigger phrases a Leader would actually say ("assigning tasks", "cross-room messages", "heartbeat", "waking/sleeping workers", "stale") plus a catch-all condition, but coverage stops short of anchor 5's comprehensive synonym/extension-level variety.

4 / 5

Distinctiveness Conflict Risk

"Matrix ID", "Team Admin", "worker phase", "heartbeat" carve a clear niche with distinct triggers and minimal conflict risk with other skills.

5 / 5

Total

17

/

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/team-leader-agent/skills/organization/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.