Name: github-project-management
Rating: 72.8 (1 reviews)
Author: ruvnet

github-project-management

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

1.51x

Quality

60%

Does it follow best practices?

Impact

100%

1.51x

Average score across 3 eval scenarios

Securityby

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/github-project-management/SKILL.md

The canonical home for this skill is github-project-management in ruvnet/agentic-flow

Quality

Content

53%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The skill is rich with executable commands and reasonably organized with collapsible sections, but it is an oversized monolith that should be split into reference files and lacks validation checkpoints around its destructive and batch operations. Redundant sections and a hard-coded date further hurt token efficiency.

Suggestions

Split the issue templates, specialized swarm strategies, and full command catalogs into separate reference files (e.g., TEMPLATES.md, COMMANDS.md) and link to them one level deep from SKILL.md.

Add explicit validation/dry-run checkpoints to destructive and batch workflows (e.g., 'review suggested stale-issue actions before closing', '--dry-run' for bulk card operations).

Remove the redundant 'Quick Reference Commands' section and the hard-coded 'Last Updated: 2025-10-19' line, or move version metadata to a deprecated/changelog section.

Dimension	Reasoning	Score
Conciseness	The body is a ~1240-line command catalog that mostly avoids explaining concepts Claude already knows, but it is heavily padded with redundant sections (e.g., 'Quick Reference Commands' repeats earlier commands) and a dated 'Last Updated: 2025-10-19' line that should live in a deprecated/metadata area.	3 / 5
Actionability	Abundant concrete, mostly executable gh CLI and npx ruv-swarm commands cover common cases; minor gaps come from placeholder values ('owner: "org"') and MCP calls shown as illustrative pseudo-JSON rather than runnable invocations.	4 / 5
Workflow Clarity	Numbered sequences exist (e.g., the 'Complete Workflow Example'), but batch and destructive operations — bulk issue creation, stale-issue auto-close, cross-org sync, bulk card moves — run without validation/dry-run checkpoints, which per the rubric caps workflow_clarity at 3.	3 / 5
Progressive Disclosure	This is a monolithic SKILL.md with no bundle files; templates, full command catalogs, and dashboards that clearly belong in separate reference files are all inlined, with only collapsible <details> tags for navigation and no one-level-deep file references.	2 / 5
	Total	12 / 20 Passed

Description

66%Weight 40%Scale 1-5

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 clearly conveys what the skill does across three concrete domains but lacks any 'when to use' trigger guidance, capping completeness. It is well-targeted with only minor conflict risk against sibling GitHub skills.

Suggestions

Append an explicit 'Use when...' clause naming concrete trigger phrases (e.g., 'Use when managing GitHub issues, project boards, sprints, or swarm-coordinated task tracking').

Tighten the verbs from abstract nouns ('management', 'automation') to concrete actions (e.g., 'create and triage issues, sync project boards, plan sprints').

Add common synonyms or tokens a user might naturally say (e.g., 'kanban', 'milestones', 'agile board') to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain and three concrete capability areas — 'swarm-coordinated issue tracking, project board automation, and sprint planning' — but the verbs ('management', 'tracking', 'automation', 'planning') stay moderately high-level rather than enumerating specific actions, leaving minor coverage gaps.	4 / 5
Completeness	Provides a clear 'what' but no 'Use when...' or equivalent explicit trigger guidance, which per the rubric caps completeness at 3.	3 / 5
Trigger Term Quality	Includes natural phrases users say ('GitHub project management', 'issue tracking', 'project board', 'sprint planning'); a few common variants and synonyms are missing and there are no file extensions.	4 / 5
Distinctiveness Conflict Risk	The 'GitHub project management' niche with board automation and sprint planning is mostly distinct; minor overlap risk with related skills like github-pr-workflow and github-release-management.	4 / 5
	Total	15 / 20 Passed

Validation

87%

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 — 14 / 16 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	14 / 16 Passed

Repository: ruvnet/RuView
Path: .claude/skills/github-project-management/SKILL.md
Commit: a76adc3

Reviewed: about 2 hours 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.