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

73%

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

Fix and improve this skill with Tessl

tessl review fix ./manager/agent/skills/file-sync-management/SKILL.md

Quality

Content

72%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 admirably concise and well-structured with a clean single reference, but it leans on the reference for executable commands and presents workflow as rules rather than an explicit validated sequence. Inline a minimal command pair and a numbered pull/push/notify sequence to raise actionability and workflow clarity.

Suggestions

Inline at least one minimal executable command pair (e.g. a 'mc mirror ... --overwrite' pull and a 'mc cp' push) so the body is actionable without opening the reference.

Add a short numbered sequence (write -> push to MinIO -> @mention Worker to file-sync; Worker pushed -> pull before reading) with an explicit verify step to clarify the workflow.

Add a one-line validation cue (e.g. confirm the pulled file exists and is fresh before reading) for the pull-after-Worker-notification step.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence: a few high-value gotchas plus a one-row pointer table, with no padded explanation of concepts Claude already knows.	3 / 3
Actionability	It gives concrete invariants (local fs is not real-time synced, 'mc mirror uses --overwrite; single file uses mc cp') but the actual executable commands are deferred to the reference, so the body itself is not copy-paste ready.	2 / 3
Workflow Clarity	Sequencing is captured as rules ('after writing -> push + notify', 'Worker pushed -> pull before reading') but there is no explicit ordered step sequence or validation checkpoint in the body itself.	2 / 3
Progressive Disclosure	A concise overview with a single, clearly signaled, one-level-deep reference (references/sync-guide.md, which exists) provides easy navigation without nested indirection.	3 / 3
	Total	10 / 12 Passed

Description

75%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 is clear, complete, and well-targeted with explicit triggers, but its second-person voice and reliance on internal jargon limit specificity and trigger-term naturalness. Rewriting in third person and adding user-facing phrasings would lift it further.

Suggestions

Rewrite in third person ('Pushes files to MinIO...' / 'Use when files must be pushed...') to avoid the second-person specificity penalty.

Add natural-language trigger variants a user might say (e.g. 'sync files', 'retrieve Worker output') alongside the MinIO/Worker terminology.

Tighten the second trigger clause ('Also use when notifying Workers to file-sync after writing files they need') which is slightly redundant with the first.

Dimension	Reasoning	Score
Specificity	The description lists several concrete actions ('push files to MinIO', 'pull Worker output from MinIO', 'notifying Workers to file-sync'), which would merit a 3, but it is written in second person ('Use when you need to'), which the rubric penalizes by reducing specificity by one level.	2 / 3
Completeness	It clearly answers both 'what' (push/pull/notify) and 'when' with an explicit 'Use when...' clause covering multiple trigger situations.	3 / 3
Trigger Term Quality	Relevant terms like 'MinIO', 'Worker', and 'file-sync' are present but are system-internal jargon rather than natural variations a user would say, missing common phrasings.	2 / 3
Distinctiveness Conflict Risk	It targets a distinct niche (MinIO file synchronization between an orchestrator and Workers) with specific triggers unlikely to fire for unrelated skills.	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/skills/file-sync-management/SKILL.md
Commit: 785c2db

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