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

79%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

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

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.

The body is lean and highly actionable with real externalized scripts and a clear worked example. The main gap is the absence of a validation/verification checkpoint around the destructive MinIO push step.

Suggestions

Add an explicit verification checkpoint before pushing (e.g., confirm the local results exist and spec.md/base/ are correctly excluded) and a verify-after-push step (e.g., re-list the MinIO path with mc ls) to lift workflow clarity above 3.

Tighten the hot-reload caveats and background-sync bullets into a single concise list to remove the small amount of remaining over-explanation.

Dimension	Reasoning	Score
Conciseness	Lean sections with executable commands and tables and no padding of concepts Claude already knows; a few caveat lines could be trimmed, so it sits between anchors 4 and 5.	4 / 5
Actionability	Provides copy-paste-ready commands (hermes-sync, cat spec.md, full push-shared.sh invocation with --exclude flags) covering the common config-sync and task-push cases.	5 / 5
Workflow Clarity	Sequences are clearly laid out with a worked example, but the destructive/batch push to MinIO (--overwrite) lacks any validate-before-push or verify-after-push checkpoint, capping workflow clarity at 3 per the batch-operation guideline.	3 / 5
Progressive Disclosure	Short, well-organized single-purpose skill with scripts externalized one level deep in scripts/ (real files hermes-sync.py and push-shared.sh) and a clear path table, matching the simple-skill exception for a 5.	5 / 5
	Total	17 / 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.

The description is concise and clearly answers both what the skill does and when to use it, with natural trigger language tied to a specific coordinator/Worker context. It could list more concrete sync actions to lift specificity.

Suggestions

Name the concrete sync operations (pull config/skills, re-bridge into ~/.hermes, push results back) to raise specificity from a single 'sync' action to multiple concrete actions.

Add file/path-based synonyms (e.g., 'openclaw.json', 'SOUL.md', 'shared/tasks/', 'MinIO') to broaden natural trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ('Sync files with centralized storage') and one concrete action (sync), but does not list several specific actions, matching anchor 3 rather than 4.	3 / 5
Completeness	Explicitly answers both 'what' (sync files with centralized storage) and 'when' (use when coordinator/Worker notifies of file updates) with concrete trigger phrases, matching anchor 5.	5 / 5
Trigger Term Quality	Includes natural trigger phrases users would say ('when your coordinator or another Worker notifies you of file updates', 'config changes', 'task files', 'shared data'), with good but not comprehensive synonym/extension coverage.	4 / 5
Distinctiveness Conflict Risk	Tied to a specific coordinator/Worker notification context, making it mostly distinct with only minor overlap risk; not quite the fully distinct niche of anchor 5.	4 / 5
	Total	16 / 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/hermes-worker-agent/skills/file-sync/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.