CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

team-management

Use when admin requests creating a team, importing a team, managing team composition, adding/removing workers from a team, or delegating tasks to a Team Leader.

Quality

72%

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

Fix and improve this skill with Tessl

tessl review fix ./manager/agent/skills/team-management/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

76%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 lean, highly actionable overview with excellent one-level-deep reference routing and dense non-obvious domain knowledge. Its weaknesses are a dangling script reference, a read-only command listed for a mutating operation, and missing validation checkpoints around destructive workflows.

Suggestions

Add validation checkpoints to the destructive workflows: verify state via "agt get team <TEAM_NAME>" after create/update/delete and confirm the member Worker's state before @mentioning the Leader, so workflow clarity can rise above the destructive-operations cap.

Fix the dangling "scripts/lifecycle-worker.sh" reference — either add the script to the bundle or point the stop/delete row at the actual commands documented in references/team-lifecycle.md.

Point the "Add/remove worker from team" row at the mutating command ("agt update team", as documented in references/team-lifecycle.md) instead of the read-only "agt get team".

DimensionReasoningScore

Conciseness

Every section carries non-obvious domain knowledge (room compositions, groupAllowFrom policy, the "--admin" vs "--team-admin" flag mismatch, "--delegated-to-team") with zero padding and no explanation of concepts Claude already knows. The one near-duplicate between the intro and a Gotcha bullet reiterates a critical rule rather than padding, so it still meets the "every token earns its place" anchor.

5 / 5

Actionability

The core "agt create team --name ... --leader-name ... --admin ... --workers ..." command is copy-paste ready and field paths like "Worker.spec.resources" are concrete, matching the "mostly executable with minor gaps" anchor. Not 5 because "scripts/lifecycle-worker.sh" in the Operation Reference table does not exist in the bundle, and the add/remove-worker row lists the read-only "agt get team" as its command; not 3 because the primary flow is fully executable with real flags.

4 / 5

Workflow Clarity

Quick Create has a clear sequence with an explicit checkpoint ("Wait for their selection; never silently assign Global Admin") and a safety confirmation for resource changes ("confirm it is not mid-task"), but the destructive workflows — removing workers, deleting a team, stopping member Workers — carry no validation/verification steps in either the body or references/team-lifecycle.md. The rubric's destructive-operations cap therefore holds this at 3 despite the strong create flow.

3 / 5

Progressive Disclosure

Near-model structure: a lean overview plus an Operation Reference table routing each admin intent to one-level-deep reference files that all exist and contain substantive material. Not 5 because "scripts/lifecycle-worker.sh" is a dangling reference — the bundle only ships scripts/create-team.sh — which breaks navigation for the stop/delete operation.

4 / 5

Total

16

/

20

Passed

Description

57%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 well-targeted, trigger-only description with strong natural keywords and a distinct team niche. Its main flaw is that it never states what the skill actually does, leaving the 'what' half of completeness unanswerable without inference.

Suggestions

Lead with an explicit capability statement before the trigger clause, e.g. "Creates and manages agent Teams (1 Team Leader + N Workers) via the agt CLI: creating teams, importing teams, and updating team composition. Use when admin requests...".

Add natural trigger synonyms such as "team members", "team roster", or "assign tasks to a team" to broaden keyword coverage toward the top anchor.

DimensionReasoningScore

Specificity

Lists several concrete operations — "creating a team, importing a team, managing team composition, adding/removing workers from a team, or delegating tasks to a Team Leader" — matching the "several specific actions; minor gaps" anchor. Not 5 because it never states what the skill actually does (no tool, no output, no capability statement), only when to invoke it; not 3 because coverage spans well beyond 1-2 actions across the whole team lifecycle.

4 / 5

Completeness

Only a "when" clause is present ("Use when admin requests...") with no explicit statement of what the skill does — a direct match for the "only 'when' is present without 'what'" anchor. Not 3 because that anchor requires a clear 'what', which is only inferable here, and the guidelines say to score only what is explicitly stated.

2 / 5

Trigger Term Quality

Phrases like "creating a team", "adding/removing workers from a team", and "delegating tasks to a Team Leader" are exactly what a user would naturally say when they need this skill. Not 5 because common variations such as "team members", "team roster", or "assign tasks to a team" are absent; not 3 because keyword coverage is broad and natural rather than partial.

4 / 5

Distinctiveness Conflict Risk

The repeated "team" / "Team Leader" vocabulary carves out a clear niche, with only minor overlap risk with a closely related worker-management skill via "adding/removing workers". Not 5 because "delegating tasks" and worker add/remove could still collide with general delegation or worker-management skills.

4 / 5

Total

14

/

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

15

/

16

Passed

Repository

agentscope-ai/AgentTeams

Path

manager/agent/skills/team-management/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.