CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

project-management

Use when admin asks to start a multi-worker project, when a Worker @mentions you with task completion in a project room, when project plan changes are needed, or when a blocked task needs resolution.

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./manager/agent/skills/project-management/SKILL.md
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.

The body is an exemplary dispatcher: lean, dense with non-obvious operational rules, and routing every situation to a real, one-level-deep reference file. Its only ceiling is that executable detail mostly lives in the bundle files rather than the body itself, which is the appropriate design for this skill.

DimensionReasoningScore

Conciseness

Every one of the ~30 lines is an operational fact Claude cannot infer — the YOLO-mode check, the file layout tree, and eight terse gotchas — with nothing explaining known concepts; matches 'lean and efficient; every token earns its place'.

5 / 5

Actionability

Includes a copy-paste command ('[ "${AGENTTEAMS_YOLO:-}" = "1" ] || [ -f ~/yolo-mode ]'), exact paths ('shared/tasks/{task-id}/', 'meta.json'), and unambiguous rules ('Do NOT proceed to next phase while REVISION_NEEDED is pending'), but most executable procedures are delegated to the reference docs rather than shown in the body — anchor 4, not 5's fully self-contained coverage.

4 / 5

Workflow Clarity

Routing is unambiguous via the situation-to-doc table and includes explicit checkpoints ('Check YOLO mode BEFORE drafting the plan', the REVISION_NEEDED gate, the mandatory 'All tasks complete' step), but the end-to-end sequences themselves live one level deep in the references, leaving minor in-body sequence gaps — anchor 4 rather than 5.

4 / 5

Progressive Disclosure

A clear overview with well-signaled, verified one-level-deep references: the table maps every situation to one of four existing reference files, explicitly instructs 'Read the relevant doc before executing. Do not load all of them', and the scripts are invoked with full paths from within the references — matches the anchor-5 example pattern.

5 / 5

Total

18

/

20

Passed

Description

52%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.

The description is strong on trigger coverage and distinctiveness but fundamentally incomplete: it tells Claude when to activate without ever saying what the skill does. Adding a one-clause capability statement before the 'Use when' triggers would move it from adequate to strong.

Suggestions

Lead with a 'what' clause before the triggers, e.g., 'Orchestrates multi-worker projects: creates project rooms, assigns and tracks tasks in plan.md, resolves blockers, and keeps the admin in sync. Use when...'

Add natural trigger synonyms such as 'new project', 'task finished/done', or 'unblock a stuck task' so phrasing variations still match.

State 1-2 concrete capabilities (e.g., 'maintains plan.md as the single source of truth', 'notifies the admin on task completion') to raise specificity alongside completeness.

DimensionReasoningScore

Specificity

Names the domain ('multi-worker project') and concrete trigger scenarios ('Worker @mentions you with task completion in a project room', 'blocked task needs resolution'), but states no actions the skill itself performs — between anchor 2 (actions minimal/generic) and anchor 3 (1-2 concrete actions); the concrete scenario language lifts it to 3, and the absence of any stated capability rules out 4.

3 / 5

Completeness

Four explicit 'Use when...' triggers are present ('when admin asks to start a multi-worker project', 'when a Worker @mentions you with task completion'), but no statement of what the skill does — this matches anchor 2 ('only when is present without what') and rules out 3, which requires a clear 'what'.

2 / 5

Trigger Term Quality

Natural trigger phrases like 'start a multi-worker project', 'task completion', 'plan changes', and 'blocked task' give good coverage, but common variations users might say (e.g., 'new project', 'unblock', 'stuck task') are missing — matches anchor 4, not 5's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

Triggers are tied to a specific environment ('project room', 'Worker @mentions you', admin), giving a mostly distinct niche with minor overlap risk; 'plan changes are needed' and 'blocked task' are broader and could overlap with general task-management skills, keeping it at anchor 4 rather than 5.

4 / 5

Total

13

/

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/skills/project-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.