agent-sync-coordinator
Agent skill for sync-coordinator - invoke with $agent-sync-coordinator
37
6%
Does it follow best practices?
Impact
87%
1.61xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./.agents/skills/agent-sync-coordinator/SKILL.mdQuality
Discovery
0%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is an extremely weak description that provides virtually no useful information for skill selection. It only names the skill and its invocation command without describing any capabilities, use cases, or trigger conditions. It reads more like a stub or placeholder than a functional skill description.
Suggestions
Add concrete actions describing what sync-coordinator actually does (e.g., 'Synchronizes file changes across branches, resolves merge conflicts, coordinates parallel edits').
Add an explicit 'Use when...' clause with natural trigger terms users would say (e.g., 'Use when the user needs to sync changes, resolve conflicts, or coordinate updates across multiple sources').
Replace the invocation instruction ('invoke with $agent-sync-coordinator') with functional context — invocation details belong in the skill body, not the description used for skill selection.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. 'Agent skill for sync-coordinator' is entirely abstract with no indication of what it actually does. | 1 / 3 |
Completeness | Neither 'what does this do' nor 'when should Claude use it' is answered. The description only states it's an agent skill and how to invoke it, providing no functional or contextual information. | 1 / 3 |
Trigger Term Quality | The only keyword is 'sync-coordinator' which is a technical internal name, not a natural term a user would say. There are no natural language trigger terms like 'synchronize', 'coordinate', 'merge', etc. | 1 / 3 |
Distinctiveness Conflict Risk | The description is so vague that it's impossible to distinguish from any other agent or coordination skill. 'Sync-coordinator' could overlap with file syncing, data synchronization, team coordination, or many other domains. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
12%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is excessively verbose with heavy repetition of swarm initialization patterns and non-executable pseudo-code throughout. The code examples mix incompatible syntaxes, use broken path separators ('$' instead of '/'), and rely on placeholder content rather than concrete, copy-paste-ready commands. The file would benefit enormously from being reduced to ~25% of its current size with actually executable examples and proper progressive disclosure to separate files.
Suggestions
Reduce the file to a concise overview (~50-80 lines) with one clear executable example per pattern, and move advanced swarm coordination, conflict resolution, and metrics into separate referenced files.
Replace all placeholder content ('[aligned package.json]', '[synchronized content]') with minimal but real, executable examples that demonstrate actual synchronization operations.
Fix path separators from '$' to '/' throughout all code examples to make them functional, and choose a consistent syntax (either MCP tool call format or JavaScript, not a mix).
Add explicit validation checkpoints with concrete error recovery steps (e.g., 'If npm test fails, run X to identify the breaking change, then revert with Y') instead of abstract descriptions of spawning error recovery agents.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at ~300+ lines with massive redundancy. The tools list is duplicated from frontmatter, swarm initialization patterns are repeated 4+ times, and sections like 'Synchronization Strategies' contain non-executable config objects that add no actionable value. Concepts like version alignment and documentation sync are over-explained with decorative pseudo-code. | 1 / 3 |
Actionability | Despite extensive code blocks, almost none are executable. Examples use placeholder content like '[aligned package.json]', '[synchronized content]', and pseudo-JavaScript that mixes MCP tool calls with async/await syntax inconsistently. Path separators use '$' instead of '/', making commands non-functional. The 'Synchronization Strategies' section contains JavaScript config objects that aren't connected to any executable workflow. | 1 / 3 |
Workflow Clarity | The batch synchronization example shows a reasonable sequence (read state → push files → run tests → track progress → store state), and validation via npm test is included. However, there are no explicit validation checkpoints with error recovery feedback loops — if tests fail, there's no guidance on what to do. The error handling section describes spawning agents but provides no concrete recovery steps. | 2 / 3 |
Progressive Disclosure | The entire skill is a monolithic wall of text with no references to external files. Content that could be split (advanced swarm features, conflict resolution, metrics, error handling) is all inline, making the file extremely long. There's no clear quick-start section separated from advanced content, and the structure encourages reading everything rather than finding what's needed. | 1 / 3 |
Total | 5 / 12 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 — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- ruvnet/claude-flow
- Commit
f547cec
- 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.