agent-project-board-sync
Agent skill for project-board-sync - invoke with $agent-project-board-sync
35
0%
Does it follow best practices?
Impact
100%
4.00xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./.agents/skills/agent-project-board-sync/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 placeholder that provides no useful information for skill selection. It names the skill's internal identifier but fails to describe any capabilities, use cases, or trigger conditions. Claude would have no basis for selecting this skill over any other when presented with a user request.
Suggestions
Add concrete actions describing what the skill does, e.g., 'Synchronizes tasks between project boards, updates card statuses, and maps columns across platforms like Jira, Trello, or GitHub Projects.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks to sync project boards, update task statuses across platforms, or keep kanban boards in sync.'
Remove the invocation instruction ('invoke with $agent-project-board-sync') from the description and replace it with capability and trigger information that helps Claude decide when to select this skill.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description provides no concrete actions whatsoever. 'Agent skill for project-board-sync' is entirely vague and does not describe what the skill actually does. | 1 / 3 |
Completeness | The description fails to answer both 'what does this do' and 'when should Claude use it'. There is no explanation of capabilities and no 'Use when...' clause or equivalent trigger guidance. | 1 / 3 |
Trigger Term Quality | The only potentially relevant term is 'project-board-sync', which is a technical/internal identifier rather than a natural keyword a user would say. No natural language trigger terms like 'project board', 'sync tasks', 'kanban', etc. are present. | 1 / 3 |
Distinctiveness Conflict Risk | The description is so vague that it's impossible to distinguish it from other skills. 'Project-board-sync' hints at a niche but without any elaboration, it could overlap with any project management or synchronization skill. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is an extremely verbose feature catalog of mostly fictional CLI commands for a hypothetical 'ruv-swarm' tool. It lacks executable, verifiable commands, has no clear workflow with validation steps, and dumps hundreds of lines of aspirational functionality into a single file. The content reads more like a marketing feature list than actionable instructions for Claude.
Suggestions
Replace fictional 'npx ruv-swarm github ...' commands with actual working gh CLI commands and real tool integrations that Claude can execute
Reduce content to a focused workflow: initialize project → sync tasks → track progress, with explicit validation steps between each phase
Move configuration examples (YAML mapping, view configs, dashboard JSON) into separate bundle reference files and link to them from a concise overview
Add concrete input/output examples showing what a successful sync looks like, rather than listing dozens of hypothetical features
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at ~400+ lines. Massive amounts of speculative CLI commands for a tool (ruv-swarm) that appears hypothetical. Includes dashboard JSON configs, view configurations, team metrics, standup automation, and dozens of features that pad the content enormously. Most sections explain concepts Claude already knows (agile, kanban, sprint management) and many commands are aspirational rather than real. | 1 / 3 |
Actionability | Nearly all commands reference 'npx ruv-swarm github ...' subcommands that appear to be fictional/aspirational rather than real executable commands. The gh CLI commands mixed in are real but incomplete (e.g., $PROJECT_ID never properly set, broken URL paths with '$' instead of '/'). None of this is copy-paste ready or verified to work. | 1 / 3 |
Workflow Clarity | No clear sequential workflow with validation checkpoints. The content is organized as a feature catalog rather than a step-by-step process. There are no feedback loops, no error recovery steps, and no validation between destructive/batch operations like bulk card operations or cross-org sync. The troubleshooting section just lists more fictional commands. | 1 / 3 |
Progressive Disclosure | Monolithic wall of content with no meaningful separation. Everything is dumped into one massive file with no referenced bundle files. References to swarm-issue.md and multi-repo-swarm.md at the bottom, but no bundle files exist. The YAML config, JavaScript config, and bash commands for dozens of features should be split into separate reference files. | 1 / 3 |
Total | 4 / 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 | |
- Repository
- ruvnet/ruflo
- Commit
367cb82
- 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.