task-coordination

Coordinate access to shared task directories using .processing marker files. Use before accessing a Worker's workspace to prevent conflicts when both Manager and Worker might modify files simultaneously.

Quality

73%

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

Fix and improve this skill with Tessl

tessl review fix ./manager/agent/skills/task-coordination/SKILL.md

Quality

Content

72%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 verified, copy-paste-ready commands and good progressive disclosure to real bundle scripts. It is mildly weakened by redundancy between the protocol and the Scripts section and the absence of an explicit error-recovery feedback loop for the marker check.

Suggestions

Add a short feedback loop for the check step, e.g. 'If exit code 1 (in progress): wait for expiration (15 min default) or coordinate with the holder before retrying'.

Reduce redundancy by either removing the separate 'Scripts' section or trimming the full command lines from the protocol so each appears in only one place.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with executable commands, but repeats script invocations both in the 6-step protocol and again in the 'Scripts' section, and the marker format is shown as both a JSON example and a field table, which could be tightened.	2 / 3
Actionability	It provides fully executable bash commands with concrete script paths (verified to exist in ./scripts/), explicit exit codes, and clear parameters, making the guidance copy-paste ready.	3 / 3
Workflow Clarity	The 6-step sequence (sync, check, create, modify, remove, sync) is clearly ordered with a marker-check checkpoint, but there is no error-recovery feedback loop (e.g. what to do if the check returns 'in progress') for shared-state modifications, capping it below 3.	2 / 3
Progressive Disclosure	Content is well-organized into clear sections with one-level-deep references to real bundle scripts (check/create/remove-processing-marker.sh, all present in ./scripts/), each documented with usage and exit codes.	3 / 3
	Total	10 / 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 cleanly answers both what and when with an explicit 'Use before...' trigger and a distinct niche, written in correct third-person voice. It is slightly held back by jargon-heavy trigger terms and a single-action rather than multi-action specificity.

Suggestions

Add more concrete actions to specificity, e.g. '...create, check, and remove .processing marker files' to hit the multi-action anchor.

Soften jargon in trigger terms by adding natural phrasings like 'shared workspace', 'file lock', or 'avoid editing conflicts' alongside Manager/Worker terminology.

Dimension	Reasoning	Score
Specificity	Names the domain ('shared task directories') and a concrete mechanism ('.processing marker files'), but describes a single coordinating action rather than listing multiple distinct concrete actions, so it does not reach the 'multiple specific actions' anchor.	2 / 3
Completeness	It states both what ('Coordinate access to shared task directories using .processing marker files') and when ('Use before accessing a Worker's workspace to prevent conflicts when both Manager and Worker might modify files simultaneously') with an explicit trigger clause.	3 / 3
Trigger Term Quality	Relevant terms like 'shared task directories', '.processing marker files', and 'prevent conflicts' appear, but the language leans on internal jargon (Manager/Worker, .processing) rather than natural variations a user would commonly say, missing common phrasings.	2 / 3
Distinctiveness Conflict Risk	The Manager/Worker task-directory coordination niche with .processing markers is distinct and unlikely to trigger for unrelated skills; the triggers are specific to this scenario.	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/skills/task-coordination/SKILL.md
Commit: 785c2db

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