github-workflow-automation
Advanced GitHub Actions workflow automation with AI swarm coordination, intelligent CI/CD pipelines, and comprehensive repository management
Install with Tessl CLI
npx tessl i github:ruvnet/agentic-flow --skill github-workflow-automation45
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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 (GitHub Actions, CI/CD) but relies heavily on vague buzzwords like 'advanced', 'intelligent', and 'comprehensive' without specifying concrete actions. The complete absence of a 'Use when...' clause significantly weakens its utility for skill selection, and the phrase 'AI swarm coordination' is unclear jargon that doesn't help users or Claude understand when to apply this skill.
Suggestions
Add an explicit 'Use when...' clause with natural trigger terms like 'GitHub Actions', 'workflow', 'CI/CD pipeline', 'build failing', 'deploy automation', or '.github/workflows'.
Replace vague modifiers ('advanced', 'intelligent', 'comprehensive') with specific actions like 'create and debug GitHub Actions workflows, configure CI/CD pipelines, manage secrets and environment variables'.
Clarify or remove 'AI swarm coordination' - either explain what this means in practical terms or replace with user-recognizable capabilities.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (GitHub Actions, CI/CD) and mentions some capabilities (workflow automation, repository management), but uses vague modifiers like 'advanced', 'intelligent', and 'comprehensive' without listing concrete actions like 'create workflows', 'debug pipeline failures', or 'configure triggers'. | 2 / 3 |
Completeness | Describes what the skill does at a high level but completely lacks a 'Use when...' clause or any explicit trigger guidance. There is no indication of when Claude should select this skill over others. | 1 / 3 |
Trigger Term Quality | Includes relevant keywords like 'GitHub Actions', 'CI/CD', 'pipelines', and 'repository management' that users might say, but misses common variations like 'workflows', 'yaml', 'build failures', 'deploy', or 'actions.yml'. The term 'AI swarm coordination' is technical jargon unlikely to be used by users. | 2 / 3 |
Distinctiveness Conflict Risk | The GitHub Actions focus provides some distinctiveness, but 'repository management' and 'CI/CD pipelines' are broad enough to overlap with general Git skills or other DevOps-related skills. The 'AI swarm coordination' phrase is distinctive but unclear in meaning. | 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 suffers from severe verbosity, presenting what could be a 100-line reference as an 800+ line document. While it provides many concrete code examples and YAML templates, the reliance on potentially fictional tooling (ruv-swarm, claude-flow@alpha) undermines actionability. The structure uses collapsible sections but fails to achieve true progressive disclosure by keeping all content inline rather than referencing external files.
Suggestions
Reduce content by 70-80% by removing redundant command examples, eliminating explanations of concepts Claude knows (CI/CD basics, what GitHub Actions are), and consolidating similar sections
Move detailed YAML templates and command references to separate files (e.g., TEMPLATES.md, COMMANDS.md) and link to them from a concise overview
Add explicit validation steps to workflows involving deployments or batch operations (e.g., 'Verify deployment health before proceeding to next stage')
Clarify the actual availability and installation of referenced tools (ruv-swarm, claude-flow@alpha) or replace with standard, verifiable tooling
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at 800+ lines with excessive repetition. Many commands are shown multiple times across sections, and the collapsible sections contain redundant information. The skill explains concepts Claude already knows (what CI/CD is, what GitHub Actions are) and includes unnecessary metadata like version history and maintainer info. | 1 / 3 |
Actionability | Provides concrete bash commands and YAML templates that appear executable, but relies heavily on fictional packages ('ruv-swarm', 'claude-flow@alpha') without explaining their actual availability or installation. Many commands reference tools that may not exist, making copy-paste execution uncertain. | 2 / 3 |
Workflow Clarity | Multi-step workflows are present (e.g., the Full-Stack CI/CD example shows job dependencies), but validation checkpoints are largely missing. The 'Self-Healing Pipeline' mentions auto-fix but lacks explicit verify-then-proceed patterns. No feedback loops for error recovery in most workflows. | 2 / 3 |
Progressive Disclosure | Uses collapsible sections extensively which is good structure, but the content within each section is still too verbose. References to related skills at the bottom are helpful, but the main content doesn't effectively split detailed reference material into separate files - everything is inline in one massive document. | 2 / 3 |
Total | 7 / 12 Passed |
Validation
81%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 (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 | 9 / 11 Passed | |
- Reviewed
Table of Contents
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.