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) but relies on high-level category names rather than concrete actions. It critically lacks a 'Use when...' clause, making it harder for Claude to know when to select this skill. The term 'swarm-coordinated' is jargon that adds confusion rather than clarity.
Suggestions
Add an explicit 'Use when...' clause with trigger scenarios, e.g., 'Use when the user asks about GitHub issues, project boards, sprint planning, backlog grooming, or task assignment.'
Replace vague category labels with concrete actions, e.g., 'Creates and triages GitHub issues, moves project board cards between columns, plans and tracks sprints with milestones.'
Remove or clarify 'swarm-coordinated' jargon and add natural user terms like 'kanban', 'backlog', 'milestone', 'agile', and 'GitHub Projects'.
| 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. 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 specific mention of project boards and sprint planning provide some distinctiveness, but 'issue tracking' could overlap with general GitHub skills or other project management tools. The 'swarm-coordinated' qualifier adds some uniqueness but is unclear in meaning. | 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 extremely bloated and largely built around fictional CLI tools (ruv-swarm, claude-flow MCP calls) that don't appear to be real, executable software, making the vast majority of its content non-actionable. While it demonstrates good structural ideas (collapsible sections, quick reference, templates), the content is far too verbose and speculative to be useful. The skill would benefit enormously from being reduced to 1/5th its size and focusing only on real, executable gh CLI commands with verified tool integrations.
Suggestions
Remove or clearly mark all speculative/fictional tool commands (npx ruv-swarm, mcp__claude-flow__) and focus on real, executable gh CLI commands and GitHub Actions workflows
Reduce content by 80%+ — move templates to separate files, eliminate redundant command variations, and cut dashboard/analytics JSON configs that have no real runtime
Add explicit validation checkpoints to multi-step workflows, especially for batch operations like stale issue closing and cross-org sync
Split large sections (issue templates, board configs, analytics) into separate referenced files to improve progressive disclosure
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at 700+ lines with 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 content enormously. Much of this could be condensed to a fraction of the size. | 1 / 3 |
Actionability | Most commands reference 'npx ruv-swarm github ...' and 'mcp__claude-flow__...' which appear to be fictional or highly speculative tools with invented CLI interfaces. The gh CLI commands are real but the bulk of the skill relies on non-existent tooling, making it largely non-executable. The JavaScript/JSON config blocks are declarative specifications with no clear runtime context. | 1 / 3 |
Workflow Clarity | The 'Complete Workflow Example' section does provide a numbered sequence of steps, and some sections show logical progressions. However, there are no validation checkpoints or error recovery steps in any of the multi-step workflows, and many destructive/batch operations (bulk close stale issues, cross-org sync) lack verification steps. | 2 / 3 |
Progressive Disclosure | Good use of HTML <details> tags for collapsible sections and a quick reference at the end. However, the skill is monolithic — all content is inline rather than split into referenced files. The sheer volume of inline content (templates, configs, analytics) should be in separate referenced documents. References to other skills exist but the core content organization is poor. | 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/agentic-flow
- Commit
8db2712
- 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.