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.

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

65%

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

The skill is highly actionable thanks to complete, executable workflow examples, but it is verbose for a catalog and its progressive disclosure is undermined by broken asset references and inline-heavy content. Workflow clarity is adequate but lacks validation feedback loops for destructive deploys.

Suggestions

Create the missing assets/ files (test-workflow.yml, deploy-workflow.yml, matrix-build.yml) or remove the dangling 'See assets/...' reference lines so navigation is not broken.

Add a validation/rollback checkpoint to the production deployment pattern (e.g., verify rollout status, abort and roll back on failure) to lift workflow clarity above 2 for a destructive operation.

Trim the redundant 'Purpose' and 'When to Use' sections (which restate the frontmatter description) and move the less-common workflows (reusable, security scan, approvals) into reference files to reduce inline length.

Dimension	Reasoning	Score
Conciseness	The body is mostly executable YAML rather than explanatory prose, but at ~320 lines with eight full inline workflows plus 'Purpose' and 'When to Use' sections that restate the frontmatter, it could be tightened; 'production-ready' framing adds mild padding.	2 / 3
Actionability	Every pattern is a complete, copy-paste-ready GitHub Actions workflow with real action versions, secrets bindings, and matrix configs — fully executable guidance rather than pseudocode.	3 / 3
Workflow Clarity	This is a pattern catalog, not a sequenced process; the production deploy step ('Deploy application', 'Notify Slack') lacks validation checkpoints or a rollback feedback loop, so per the destructive-operations rule workflow clarity is capped at 2.	2 / 3
Progressive Disclosure	Sections are organized, but the body references assets/test-workflow.yml, assets/deploy-workflow.yml, and assets/matrix-build.yml while no assets/ directory exists, so the references are broken; most workflow content also lives inline rather than split into those files.	2 / 3
	Total	9 / 12 Passed

Description

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.

A well-crafted description that concisely states concrete capabilities and provides explicit, natural-language trigger guidance in third person. It avoids fluff almost entirely, with only mild buzz in 'production-ready'.

Dimension	Reasoning	Score
Specificity	Names the domain and multiple concrete actions — 'automated testing, building, and deploying applications' — matching the anchor for listing several specific concrete actions rather than vague language.	3 / 3
Completeness	It explicitly states what it does ('Create production-ready GitHub Actions workflows...') and when to use it ('Use when setting up CI/CD with GitHub Actions...'), satisfying both halves of the completeness anchor.	3 / 3
Trigger Term Quality	'CI/CD with GitHub Actions', 'automating development workflows', and 'reusable workflow templates' are natural phrases a user would say when needing this skill, giving good keyword coverage.	3 / 3
Distinctiveness Conflict Risk	The GitHub Actions niche with GitHub-Actions-specific triggers is clearly distinguishable and unlikely to fire for unrelated skills, despite a minor overlap risk with general CI/CD pipeline skills.	3 / 3
	Total	12 / 12 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
referenced_paths_exist	Referenced path issues: 3 missing	Warning

	Total	15 / 16 Passed

Repository: wshobson/agents
Commit: 5cc2549

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.