github-workflow-automation

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

2.41x

Quality

50%

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

Quality

Content

50%

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

The body is rich with concrete commands and ready-to-use workflow templates, but it is bloated, mixes pseudo-syntax with real code, omits validation checkpoints in risky workflows, and keeps everything inline in one monolithic file instead of splitting into reference files.

Suggestions

Split the catalog (workflow templates, command reference, best practices, real-world examples) into separate reference files and keep SKILL.md a concise overview that links one level deep.

Add explicit validation/retry checkpoints to the batch-operations, deployment, and self-healing workflows (e.g. verify gh auth before batch PR creation; confirm risk level before auto-execute deploy).

Replace the non-executable mcp__claude-flow__ and "[Concurrent Execution]" pseudo-blocks with real, copy-pasteable commands or clearly label them as illustrative patterns.

Dimension	Reasoning	Score
Conciseness	Prose is concrete and does not condescendingly explain basics, but the ~600-line body is bloated with near-duplicate sections (8 modes, 8 templates, 3 full workflows) and buzzword framing ("self-organizing, adaptive GitHub workflows") that could be dramatically tightened.	2 / 3
Actionability	Extensive concrete bash/YAML commands and full workflows are present, but several blocks use non-executable pseudo-syntax (mcp__claude-flow__ calls, the "[Concurrent Execution]" block) and many flags reference tools/behavior (ruv-swarm, --auto-fix-common) that read as illustrative rather than verified, so guidance is not uniformly executable.	2 / 3
Workflow Clarity	There is a setup checklist and a debug/failure-analysis flow, but the main task workflows (batch operations, progressive deployment) lack explicit validation checkpoints and retry feedback loops; per the rubric, missing validation in batch/destructive operations caps this at 2.	2 / 3
Progressive Disclosure	Despite the frontmatter progressive_disclosure: true and liberal use of <details> tags, the entire skill is a single monolithic file with all content inline and no reference/bundle files; content that should be split (templates, command reference, best practices) is not separated out.	2 / 3
	Total	8 / 12 Passed

Description

50%

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 GitHub Actions niche but relies on buzzword-heavy, abstract phrasing and omits any explicit "Use when" trigger guidance. It is adequate but generic enough to overlap with sibling skills.

Suggestions

Replace abstract nouns with concrete actions, e.g. "Generate, optimize, and debug GitHub Actions workflows; coordinate multi-repo releases and automated PR reviews."

Add an explicit trigger clause: "Use when the user asks to create or optimize GitHub Actions workflows, fix failed CI runs, or coordinate multi-repo CI/CD."

Drop filler adjectives ("Advanced", "intelligent", "comprehensive") and "AI swarm coordination" jargon to sharpen distinctiveness from the ci-cd-optimization and release-coordination skills.

Dimension	Reasoning	Score
Specificity	Names the domain and several areas ("AI swarm coordination, intelligent CI/CD pipelines, and comprehensive repository management") but uses abstract noun phrases and buzzwords ("Advanced", "intelligent", "comprehensive") rather than concrete verbs like generate/optimize/analyze, so it is not a comprehensive list of specific actions.	2 / 3
Completeness	States what the skill does but has no "Use when..." clause or equivalent trigger guidance; per the rubric a missing explicit trigger caps completeness at 2.	2 / 3
Trigger Term Quality	Includes some natural terms a user would say ("GitHub Actions", "CI/CD pipelines", "repository management") but mixes in jargon ("AI swarm coordination") and misses common variations, so coverage is partial.	2 / 3
Distinctiveness Conflict Risk	It targets a GitHub Actions niche, but "repository management" and "CI/CD pipelines" overlap with the related skills listed at the end (ci-cd-optimization, release-coordination), so conflict risk remains.	2 / 3
	Total	8 / 12 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/agentic-flow
Path: .claude/skills/github-workflow-automation/SKILL.md
Commit: d069fff

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