file-sharing

Use before direct filesync calls, reading non-task shared files, pushing mid-task progress, or troubleshooting missing shared files. Do not use for normal task acceptance or submission; taskflow ack_task and submit_task handle lifecycle sync internally.

Quality

86%

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

93%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 exceptionally lean and actionable with copy-paste examples and a well-sequenced troubleshooting flow. The only minor gap is the absence of explicit success-verification steps for the filesync pull/push operations.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence: no concept explanations, just actionable path lists, copy-paste JSON, and concrete commands, with every token earning its place.	5 / 5
Actionability	Provides fully executable, copy-paste-ready guidance including JSON pull/push payloads, specific bash commands (pwd, ls -la), and a concrete coordinator escalation template covering the common cases.	5 / 5
Workflow Clarity	The 'If You Cannot Find Files' section is a clearly numbered sequence with an escalation checkpoint, but the pull/push operations lack explicit success-verification steps, leaving minor validation gaps versus the 5 anchor.	4 / 5
Progressive Disclosure	A self-contained single-purpose skill with clean section headers (Local Paths, Task Lifecycle Sync, Non-Task Shared Files, troubleshooting) and easy navigation; no external references are needed, so well-organized sections suffice for the top score.	5 / 5
	Total	19 / 20 Passed

Description

78%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.

The description is trigger-rich with strong negative boundary guidance that makes it highly distinctive. Its main weakness is that the capability ('what') is implied through triggers rather than stated directly.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ('direct filesync calls, reading non-task shared files, pushing mid-task progress, troubleshooting missing shared files') but frames them as triggers rather than a pure capability list, leaving minor gaps versus the comprehensive 5 anchor.	4 / 5
Completeness	The 'when' is explicit and strong with both positive and negative trigger guidance, but the 'what' is only implied from the listed trigger actions rather than stated as a capability, so it is not quite the fully explicit 5.	4 / 5
Trigger Term Quality	Includes natural terms a user would say ('filesync', 'shared files', 'mid-task progress', 'missing shared files') with good coverage, though a few synonyms or variations are absent.	4 / 5
Distinctiveness Conflict Risk	The explicit negative boundary ('Do not use for normal task acceptance or submission; taskflow ack_task and submit_task handle lifecycle sync internally') carves out a clear niche with minimal conflict risk against the related taskflow skill.	5 / 5
	Total	17 / 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: manager/agent/copaw-worker-agent/skills/file-sharing/SKILL.md
Commit: 69c5849

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