Name: github-workflow-automation
Rating: 62.2 (1 reviews)
Author: ruvnet

github-workflow-automation

Advanced GitHub Actions workflow automation with AI swarm coordination, intelligent CI/CD pipelines, and comprehensive repository management

2.41x

Quality

47%

Does it follow best practices?

Impact

87%

2.41x

Average score across 3 eval scenarios

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/github-workflow-automation/SKILL.md

The canonical home for this skill is github-workflow-automation in ruvnet/agentic-flow

Quality

Content

46%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 concrete, executable GitHub Actions examples but is severely bloated: a 1000-line monolith padded with buzzwords, redundancies, and collapsible sections, with no external reference files despite claiming progressive disclosure. Workflow guidance lacks the validation feedback loops its destructive/batch operations demand.

Suggestions

Split the 8 workflow templates and the Command Reference into separate reference files under references/ and link to them from a concise overview, fulfilling the claimed progressive_disclosure: true.

Strip marketing prose ("self-organizing", "intelligent", "adaptive") and remove the duplicated "Cache Swarm Dependencies" entry to cut token cost.

Add explicit validation/verification checkpoints (e.g. `gh pr checks --watch` before merge, dry-run before deploy, confirm before auto-creating issues) to the destructive/batch workflows so workflow_clarity can exceed the cap.

Dimension	Reasoning	Score
Conciseness	The body is a ~1000-line document padded with marketing prose ("self-organizing, adaptive GitHub workflows", "intelligent CI/CD pipelines"), redundant entries ("Cache Swarm Dependencies" appears twice), and emoji-laden collapsible headers; much of this catalog could be trimmed or moved to reference files.	2 / 5
Actionability	It provides abundant concrete, copy-paste-ready code — real `gh` CLI commands and GitHub Actions YAML with specific flags (e.g. `npx ruv-swarm actions generate-workflow --analyze-codebase --detect-languages`) — though some MCP/JS blocks read as pseudocode and depend on unverifiable packages.	4 / 5
Workflow Clarity	The skill drives destructive/batch operations (auto-deploy, auto-PR-creation, self-healing auto-fix, auto-issue-creation) yet presents a command catalog rather than a sequenced workflow with validate→fix→retry checkpoints; per the guidelines, missing validation in such contexts caps this at 3.	3 / 5
Progressive Disclosure	Despite frontmatter declaring `progressive_disclosure: true`, no references/scripts/assets bundle files exist and the entire content — 8 workflow templates, 8 modes, a full command reference — is inlined into one monolithic 1000-line file with no one-level-deep external references.	2 / 5
	Total	11 / 20 Passed

Description

48%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 names a recognizable domain and some natural trigger terms but leans heavily on marketing buzzwords ("Advanced", "intelligent", "AI swarm coordination") and omits any explicit "Use when..." guidance, capping completeness. It is distinguishable but lacks concrete, action-oriented specificity.

Suggestions

Replace buzzword adjectives ("Advanced", "intelligent", "comprehensive", "AI swarm") with concrete verbs, e.g. "Generate, optimize, and debug GitHub Actions workflows; manage PRs, releases, and CI/CD pipelines."

Add an explicit trigger clause, e.g. "Use when the user asks to create or optimize GitHub Actions workflows, debug failed CI runs, or automate PR/release/issue management."

Drop "AI swarm coordination" or move it to a secondary phrase — it is jargon users would not naturally say and adds conflict risk with a generic swarm-coordination skill.

Dimension	Reasoning	Score
Specificity	The description names the domain ("GitHub Actions workflow automation", "CI/CD pipelines", "repository management") but the actions are generic abstract nouns padded with buzzwords ("Advanced", "intelligent", "comprehensive", "AI swarm coordination") rather than concrete verbs like generate/optimize/analyze.	2 / 5
Completeness	A clear-ish "what" is present but there is no "Use when..." clause or equivalent trigger guidance, which per the guidelines caps completeness at 3; the "what" is also weakened by buzzword padding.	3 / 5
Trigger Term Quality	It includes several natural terms a user might say ("GitHub Actions", "CI/CD", "workflow", "pipelines") but dilutes them with jargon ("AI swarm coordination", "swarm") and misses common synonyms and file-path triggers like ".github/workflows".	3 / 5
Distinctiveness Conflict Risk	The core trigger "GitHub Actions workflow automation" is a fairly distinct niche with minimal conflict risk, though "comprehensive repository management" and "CI/CD pipelines" overlap slightly with the related skills it itself lists.	4 / 5
	Total	12 / 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 (1066 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/ruvector
Path: .claude/skills/github-workflow-automation/SKILL.md
Commit: 74d2a60

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.