agent-sync-coordinator
Agent skill for sync-coordinator - invoke with $agent-sync-coordinator
42
13%
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 description is essentially a label with an invocation command rather than a functional description. It fails on every dimension: it provides no concrete actions, no natural trigger terms, no guidance on when to use it, and nothing to distinguish it from other skills. This would be nearly impossible for Claude to correctly select from a pool of available skills.
Suggestions
Describe what the skill actually does with concrete actions (e.g., 'Synchronizes file changes across multiple repositories, resolves merge conflicts, and coordinates branch updates').
Add an explicit 'Use when...' clause with natural trigger terms users would say (e.g., 'Use when the user needs to sync changes, coordinate updates between repos, or resolve synchronization conflicts').
Remove the invocation instruction ('invoke with $agent-sync-coordinator') from the description, as this is operational metadata rather than descriptive content that helps with skill selection.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. 'Agent skill for sync-coordinator' is entirely vague and does not describe what the skill 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 it from any other agent skill. 'Sync-coordinator' hints at synchronization but without specifics, it could conflict with any coordination or syncing-related skill. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
27%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 significant repetition—swarm initialization, agent spawning, and memory storage patterns are repeated nearly identically across multiple sections. While it demonstrates awareness of the relevant tools and provides structured examples, most code uses placeholder content rather than executable specifics, and the sheer volume of content (much of it redundant) undermines its utility. The lack of any content splitting or progressive disclosure for a 300+ line skill is a significant structural weakness.
Suggestions
Reduce content by at least 60%: eliminate duplicate swarm init/agent spawn patterns, remove the redundant tools listing, and consolidate the 'Synchronization Strategies' and 'Best Practices' sections which add little actionable value beyond what the examples already show.
Replace placeholder content like '[aligned package.json]' and '[synchronized content]' with realistic, minimal but concrete examples that demonstrate actual synchronization logic.
Add explicit validation checkpoints with error recovery: after npm test steps, include 'if tests fail → rollback branch → report error' rather than just describing error recovery abstractly in a separate section.
Split into multiple files: move Advanced Swarm Features, Error Handling, and Metrics into separate referenced documents, keeping SKILL.md as a concise overview with the core workflow and one primary example.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at 300+ lines with massive repetition. The tools list is duplicated from frontmatter, swarm initialization patterns are repeated 4+ times with minor variations, and sections like 'Synchronization Strategies' and 'Best Practices' contain abstract configuration objects and bullet points that add no actionable value. Concepts like version alignment and documentation sync are explained redundantly across multiple sections. | 1 / 3 |
Actionability | Provides concrete tool invocations and code patterns, but most examples use placeholder content like '[aligned package.json]', '[synchronized content]', and '[GitHub modes documentation]' rather than real executable code. The gh CLI examples have plausible structure but use pseudo-paths with '$' separators that aren't valid, and the JavaScript conflict resolver is conceptual pseudocode wrapping MCP calls rather than executable code. | 2 / 3 |
Workflow Clarity | The 'Complete Package Sync Workflow' section provides 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 handling—no 'if tests fail, do X' feedback loops. The error recovery section describes spawning agents but never shows actual recovery steps or rollback commands. | 2 / 3 |
Progressive Disclosure | Everything is crammed into a single monolithic file with no references to external files. The content is a wall of repetitive examples and sections that could easily be split into separate reference files (e.g., strategies, error handling, metrics). No bundle files are provided, and the skill makes no attempt to organize content hierarchically despite its length and complexity. | 1 / 3 |
Total | 6 / 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
9d4a9ea
- 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.