github-project-management

Comprehensive GitHub project management with swarm-coordinated issue tracking, project board automation, and sprint planning

1.51x

Quality

33%

Does it follow best practices?

Impact

100%

1.51x

Average score across 3 eval scenarios

Securityby

Critical

Do not install without reviewing

Optimize this skill with Tessl

npx tessl skill review --optimize ./.claude/skills/github-project-management/SKILL.md

Quality

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 the domain and lists relevant capabilities but relies on vague buzzwords ('comprehensive', 'swarm-coordinated') without explaining concrete actions. The critical weakness is the complete absence of explicit trigger guidance, making it difficult for Claude to know when to select this skill over others.

Suggestions

Add a 'Use when...' clause with explicit triggers like 'Use when the user asks about GitHub issues, project boards, sprints, or mentions managing GitHub Projects'

Replace vague terms like 'comprehensive' and 'swarm-coordinated' with specific actions such as 'create issues, assign labels, move cards between columns, plan sprints'

Include common keyword variations users might say: 'issues', 'milestones', 'kanban board', 'backlog grooming', 'GitHub Projects'

Dimension	Reasoning	Score
Specificity	Names the domain (GitHub project management) and lists several actions (issue tracking, project board automation, sprint planning), but uses vague modifiers like 'comprehensive' and 'swarm-coordinated' without explaining concrete operations.	2 / 3
Completeness	Describes what the skill does but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill.	1 / 3
Trigger Term Quality	Includes relevant keywords like 'GitHub', 'issue tracking', 'project board', and 'sprint planning' that users might say, but missing common variations like 'issues', 'milestones', 'kanban', 'backlog', or 'GitHub Projects'.	2 / 3
Distinctiveness Conflict Risk	GitHub-specific focus provides some distinction, but 'project management' and 'issue tracking' are broad enough to potentially overlap with generic project management or other GitHub-related skills.	2 / 3
	Total	7 / 12 Passed

Implementation

35%

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 comprehensive but suffers from severe verbosity, making it impractical for context window efficiency. While it provides many concrete commands, the reliance on hypothetical tooling (ruv-swarm, claude-flow MCP calls) undermines actionability. The structure attempts progressive disclosure with collapsible sections but fails to split content appropriately across files.

Suggestions

Reduce content by 70-80% by moving templates, configurations, and detailed examples to separate referenced files (e.g., TEMPLATES.md, ANALYTICS.md, WORKFLOWS.md)

Remove or clearly mark hypothetical tools (ruv-swarm, mcp__claude-flow__*) - either document real tools or explicitly state these are conceptual examples

Add explicit validation checkpoints to workflows, especially for board sync operations (e.g., 'Verify sync completed: gh project item-list | grep <issue>')

Consolidate redundant command patterns - many sections repeat similar npx ruv-swarm commands with minor variations that could be a single parameterized example

Dimension	Reasoning	Score
Conciseness	Extremely verbose at 1000+ lines with massive redundancy. Many commands are variations of the same pattern repeated across sections. The skill explains concepts Claude already knows (what sprints are, what kanban is) and includes excessive template examples that could be referenced externally.	1 / 3
Actionability	Provides concrete CLI commands and code examples, but relies heavily on hypothetical tools (npx ruv-swarm, mcp__claude-flow__*) that may not exist or work as shown. Many examples are pseudocode-like configurations rather than executable commands, and the mcp__ syntax appears to be made-up notation.	2 / 3
Workflow Clarity	Multi-step processes are present but lack explicit validation checkpoints. The 'Complete Workflow Example' shows a sequence but doesn't include verification steps between stages. No feedback loops for error recovery when commands fail, and no guidance on what to do if sync operations encounter conflicts.	2 / 3
Progressive Disclosure	Uses collapsible <details> sections which helps organization, but the sheer volume of inline content is overwhelming. References to external resources exist at the bottom, but the skill itself is monolithic. Content that should be in separate files (templates, configurations, analytics) is all inline.	2 / 3
	Total	7 / 12 Passed

Validation

81%

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 — 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/ruv-FANN
Commit: 46f6f8a

Reviewed: about 1 month 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.