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

91%

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

96%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, well-structured instruction skill with concrete paths, copy-paste templates, and explicit stop-on-failure validation checkpoints. The only minor gap is the lack of any progressive-disclosure structure, which is acceptable for a self-contained skill but keeps it off the top anchor.

Dimension	Reasoning	Score
Conciseness	Lean and efficient: short directive sections, a compact directory tree, and copy-paste path/JSON snippets with no padding or explanation of concepts Claude already knows; every token earns its place.	5 / 5
Actionability	Fully actionable instruction-only guidance: exact local paths to use, a copy-paste JSON pull action, a ready-to-send Worker message template, and a concrete forbidden-path list, covering the common cases.	5 / 5
Workflow Clarity	Explicit validation/stop checkpoints ('If a directory pull fails, stop and report', 'If this project directory pull fails, stop. Do not pull only meta.json...') and a numbered troubleshooting procedure with a one-retry feedback loop, matching the explicit-validation anchor.	5 / 5
Progressive Disclosure	Well-organized into clearly labeled sections with no nested references and no bundle files; slightly above the simple-skill threshold in length and entirely self-contained, so it sits just below the clear-overview-with-one-level-references anchor.	4 / 5
	Total	19 / 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, well-scoped description that clearly states what it is for, when to use it, and when not to, with good distinctiveness from the related taskflow skill. Main weakness is that it lists trigger scenarios rather than concrete actions and leans on internal jargon for some trigger terms.

Suggestions

Lead with the concrete actions the skill performs (e.g., 'Resolves shared-path lookups and refreshes project/task directories before filesync') rather than only the scenarios that trigger it, to lift specificity.

Pair internal tool names with plain-language phrases (e.g., 'taskflow delegate_task / delegating tasks') so users naturally matching the description aren't gated behind jargon.

Dimension	Reasoning	Score
Specificity	Lists several concrete scenarios ('project directories, global-shared inputs, non-task shared files, listing shared paths, or troubleshooting missing files') plus an explicit exclusion; scored 4 rather than 5 because it frames trigger scenarios rather than the concrete actions the skill performs, and several terms lean on internal jargon ('global-shared inputs', 'non-task shared files').	4 / 5
Completeness	Explicitly answers both what (use before filesync calls for shared/non-task files) and when (concrete trigger scenarios), and adds a clear 'do not use' boundary with concrete trigger phrases.	5 / 5
Trigger Term Quality	Good natural-term coverage ('filesync calls', 'shared files', 'shared paths', 'missing files', 'troubleshooting') but leans on internal jargon ('taskflow delegate_task', 'check_task', 'global-shared') that a user would not naturally say, leaving a few common synonyms missing.	4 / 5
Distinctiveness Conflict Risk	Clear niche (shared/project-level file sync) explicitly disambiguated from task-level sync handled by taskflow, giving distinct triggers and minimal conflict risk.	5 / 5
	Total	18 / 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/team-leader-agent/skills/file-sharing/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.