github-actions-templates
Create production-ready GitHub Actions workflows for automated testing, building, and deploying applications. Use when setting up CI/CD with GitHub Actions, automating development workflows, or creating reusable workflow templates.
87
82%
Does it follow best practices?
Impact
93%
1.02xAverage score across 3 eval scenarios
Passed
No known issues
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong skill description that clearly communicates what the skill does and when to use it. It uses specific, natural trigger terms like 'GitHub Actions', 'CI/CD', and 'workflow templates' that users would naturally mention. The explicit 'Use when' clause with multiple trigger scenarios makes it easy for Claude to select this skill appropriately.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'automated testing, building, and deploying applications', 'setting up CI/CD', 'automating development workflows', 'creating reusable workflow templates'. These are concrete, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (create production-ready GitHub Actions workflows for testing, building, deploying) and 'when' (explicit 'Use when' clause covering CI/CD setup, automating workflows, and creating reusable templates). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'GitHub Actions', 'CI/CD', 'workflows', 'automated testing', 'building', 'deploying', 'workflow templates'. These cover the primary terms a user would naturally use when requesting this kind of help. | 3 / 3 |
Distinctiveness Conflict Risk | Clearly scoped to GitHub Actions specifically, which distinguishes it from general CI/CD skills, deployment skills, or other automation tools. The mention of 'GitHub Actions' and 'workflow templates' creates a distinct niche unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides highly actionable, production-ready GitHub Actions templates covering common CI/CD patterns. Its main weakness is length—it inlines many complete YAML workflows that could be referenced from asset files, making it more of a template library than a concise skill guide. It also lacks workflow-level validation guidance (testing workflows, debugging failures, rollback strategies) which would improve its practical utility.
Suggestions
Move full YAML workflow examples to referenced asset files and keep only minimal snippets or key configuration highlights inline to improve conciseness and progressive disclosure.
Add a workflow validation section covering how to test workflows locally (e.g., using `act`), common debugging steps for failed runs, and how to verify workflow syntax before pushing.
Replace the generic 'Best Practices' bullet list with specific, actionable examples (e.g., show a before/after of caching, or a concrete reusable workflow pattern) or remove it entirely.
Add rollback/error recovery guidance for deployment workflows (e.g., what to do when kubectl rollout status fails).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient with concrete YAML examples, but includes some unnecessary sections like 'Purpose' and 'When to Use' that explain things Claude already knows. The 'Best Practices' list is a set of vague one-liners that add little value. The overall length (~200 lines of YAML templates) could be trimmed by referencing asset files more aggressively. | 2 / 3 |
Actionability | All workflow patterns are fully executable, copy-paste ready YAML with specific action versions, proper syntax, and realistic configurations. The examples cover real-world scenarios (Docker builds, K8s deploys, matrix builds, security scanning) with concrete details like registry URLs, permissions blocks, and caching strategies. | 3 / 3 |
Workflow Clarity | Individual workflow files are well-structured, but there's no guidance on the overall process of creating/validating workflows. The Kubernetes deployment pattern includes a verification step, which is good, but there are no validation checkpoints for the workflow creation process itself (e.g., how to test workflows locally with `act`, how to debug failures, or feedback loops for fixing broken pipelines). Deployment workflows lack rollback steps. | 2 / 3 |
Progressive Disclosure | References to asset files (e.g., 'See assets/test-workflow.yml') and related skills are present, which is good. However, the skill itself is quite long with many full YAML blocks inline that could be in referenced files. The main SKILL.md tries to be both an overview and a comprehensive reference, rather than a concise overview pointing to detailed materials. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- wshobson/agents
- Commit
91fe43e
- 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.