github-project-management
Comprehensive GitHub project management with swarm-coordinated issue tracking, project board automation, and sprint planning
51
26%
Does it follow best practices?
Impact
100%
1.51xAverage score across 3 eval scenarios
Critical
Do not install without reviewing
Optimize this skill with Tessl
npx tessl skill review --optimize ./.claude/skills/github-project-management/SKILL.mdQuality
Discovery
32%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description identifies a clear domain (GitHub project management) and lists several high-level capability areas, but lacks concrete action verbs and explicit trigger guidance. The term 'swarm-coordinated' is internal jargon that won't help with skill selection and adds confusion. The absence of a 'Use when...' clause significantly weakens its utility for skill routing.
Suggestions
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about GitHub issues, project boards, sprint planning, backlog grooming, or task tracking.'
Replace vague category labels with concrete actions, e.g., 'Creates and triages GitHub issues, automates project board column transitions, plans and tracks sprints with milestones.'
Remove or clarify internal jargon like 'swarm-coordinated' which users would never say, and add common user-facing terms like 'kanban', 'backlog', 'milestone', or 'agile workflow'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (GitHub project management) and some actions (issue tracking, project board automation, sprint planning), but these are more like category labels than concrete actions. It doesn't specify what concrete operations are performed (e.g., 'create issues', 'move cards between columns', 'assign milestones'). | 2 / 3 |
Completeness | Describes what it does at a high level but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per the rubric, a missing 'Use when...' clause should cap completeness at 2, and since the 'what' is also somewhat vague, this scores a 1. | 1 / 3 |
Trigger Term Quality | Includes some relevant keywords like 'GitHub', 'issue tracking', 'project board', and 'sprint planning' that users might mention. However, it misses common variations like 'kanban', 'backlog', 'milestone', 'GitHub Projects', 'task management', or 'agile'. The term 'swarm-coordinated' is internal jargon unlikely to be used by users. | 2 / 3 |
Distinctiveness Conflict Risk | The GitHub focus and mention of 'swarm-coordinated' provide some distinctiveness, but 'project management', 'issue tracking', and 'sprint planning' are broad enough to overlap with other project management or GitHub-related skills. Without clearer boundaries, there's moderate conflict risk. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
20%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 for a hypothetical swarm-based GitHub project management system. The vast majority of commands reference tools (ruv-swarm, claude-flow MCP calls) that appear speculative rather than real, documented software, making the content largely non-actionable. While structurally organized with collapsible sections and a quick reference, the document would benefit enormously from being reduced to 1/5th its size, focusing only on verified, executable commands, and splitting templates and configs into separate bundle files.
Suggestions
Verify that all 'npx ruv-swarm github ...' commands correspond to real, documented CLI subcommands; remove or clearly mark any hypothetical/aspirational features
Reduce the document to under 150 lines by extracting templates into separate files (e.g., TEMPLATES.md), configs into a configs/ directory, and keeping only core workflows in SKILL.md
Add explicit validation checkpoints and error handling to batch/destructive operations like stale issue closing, cross-org sync, and bulk card operations
Replace pseudo-API syntax (mcp__claude-flow__swarm_init) with actual executable code or clearly document the expected tool interface
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at 700+ lines. Massive amounts of speculative CLI commands for tools (ruv-swarm, claude-flow) that appear hypothetical. Includes extensive templates, dashboard JSON configs, and repetitive patterns that bloat the document enormously. Much content describes aspirational features rather than providing actionable instructions Claude needs. | 1 / 3 |
Actionability | Nearly all commands reference 'npx ruv-swarm github ...' with dozens of subcommands and flags that appear to be invented/hypothetical rather than documented real tools. The gh CLI commands are real but basic. The JavaScript blocks use pseudo-API syntax (mcp__claude-flow__swarm_init) that isn't executable. Most content describes what tools would do rather than providing verified, executable guidance. | 1 / 3 |
Workflow Clarity | The 'Complete Workflow Example' section at the end provides a reasonable 5-step sequence, and some individual sections show logical ordering. However, there are no validation checkpoints, no error handling, no feedback loops for the many destructive/batch operations (bulk close stale issues, cross-org sync, data recovery). The overall document lacks a clear workflow narrative, reading more like a feature catalog. | 2 / 3 |
Progressive Disclosure | Good use of HTML <details> tags to collapse sections, and the document has clear hierarchical headings. However, with no bundle files, all 700+ lines are crammed into a single SKILL.md. The templates, workflow YAML files, and configuration examples should be in separate referenced files. The 'Additional Resources' link to external docs but nothing is split into companion files. | 2 / 3 |
Total | 6 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (1278 lines); consider splitting into references/ and linking | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Repository
- ruvnet/ruvector
- Commit
edf6b04
- 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.