agent-project-board-sync

Agent skill for project-board-sync - invoke with $agent-project-board-sync

4.00x

Quality

Does it follow best practices?

Impact

100%

4.00x

Average score across 3 eval scenarios

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/agent-project-board-sync/SKILL.md

Quality

Content

0%Scale 1-3

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 extensive but largely non-functional feature catalog for a seemingly non-existent `npx ruv-swarm` CLI tool. The commands are not executable, the content is extremely verbose without adding actionable value, and there is no coherent workflow or validation structure. The skill reads more like a marketing feature list than an operational guide Claude could follow.

Suggestions

Replace fabricated `npx ruv-swarm` commands with actual executable `gh` CLI commands and MCP tool calls that Claude can use to interact with GitHub Projects

Reduce content to under 100 lines focusing on a clear sequential workflow: authenticate → find/create project → sync tasks → verify sync status, with explicit validation at each step

Add validation checkpoints and error recovery steps, especially for sync operations that could fail or create conflicts

Move configuration schemas and dashboard examples to separate referenced files, keeping SKILL.md as a concise overview with links to detailed materials

Dimension	Reasoning	Score
Conciseness	Extremely verbose at 400+ lines. Most commands reference a hypothetical `npx ruv-swarm` CLI with dozens of subcommands that appear fabricated/non-existent. Massive amounts of configuration examples (YAML, JSON, bash) that are not executable and serve as padding. The skill explains obvious concepts like board organization best practices that Claude already knows.	1 / 3
Actionability	Nearly all commands use `npx ruv-swarm github ...` which appears to be a non-existent tool - these are not executable. The `gh` CLI commands mixed in are partially real but incomplete and contain syntax errors (e.g., `$dev$null` instead of `/dev/null`, broken URL paths with `$` instead of `/`). The vast majority of code blocks are aspirational pseudocode disguised as real commands.	1 / 3
Workflow Clarity	No clear sequential workflow with validation checkpoints. The skill is organized as a feature catalog listing dozens of independent commands without explaining when or how to use them together. There are no feedback loops, no error recovery steps, and no validation between steps despite dealing with sync operations that could fail or cause data conflicts.	1 / 3
Progressive Disclosure	Monolithic wall of content with 15+ sections all inline. References to `swarm-issue.md` and `multi-repo-swarm.md` at the bottom use broken paths (`.$swarm-issue.md`). No bundle files exist to support the references. Content that should be in separate files (configuration schemas, dashboard configs, view configs) is all dumped inline.	1 / 3
	Total	4 / 12 Passed

Description

0%Scale 1-3

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

Validation

90%

Warnings & errors only

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/claude-flow
Path: .agents/skills/agent-project-board-sync/SKILL.md
Commit: 913f9ea

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.