task-progress

Use when executing a task (progress logging, plan updates), when resuming a task after session reset, or when managing task history. Covers progress log format, task-history.json, and resume flow.

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Medium

Suggest reviewing before use

Quality

Content

100%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 body is lean, concrete, and well-structured, giving copy-paste-ready paths and commands plus a clear resume workflow. It assumes Claude's competence and avoids unnecessary explanation.

Dimension	Reasoning	Score
Conciseness	Lean and efficient throughout: terse gotchas, concrete paths, and code/JSON blocks with no padding or explanation of concepts Claude already knows.	3 / 3
Actionability	Provides fully concrete, copy-paste-ready guidance: exact file paths, the `mc cp` push command, a full task-history.json schema, and a numbered resume flow.	3 / 3
Workflow Clarity	The resume flow is a clear 4-step numbered sequence and the progress-log loop (append then push) is unambiguous, with gotchas acting as guardrails; no destructive/batch operation needs an explicit validate-retry checkpoint.	3 / 3
Progressive Disclosure	A single self-contained file (~70 lines) with well-organized sections (Gotchas, Progress Log, Task History, Resume Flow); no nested or external references needed, and none are referenced.	3 / 3
	Total	12 / 12 Passed

Description

77%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 clearly states both capabilities and trigger conditions with concrete named artifacts, but leans on broad "executing a task" phrasing and some technical jargon that weakens trigger-term naturalness and distinctiveness.

Suggestions

Lead with the most distinctive trigger (e.g., "Use when resuming a task after a session reset or managing task history") rather than the broad "executing a task".

Add common natural phrasings users might say (e.g., "pick up where I left off", "task log") alongside the technical artifact names.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ("progress logging, plan updates", "resuming a task after session reset", "managing task history") and names specific artifacts (progress log format, task-history.json, resume flow).	3 / 3
Completeness	Explicitly answers both what ("Covers progress log format, task-history.json, and resume flow") and when ("Use when executing a task... when resuming... or when managing task history").	3 / 3
Trigger Term Quality	Has natural trigger phrases ("resuming a task", "managing task history") but mixes in technical jargon like "task-history.json" and "progress logging"; missing some common user phrasings.	2 / 3
Distinctiveness Conflict Risk	The resume/history niche is fairly distinct, but the leading trigger "executing a task" is broad and could overlap with general task-execution skills.	2 / 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/worker-agent/skills/task-progress/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.