CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

teamharness-task-execution

Use when you act as Worker: receive TASK_ASSIGNED, acknowledge the task, work inside shared/tasks/{task-id}/, submit with taskflow submit_task, publish deliverables through submit_task, and report TASK_COMPLETED or blockers in the Task room.

Quality

86%

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

The canonical home for this skill is teamharness-task-execution in agentscope-ai/AgentTeams

SKILL.md
Quality
Evals
Security

Quality

Content

77%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 highly actionable and the workflow is sequenced with explicit validation and recovery loops, but token efficiency and file organization lag: a quarter of the content is edge-case protocol detail (conclusions warnings, digest internals, legacy submissions) inlined into an already long single file. Splitting that detail into a reference file and trimming the semantics explanations would lift both weaker dimensions.

Suggestions

Move the edge-case submission semantics (conclusions warning/strict-mode behavior, submission_id/digest fencing, legacy-task retry rules) into a one-level-deep reference file such as references/submission-protocol.md, keeping SKILL.md to the common acknowledge-execute-submit path.

Trim the conclusions paragraph to the essential rule (3-5 one-line entries) and cut the digest-coverage and CoPaw legacy-adoption details unless the worker genuinely must act on them.

Add a short numbered overview (acknowledge → read spec → execute → report progress → submit) near the top so the full sequence is visible before the per-section detail.

DimensionReasoningScore

Conciseness

Mostly efficient — the guidance is novel protocol detail Claude cannot know, with no generic-concept padding — but roughly 60-80 of the ~260 lines are rare edge-case minutiae that could be tightened or offloaded: the 9-line conclusions-semantics paragraph ("Fewer than 3 comes back as a warning... more than 5 are all recorded in the task meta"), the submission digest internals ("The digest covers your trimmed status, whitespace-collapsed summary..."), and legacy-task handling naming "CoPaw". Not a 4: the over-explanation is more than minor instances; not a 2: the bulk is necessary, non-redundant operational rule.

3 / 5

Actionability

Fully executable: copy-paste-ready JSON payloads for ack_task and submit_task (with status, summary, conclusions, deliverables), the exact status enum (SUCCESS through INTERRUPTED), a concrete progress-note format ("coding-cli:<cli> run=<run_id> dispatched"), and a field-by-field spec for request_attention (kind, question, options, suggested, expiresAt). Not a 4: the common cases are covered by complete, copy-paste examples.

5 / 5

Workflow Clarity

The Acknowledge → Read spec → Execute → Submit → Completion sequence is clearly sectioned, with explicit validation checkpoints ("confirm the acknowledgment reached shared storage (`synced: true`)") and error-recovery feedback loops throughout: ack failure → "stop and report the blocker", sync failure → inspect authoritative state and "retry with exactly the same status, summary, and ordered deliverables", and the CLI-run outcome mapping to SUCCESS/PARTIAL/BLOCKED. Not a 4: validation steps and recovery loops are explicit, not implicit.

5 / 5

Progressive Disclosure

The body is well-sectioned with clear headers (Task Directory, Acknowledge, Execute, Submit, Completion Message) but is a single ~260-line monolith with no bundle files or references; the edge-case material (digest semantics, submission identity fencing, legacy-task adoption) is inline content that plausibly belongs in a one-level-deep reference file. Not a 4: content that should be separate is inline and the file exceeds the under-50-lines simple-skill exception; not a 2: structure is clear and navigable, with no buried references.

3 / 5

Total

16

/

20

Passed

Description

87%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 description: it explicitly covers both what the skill does and when to use it, with concrete protocol-specific trigger terms and minimal conflict risk. The only deductions are the second-person phrasing (specificity) and a few missing natural variations like "task execution" or "assigned work" (trigger terms).

DimensionReasoningScore

Specificity

The description lists multiple concrete actions covering the full worker lifecycle — "receive TASK_ASSIGNED, acknowledge the task, work inside shared/tasks/{task-id}/, submit with taskflow submit_task, publish deliverables through submit_task, and report TASK_COMPLETED or blockers" — which is comprehensive (base 5). However, it opens with second-person voice ("Use when you act as Worker"), which the rubric penalizes by reducing specificity by 1. Not a 3: far more than 1-2 concrete actions; not a 5: the second-person penalty applies.

4 / 5

Completeness

Both questions are answered explicitly: 'when' via the leading "Use when you act as Worker" with the concrete TASK_ASSIGNED trigger, and 'what' via the enumerated action chain from acknowledgment through submission to completion reporting. Not a 4: the 'when' is not merely present but concrete and specific.

5 / 5

Trigger Term Quality

Natural in-domain terms are present: "TASK_ASSIGNED", "acknowledge the task", "submit_task", "TASK_COMPLETED", "blockers", "Task room" — phrases a user in this harness would actually say. Not a 5: common variations like "task execution", "assigned work", "pick up a task", or "progress report" are missing; not a 3: coverage goes well beyond a couple of generic keywords.

4 / 5

Distinctiveness Conflict Risk

Clear niche (TeamHarness Worker role) with distinctive tokens — "TASK_ASSIGNED", "taskflow submit_task", "Task room", "shared/tasks/{task-id}/" — that are unlikely to appear in other skills' triggers. Not a 4: overlap risk is essentially nil given the protocol-specific vocabulary.

5 / 5

Total

18

/

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

plugins/agentteams-teamharness/skills/team/task-execution/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.