CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

file-sync

Sync files with centralized storage. Use when your coordinator or another Worker notifies you of file updates (config changes, task files, shared data, collaboration artifacts).

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

76%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, actionable single-purpose skill: it tells the agent exactly what to run and when, with no padding. Its main gap is the absence of any verification step for what is actually a destructive batch mirror operation, and the bundle script is never referenced.

Suggestions

Add a verification checkpoint before confirming to the sender, e.g. check that agentteams-sync exits 0 / prints its completion line, and what to do on failure (re-run or report the error).

Remove one of the duplicated trigger statements — the 'When to use' section repeats the opening paragraph and the frontmatter description nearly verbatim.

Reference the bundle script explicitly (e.g. note that 'agentteams-sync' maps to scripts/agentteams-sync.sh) so the implementation is discoverable from the body.

DimensionReasoningScore

Conciseness

The body is lean (13 lines) and assumes competence, but the trigger is stated three times (opening paragraph, 'When to use' section, echoing the frontmatter description), which is a minor redundancy that could be trimmed.

4 / 5

Actionability

The skill gives a copy-paste-ready command ('agentteams-sync' in a bash block) plus a concrete post-action instruction ('Always confirm to the sender after sync completes'), fully covering the single common case.

5 / 5

Workflow Clarity

The single action is unambiguous, but the underlying sync is a batch/overwrite operation (mc mirror --overwrite in scripts/agentteams-sync.sh) with no validation or verification step before confirming to the sender; the rubric's destructive/batch cap of 3 applies.

3 / 5

Progressive Disclosure

For a sub-50-line skill the sectioning is good ('When to use' as a bolded section), and the bundle script scripts/agentteams-sync.sh matches the command name, but the body never signals or links that script, a minor navigation gap.

4 / 5

Total

16

/

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.

A strong description with a clear what and an explicit, concrete when-clause populated with natural trigger terms. Its only weaknesses are modest action coverage (a single 'sync' verb) and some overlap risk with generic file-sync skills.

DimensionReasoningScore

Specificity

It names the domain and one concrete action ('Sync files with centralized storage') but offers no further concrete actions or detail on what syncing entails — matching anchor 3, not 4 which expects several specific actions.

3 / 5

Completeness

It explicitly answers both what ('Sync files with centralized storage') and when ('Use when your coordinator or another Worker notifies you of file updates (config changes, task files, shared data, collaboration artifacts)') with concrete trigger phrases, matching the anchor-5 example structure.

5 / 5

Trigger Term Quality

Natural terms like 'file updates', 'config changes', 'task files', 'shared data', and 'coordinator' are present, but a few natural phrasings users would say (e.g. 'sync', 'pull latest files', 'new files available') are missing — matching anchor 4.

4 / 5

Distinctiveness Conflict Risk

The coordinator/Worker-notification trigger carves out a fairly distinct niche, but 'Sync files' as the leading clause leaves minor overlap risk with other file-transfer or sync skills — anchor 4, not 5, which demands a clear niche with minimal conflict.

4 / 5

Total

16

/

20

Passed

Validation

100%

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/worker-agent/skills/file-sync/SKILL.md

Revision

8a661dd

Reviewed

Table of Contents

DiscoveryImplementationValidation

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.

Claim skill