teamharness-task-execution

Use when a Worker receives TASK_ASSIGNED, acknowledges the task, works inside shared/tasks/{task-id}/, submits with taskflow submit_task, publishes deliverables through submit_task, and reports TASK_COMPLETED or blockers in the Task room.

Quality

96%

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

100%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, executable, well-sequenced instruction skill: concrete templates, explicit error/blocked/boundary handling, and clean section structure with no wasted tokens. Nothing material is missing for its single-purpose scope.

Dimension	Reasoning	Score
Conciseness	The body is lean: short directive sentences and concrete JSON/message templates, with no padding or explanation of concepts Claude already knows; every line carries operational content.	5 / 5
Actionability	It provides copy-paste-ready ack_task and submit_task JSON payloads, exact completion/blocked message templates, an enumerated status list, and explicit owned/do-not-edit path lists covering the common cases.	5 / 5
Workflow Clarity	The lifecycle is clearly sequenced (Acknowledge → Execute → Submit → Completion) with explicit validation checkpoints and feedback loops for failure (ack failure → report blocker), blocked states (BLOCKED result), and boundary conflicts.	5 / 5
Progressive Disclosure	The skill is self-contained with no bundle files and is organized into clearly headed sections (Task Directory, Acknowledge, Execute, Submit, Completion Message) that are easy to navigate; per the simple-skill note this earns a 5.	5 / 5
	Total	20 / 20 Passed

Description

92%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, highly specific description that names the niche, the concrete actions, and the triggering event with minimal overlap risk. The only soft spot is trigger-term breadth — it relies on a small set of system tokens rather than a wider synonym spread.

Dimension	Reasoning	Score
Specificity	The description lists multiple concrete actions across the full task lifecycle (acknowledge, work in shared/tasks/{task-id}/, submit_task, publish deliverables, report TASK_COMPLETED/blockers), tied to specific commands and paths.	5 / 5
Completeness	It explicitly answers both 'what' (the enumerated task-execution actions) and 'when' ('Use when a Worker receives TASK_ASSIGNED...') with a concrete trigger phrase.	5 / 5
Trigger Term Quality	It includes the exact operational trigger tokens a Worker/system would emit (TASK_ASSIGNED, taskflow submit_task, TASK_COMPLETED, blockers, Task room), but offers no broader spread of natural synonyms or file extensions.	4 / 5
Distinctiveness Conflict Risk	The trigger set (TASK_ASSIGNED, shared/tasks/{task-id}/, taskflow, TASK_COMPLETED, Task room) carves out a narrow, unambiguous niche with minimal risk of firing for unrelated skills.	5 / 5
	Total	19 / 20 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: plugins/teamharness/skills/team/task-execution/SKILL.md
Commit: 223ddc2

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