agent-project-board-sync
Agent skill for project-board-sync - invoke with $agent-project-board-sync
Install with Tessl CLI
npx tessl i github:ruvnet/claude-flow --skill agent-project-board-sync28
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 functions only as a label and invocation instruction rather than a functional description. Claude would have no basis to select this skill appropriately since there's no information about capabilities, use cases, or trigger scenarios.
Suggestions
Add concrete actions describing what the skill does (e.g., 'Synchronizes tasks between project management boards, updates card statuses, and tracks progress across platforms').
Include a 'Use when...' clause with natural trigger terms users would say (e.g., 'Use when syncing Trello, Jira, or project boards, or when the user mentions task synchronization, board updates, or project tracking').
Specify which project board platforms or systems are supported to create clear distinctiveness from other project management skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. 'Agent skill for project-board-sync' is completely abstract and doesn't describe what the skill actually does. | 1 / 3 |
Completeness | Missing both 'what does this do' and 'when should Claude use it'. The description only provides an invocation command, not any functional information. | 1 / 3 |
Trigger Term Quality | The only terms present are technical jargon ('agent skill', 'project-board-sync') and an invocation command. No natural keywords a user would say like 'sync', 'project board', 'kanban', 'tasks', etc. | 1 / 3 |
Distinctiveness Conflict Risk | While 'project-board-sync' hints at a specific domain, the description is so vague it's unclear what distinguishes this from other project management or sync-related skills. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
22%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, presenting dozens of similar CLI command patterns without a clear workflow or explanation of the core 'ruv-swarm' tool being used. While it provides concrete command examples, the lack of tool documentation, missing sequential workflows, and repetitive structure make it difficult to follow. The content would benefit from significant condensation and reorganization around a clear step-by-step process.
Suggestions
Add a 'Prerequisites' section explaining what 'npx ruv-swarm' is, how to install it, and its relationship to the MCP tools listed in frontmatter
Create a clear numbered workflow (e.g., '1. Initialize board connection, 2. Configure mapping, 3. Enable sync, 4. Validate sync status') with explicit validation checkpoints
Move detailed sections (Analytics, Team Collaboration, Advanced Sync) to separate reference files and keep only a 2-3 line summary with links in the main skill
Remove redundant command examples - keep one representative example per category rather than showing every possible flag combination
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose with extensive repetitive command examples that follow the same pattern. Many sections could be consolidated, and the document explains concepts (like what Kanban/Scrum are) that Claude already knows. The 400+ lines could be reduced to under 100 while preserving all actionable content. | 1 / 3 |
Actionability | Provides concrete bash commands and configuration examples, but relies heavily on a hypothetical 'npx ruv-swarm' CLI tool without explaining what it is or how to install it. The gh CLI examples are executable, but most commands reference an undocumented tool making them not truly copy-paste ready. | 2 / 3 |
Workflow Clarity | No clear sequential workflow for the core task of syncing a project board. Commands are presented in isolation without explaining when to use each or how they connect. Missing validation checkpoints for sync operations which could cause data loss or conflicts. | 1 / 3 |
Progressive Disclosure | References external files at the end (swarm-issue.md, multi-repo-swarm.md) which is good, but the main document is a monolithic wall of similar command examples. Content like 'Advanced Synchronization', 'Visualization & Reporting', and 'Team Collaboration' should be in separate files with brief summaries here. | 2 / 3 |
Total | 6 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (514 lines); consider splitting into references/ and linking | Warning |
Total | 10 / 11 Passed | |
- 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.