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 third person voice, includes natural trigger terms like 'GitHub Actions', 'CI/CD', and 'workflow templates', and has an explicit 'Use when' clause. The description is concise yet comprehensive, covering the key capabilities without unnecessary verbosity.
| 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.
The skill provides a comprehensive collection of production-ready GitHub Actions workflow templates that are highly actionable and copy-paste ready. However, it suffers from being overly long by inlining too many full workflow examples rather than leveraging progressive disclosure, and it lacks validation/rollback guidance for deployment workflows. The best practices section is too superficial to be useful.
Suggestions
Move most workflow patterns to separate referenced files (e.g., assets/), keeping only 1-2 core patterns inline with clear links to the rest
Add rollback/error-recovery steps to deployment workflows (K8s deploy, production deploy) — e.g., 'if rollout status fails, run kubectl rollout undo'
Replace the generic 'Best Practices' bullet list with specific, actionable examples or remove it entirely — items like 'Use secrets for sensitive data' add no value to Claude
Remove the 'Purpose' and 'When to Use' sections which explain things Claude already understands from context
| 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 sheer volume of patterns (7 full workflow examples) makes this quite long when some could be referenced externally. | 2 / 3 |
Actionability | All workflow patterns are fully executable, copy-paste ready YAML with specific action versions, proper secret references, and realistic configurations. The examples cover real-world scenarios with complete job definitions, not pseudocode. | 3 / 3 |
Workflow Clarity | Individual workflow patterns are clear, but there's no guidance on how to compose these patterns together, no validation checkpoints for deployment workflows (e.g., the K8s deploy has a verify step but no rollback guidance if verification fails), and the 'Deployment with Approvals' pattern has a placeholder comment instead of actual deployment commands. Missing feedback loops for destructive deployment operations. | 2 / 3 |
Progressive Disclosure | There are references to asset files (e.g., 'See assets/test-workflow.yml') and related skills, which is good. However, the main file is very long (~250 lines of YAML) with 7 full workflow examples inline. Several patterns could be moved to referenced files, keeping only the most common 1-2 patterns inline with links to the rest. | 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
27a7ed9
- 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.