github-automation

GitHub workflow automation, PR management, issue tracking, and code review coordination. Integrates with GitHub Actions and repository management. Use when: PR creation, code review, issue management, release automation, workflow setup. Skip when: local-only changes, non-GitHub repositories.

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

72%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.

A concise, actionable reference of GitHub automation commands with clean sectioning, but it lacks workflow sequencing and validation/verification steps for outward-facing operations like releases and PR creation.

Suggestions

Add explicit verification steps for outward-facing operations, e.g. run `gh pr checks <n>` after PR creation and confirm CI passes before merging.

Replace placeholder templates with concrete filled-in examples or clearly mark the variable portions so commands are copy-paste ready.

Drop the obvious 'Best Practices' items Claude already knows, or replace them with non-obvious project-specific conventions.

Dimension	Reasoning	Score
Conciseness	Mostly lean with executable commands, but the Purpose section restates the description and 'Best Practices' lists truisms Claude already knows ('Use conventional commits', 'Require reviews before merge').	4 / 5
Actionability	Concrete executable gh and npx claude-flow commands cover the common cases, though several are placeholder templates ('feat: description', '## Summary\n...') rather than fully copy-paste-ready.	4 / 5
Workflow Clarity	Commands are presented as discrete standalone actions with no sequencing or validation checkpoints; release management and PR creation are outward-facing operations that proceed without any verify step.	3 / 5
Progressive Disclosure	Under 50 lines with no bundle files and well-organized section headers, satisfying the simple-skill exception for progressive disclosure.	5 / 5
	Total	16 / 20 Passed

Description

92%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.

A strong, third-person description that clearly states capabilities and explicit trigger/skip conditions with low conflict risk. Its only weakness is missing synonym and extension coverage in trigger terms.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'GitHub workflow automation, PR management, issue tracking, and code review coordination' plus 'Integrates with GitHub Actions and repository management' and release automation, giving comprehensive coverage.	5 / 5
Completeness	Explicitly answers 'what' (the action list) and 'when' ('Use when: PR creation...') and even adds a 'Skip when' clause for negative guidance.	5 / 5
Trigger Term Quality	Natural phrases like 'PR creation, code review, issue management, release automation, workflow setup' map to what users say, but it lacks synonyms and file/extension variations.	4 / 5
Distinctiveness Conflict Risk	GitHub-specific niche with a 'Skip when: local-only changes, non-GitHub repositories' clause minimizes overlap with other skills.	5 / 5
	Total	19 / 20 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: ruvnet/ruflo
Path: .agents/skills/github-automation/SKILL.md
Commit: b14c79e

Reviewed: 3 days 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.