file-sync-management

Use when you need to push files to MinIO for Workers to access, pull Worker output from MinIO, or when a Worker reports they've uploaded files. Also use when notifying Workers to file-sync after writing files they need.

Quality

81%

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

80%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 concise, well-structured skill with excellent progressive disclosure and good actionability; its main gap is the absence of explicit validation checkpoints for the destructive --overwrite sync workflow, capping workflow clarity.

Suggestions

Add an explicit validation step to the body's workflow, e.g. after pulling, verify the expected file exists and is non-empty before reading it.

Include a minimal copy-paste mc command pair (one push, one pull) inline so the body is self-sufficient for the most common case.

Add a brief 'verify' gotcha such as 'After mc mirror, ls the destination to confirm files landed' to close the feedback loop.

Dimension	Reasoning	Score
Conciseness	The body is lean and token-efficient — terse gotcha bullets and a compact routing table with no concept over-explanation — matching anchor 5 ('every token earns its place').	5 / 5
Actionability	Gotchas give concrete directives ('immediately push to MinIO + notify Worker via @mention', 'mc mirror uses --overwrite; single file uses mc cp') but the executable copy-paste commands live in the referenced file rather than the body itself, fitting anchor 4.	4 / 5
Workflow Clarity	A rough push→notify and pull→read sequence is present, but this batch/destructive sync skill (mc mirror --overwrite) lacks explicit validation/verification checkpoints in the body, which the rubric caps at 3 for such operations.	3 / 5
Progressive Disclosure	SKILL.md is a clear, well-organized overview pointing to a single real one-level-deep reference (references/sync-guide.md) via a routing table, matching anchor 5 for a simple, properly split skill.	5 / 5
	Total	17 / 20 Passed

Description

82%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, concrete description with clear trigger guidance and a distinct niche; its only real weakness is second-person voice, which costs it a specificity point under the rubric.

Suggestions

Rewrite in third person to avoid the specificity penalty: e.g. 'Pushes files to MinIO for Workers to access, pulls Worker output, and notifies Workers to file-sync. Use when...'.

Add a couple of natural synonyms (e.g. 'upload', 'download', 'sync') to broaden trigger coverage toward anchor 5.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions (push to MinIO, pull Worker output, notify Workers to file-sync), matching anchor 4, but reduced to 3 because the description uses second-person voice ('you need to push', 'you need'), which the rubric penalizes by lowering specificity by one level.	3 / 5
Completeness	It explicitly answers both 'what' (push/pull files to/from MinIO, notify Workers to file-sync) and 'when' via concrete 'Use when...' / 'Also use when...' trigger clauses, matching the anchor-5 example.	5 / 5
Trigger Term Quality	Natural trigger phrases like 'Worker reports they've uploaded files', 'notifying Workers to file-sync', and 'push files to MinIO' are phrases a user would naturally say; minor synonyms/variants are missing, fitting anchor 4 rather than 5.	4 / 5
Distinctiveness Conflict Risk	The niche is narrow and tool-specific (MinIO file sync between coordinator and Workers), with distinct triggers unlikely to fire for unrelated skills, matching anchor 5.	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/skills/file-sync-management/SKILL.md
Commit: 223ddc2

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