file-sharing

Use before filesync calls for project directories, global-shared inputs, non-task shared files, listing shared paths, or troubleshooting missing files. Do not use for task-level sync; taskflow delegate_task and check_task handle task directory sync internally.

Quality

83%

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-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 a well-organized, actionable reference: concrete paths and payloads, clear ownership, and explicit validation checkpoints with feedback loops for failure cases.

Dimension	Reasoning	Score
Conciseness	Lean and efficient — concrete paths, a compact ownership tree, and a JSON payload with no explanation of concepts Claude already knows; every section earns its place.	3 / 3
Actionability	Provides concrete local paths, an exact JSON pull payload, a directory ownership tree, and copy-ready Worker messages — fully actionable instruction guidance.	3 / 3
Workflow Clarity	The "If Worker Cannot Find Files" section is a clear 3-step sequence with an explicit retry-once-then-report feedback loop, and pull failures carry explicit stop-don't-fallback checkpoints for destructive state updates.	3 / 3
Progressive Disclosure	Single-purpose skill with no bundle files and no nested references, organized into clear, well-signaled sections; nothing here needs splitting off.	3 / 3
	Total	12 / 12 Passed

Description

67%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 has excellent trigger guidance and a strong disambiguating anti-trigger, but leans on system jargon for trigger terms and never explicitly states what the skill does.

Suggestions

Add a brief clause stating what the skill does (e.g., 'Provides local shared-path abstractions and sync rules for non-task shared files'), so the 'what' is explicit alongside the 'when'.

Soften jargon-heavy trigger terms by adding more natural phrasings a user might say (e.g., 'shared files', 'project folder', 'file not found') alongside the system terms.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete contexts — "project directories, global-shared inputs, non-task shared files, listing shared paths, or troubleshooting missing files" — rather than vague language.	3 / 3
Completeness	The "when" is explicit and strong ("Use before filesync calls for..." plus an anti-trigger), but the "what" the skill actually does is only implied, not stated as a capability.	2 / 3
Trigger Term Quality	Terms like "filesync calls", "global-shared inputs", "delegate_task", and "check_task" are system-internal jargon rather than natural user phrasing, though "shared files", "missing files", and "project directories" are more natural.	2 / 3
Distinctiveness Conflict Risk	The explicit anti-trigger ("Do not use for task-level sync; taskflow delegate_task and check_task handle task directory sync internally") carves out a clear niche and prevents triggering for the wrong skill.	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/team-leader-agent/skills/file-sharing/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.