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.
68
82%
Does it follow best practices?
Impact
—
No eval scenarios have been run
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.
This skill provides a solid collection of production-ready, copy-paste GitHub Actions workflow templates covering common CI/CD scenarios. Its main strengths are actionability and breadth of coverage. However, it lacks workflow guidance for actually implementing these patterns (validation, troubleshooting, rollback), references non-existent bundle files, and includes some unnecessary explanatory content that Claude doesn't need.
Suggestions
Add validation and verification guidance: include steps like testing workflows locally with 'act', checking that required secrets are configured, and rollback procedures for deployment workflows.
Remove or populate the referenced asset files (assets/test-workflow.yml, assets/deploy-workflow.yml, assets/matrix-build.yml) — currently they are dead references that mislead.
Trim the 'Purpose', 'When to Use', and 'Best Practices' sections — these are either obvious to Claude or too vague to be actionable. Replace the best practices list with concrete examples or remove it.
Add a troubleshooting section covering common failure modes (e.g., permission errors, cache misses, secret misconfiguration) with specific diagnostic commands.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill provides many complete YAML examples which are useful as templates, but there's redundancy across patterns (e.g., checkout steps repeated everywhere) and the 'Purpose' and 'When to Use' sections explain things Claude already knows. The best practices list is a set of vague one-liners that add little value. Overall moderately efficient but could be tightened. | 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 including matrix builds, Docker builds, Kubernetes deployments, security scanning, and reusable workflows with concrete details. | 3 / 3 |
Workflow Clarity | The patterns are presented as standalone templates rather than as part of a guided workflow for setting up CI/CD. There are no validation checkpoints (e.g., 'test the workflow locally with act before pushing', 'verify secrets are configured'), no error recovery guidance, and the Kubernetes deployment pattern lacks a rollback step if verification fails. For destructive/deployment operations, this absence caps the score. | 2 / 3 |
Progressive Disclosure | References to asset files like 'assets/test-workflow.yml' and 'assets/deploy-workflow.yml' are mentioned but no bundle files exist, making these dead references. The content is somewhat monolithic—all patterns are inline in one long file when some could be split into referenced files. The 'Related Skills' section is a nice touch but the overall structure could better separate overview from detailed templates. | 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
34632bc
- 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.