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

74%

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

Fix and improve this skill with Tessl

tessl review fix ./manager/agent/worker-agent/skills/file-sync/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

61%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.

The body is lean and centers on one concrete, executable command with a clear single-purpose workflow, but it duplicates its trigger conditions twice and lacks any validation step for what is a batch file-overwrite operation. The bundled sync script is also never referenced, leaving a small gap between the invoked command and the actual implementation.

Suggestions

State the trigger conditions once (either the opening sentence or the When-to-use section) and drop the duplicate to tighten the body.

Add a verification checkpoint before confirming to the sender, e.g., check the command's success output or `~/.last-pull` marker, since the sync batch-overwrites local files.

Reference the implementation explicitly (e.g., `scripts/agentteams-sync.sh`) or clarify how `agentteams-sync` resolves to it, so the command and the bundle file clearly correspond.

DimensionReasoningScore

Conciseness

The opening sentence ("When your coordinator or another Worker notifies you that files have been updated...") and the "**When to use**" paragraph ("any time you are told that new files are available, configs have changed...") state the same trigger conditions twice, mirroring the frontmatter. This is more than minor padding, so it sits at "mostly efficient but could be tightened" rather than anchor 4.

3 / 5

Actionability

The body gives a concrete, copy-paste-ready command (```bash\nagentteams-sync\n```) plus a follow-up action ("Always confirm to the sender after sync completes"), which is mostly executable guidance. Not 5 because the invoked command `agentteams-sync` does not match the bundled `scripts/agentteams-sync.sh`, and there is no guidance for the failure path.

4 / 5

Workflow Clarity

The sequence (receive notification → run `agentteams-sync` → confirm to sender) is present and unambiguous, but the sync is a batch overwrite operation pulling many files, and the body includes no validation that the sync succeeded — "confirm to the sender" is a notification, not a checkpoint. Per the rubric's cap for batch operations without validation, workflow clarity cannot exceed 3.

3 / 5

Progressive Disclosure

The body is appropriately minimal for a single-task skill (~10 lines, organized with a When-to-use callout), but the bundle's `scripts/agentteams-sync.sh` is never referenced and the command name does not obviously map to it, leaving a minor navigation gap. This matches "good structure; most content appropriately placed; minor organization gaps" rather than the clean top anchor.

4 / 5

Total

14

/

20

Passed

Description

73%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.

The description is well-structured with an explicit and specific Use-when clause carrying concrete trigger terms, giving strong completeness and low conflict risk. Its main weakness is capability specificity: it names only one generic action in second-person voice rather than listing what the sync actually does.

Suggestions

State the concrete actions in third person, e.g., "Pulls the latest configs, task briefs, and shared data from centralized storage into the local workspace and hot-reloads config changes."

Remove second-person phrasing ("your coordinator or another Worker notifies you") in favor of third-person triggers like "Use when a coordinator or Worker announces file updates".

Add natural trigger synonyms such as "new files available", "configs have changed", or "pull latest files" to broaden keyword coverage.

DimensionReasoningScore

Specificity

"Sync files with centralized storage" names the domain but offers only one minimal, generic action, matching the anchor "Names the domain but actions are minimal or generic" (e.g., "Processes PDF files"). A base of 3 (one concrete action plus the parenthetical file types) is reduced by 1 per the rubric's voice guideline because the description uses second person ("your coordinator or another Worker notifies you").

2 / 5

Completeness

"Sync files with centralized storage" clearly states what the skill does, and "Use when your coordinator or another Worker notifies you of file updates (config changes, task files, shared data, collaboration artifacts)" explicitly answers when with concrete trigger phrases — matching the top anchor. Not 4 because the when-clause is already fully explicit and specific.

5 / 5

Trigger Term Quality

"file updates (config changes, task files, shared data, collaboration artifacts)" plus "coordinator" and "Worker" give good natural keyword coverage for the multi-agent context. Not 5 because common variations like "pull latest", "new files available", or "sync files" are missing.

4 / 5

Distinctiveness Conflict Risk

The agent-coordination niche ("coordinator or another Worker notifies you") gives distinct triggers with minimal conflict risk. Not 5 because "file updates" and "config changes" could still overlap with generic file-management or config-reload skills.

4 / 5

Total

15

/

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

Reviewed

Table of Contents

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.