project-management

Use before any projectflow call or Team Leader workflow involving Project state, Project lifecycle, DAG planning, Loop planning, ready node checks, pause/resume/complete, project recovery, heartbeat project checks, or project-level result aggregation. Always use team-coordination first when the question is how to organize the work.

Quality

88%

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

77%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 content is highly actionable with concrete payloads, exact commands, and clear validated workflows, supported by a real one-level reference. Its main weakness is conciseness/structure: the assignedTo rule, lookup steps, and correction table are duplicated between the body and the reference, and a large report template sits inline.

Suggestions

Remove the duplication of the assignedTo localpart rule, the 'agt get workers' lookup steps, and the ❌ correction table: keep one canonical copy (ideally in references/dag-execution.md) and reference it from the body to improve both conciseness and progressive disclosure.

Move the full Project Status Report envelope/emoji tables into references/ (e.g. references/status-report.md), leaving the body with a short 'see reference' pointer plus the essential envelope, to reduce inline bulk.

Consolidate the time-sensitive heartbeat caveats ('for now', 'temporarily disabled', disabled probes) into a single clearly marked 'deprecated/temporary' subsection so they do not read as standing guidance and penalize conciseness.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and free of concept-explanation fluff, but it duplicates the assignedTo localpart rule, lookup steps, and correction table between the main body and references/dag-execution.md, and repeats constraints again in Patch Rules; the heartbeat section also carries time-sensitive caveats ('for now', 'temporarily disabled') outside a deprecation section, so it could be tightened.	2 / 3
Actionability	It provides concrete JSON payloads for every projectflow action, an exact CLI command ('agt get workers --team "$TEAM_CR" -o json'), precise ID formats with a regex, and a copy-paste-ready status report template — fully executable, specific guidance.	3 / 3
Workflow Clarity	Multi-step processes (Create, Pause, Resume, Complete, Result Gate) are clearly numbered with explicit validation checkpoints such as 'If the Project is paused, stop', 'If pulling... fails, stop before any Project state mutation', and 'Only accepted [x] plan nodes satisfy dependencies', providing feedback loops for risky state mutations.	3 / 3
Progressive Disclosure	There is a well-signaled, verified one-level-deep reference (references/dag-execution.md, real and non-nested), but substantial content that could live in the reference — the assignedTo rule and correction table, plus a large inline status-report template — is duplicated inline, leaving the split less clean than the anchor for a score of 3.	2 / 3
	Total	10 / 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 strong across all dimensions: specific actions, broad natural trigger terms, explicit what-and-when guidance, and a conflict-reducing routing note. It is concise and avoids fluff.

Dimension	Reasoning	Score
Specificity	The description enumerates multiple concrete actions — 'projectflow call', 'DAG planning', 'Loop planning', 'ready node checks', 'pause/resume/complete', 'project recovery', 'heartbeat project checks', 'project-level result aggregation' — matching the anchor for listing multiple specific concrete actions.	3 / 3
Completeness	It explicitly answers 'what' (projectflow/lifecycle operations) and 'when' via an explicit 'Use before any projectflow call or Team Leader workflow involving...' trigger clause, satisfying both halves.	3 / 3
Trigger Term Quality	It covers a broad set of natural operational terms an operator would say (DAG planning, Loop planning, pause/resume/complete, project recovery), giving good coverage rather than jargon-only phrasing.	3 / 3
Distinctiveness Conflict Risk	The skill has a clear niche (Project state via projectflow) and actively reduces conflict with the routing directive 'Always use team-coordination first when the question is how to organize the work', making wrong-skill triggering unlikely.	3 / 3
	Total	12 / 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/team-leader-agent/skills/project-management/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.