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.mdBoard mapping configuration
Version field
0%
100%
Correct file location
100%
100%
Pending→Backlog mapping
0%
100%
Assigned→Ready mapping
0%
100%
Blocked status mapping
37%
100%
Coder label with emoji
0%
100%
Tester label with emoji
0%
100%
Critical priority label
0%
100%
Low priority label
0%
100%
Agent Count field
20%
100%
Complexity field
25%
100%
ETA field
12%
100%
All five agent types
100%
100%
Board initialization commands
Auth check present
100%
100%
Uses gh CLI for project ID
100%
100%
Uses npx ruv-swarm board-init
0%
100%
Bidirectional sync mode
0%
100%
Correct view names
0%
100%
gh field-create command
100%
100%
SINGLE_SELECT field type
100%
100%
Correct status options
0%
100%
Swarm Status field name
100%
100%
jq JSON parsing
100%
100%
Analytics, automation, and smart card rules
Load-balanced strategy
0%
100%
Assignment consideration flags
0%
100%
board-smart-move command
0%
100%
auto-progress rule
0%
100%
auto-review rule
0%
100%
auto-done rule
0%
100%
Analytics metrics
0%
100%
Analytics group-by
0%
100%
Report markdown format
0%
100%
Sprint summary report type
0%
100%
Report includes velocity/burndown/blockers
0%
100%
f547cec
Table of Contents
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.