agent-sync-coordinator
Agent skill for sync-coordinator - invoke with $agent-sync-coordinator
Install with Tessl CLI
npx tessl i github:ruvnet/claude-flow --skill agent-sync-coordinator31
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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 critically deficient across all dimensions. It provides only an invocation command without explaining what the skill does, when to use it, or what problems it solves. Claude would have no basis for selecting this skill appropriately from a list of available skills.
Suggestions
Add concrete actions describing what sync-coordinator does (e.g., 'Synchronizes files between directories, resolves merge conflicts, coordinates multi-agent workflows').
Add an explicit 'Use when...' clause with natural trigger terms users would say (e.g., 'Use when the user needs to sync files, coordinate tasks, or resolve synchronization conflicts').
Remove the invocation syntax from the description and replace with functional content - invocation details belong elsewhere in the skill file.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. 'Agent skill for sync-coordinator' is completely abstract with no indication of what the skill actually does. | 1 / 3 |
Completeness | The description fails to answer both 'what does this do' and 'when should Claude use it'. It only provides an invocation command with no functional description or usage guidance. | 1 / 3 |
Trigger Term Quality | The only potential trigger term is 'sync-coordinator' which is technical jargon, not a natural phrase users would say. No common variations or user-friendly keywords are provided. | 1 / 3 |
Distinctiveness Conflict Risk | While the specific agent name 'sync-coordinator' is unique, the description is so vague that Claude cannot determine when to use it versus any other skill. 'Sync' could apply to many different synchronization tasks. | 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 and repetitive, explaining swarm coordination concepts multiple times and providing redundant code examples. While it attempts to be comprehensive, the lack of executable code (using placeholders and pseudocode), missing validation checkpoints in workflows, and monolithic structure significantly reduce its practical utility. The content would benefit from aggressive condensation and restructuring into a concise overview with linked reference materials.
Suggestions
Reduce content by 75% - remove redundant explanations of swarm coordination, consolidate similar code examples, and eliminate the tools list (already in YAML frontmatter)
Replace placeholder code ('[aligned package.json]', '[synchronized CLAUDE.md]') with minimal but complete executable examples or explicit instructions to customize
Add explicit validation checkpoints to workflows: after each sync operation, include a concrete validation step with error handling before proceeding
Split into multiple files: keep SKILL.md as a concise overview (<100 lines) and move detailed examples, strategies, and metrics to linked reference documents like SYNC-PATTERNS.md and TROUBLESHOOTING.md
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at 400+ lines with massive redundancy. The YAML frontmatter tools are repeated in the body, concepts like swarm coordination are over-explained, and there are multiple nearly-identical code examples showing the same patterns. Much content could be condensed to 1/4 the size. | 1 / 3 |
Actionability | Provides code examples but they are pseudocode/illustrative rather than executable. The JavaScript examples use undefined functions (mcp__claude_flow__swarm_init as async function), contain placeholder content like '[aligned package.json]', and the bash commands have syntax issues (using $ instead of / in paths). | 2 / 3 |
Workflow Clarity | Multi-step workflows are present but validation checkpoints are weak. The 'Complete Package Sync Workflow' shows steps but lacks explicit error handling between steps. The 'Error Handling and Recovery' section describes concepts but doesn't provide concrete validation-fix-retry loops integrated into the main workflows. | 2 / 3 |
Progressive Disclosure | Monolithic wall of text with no references to external files. All content is inline including detailed examples, strategies, metrics, and error handling that could be split into separate reference documents. No clear navigation structure or links to supplementary materials. | 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.
- 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.