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

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/cicd-automation/skills/github-actions-templates/SKILL.md

Quality

Content

68%Weight 40%Scale 1-5

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

The content is highly actionable with complete, executable workflow templates and tight prose, but workflow clarity is capped by inconsistent validation in destructive deploy flows, and progressive disclosure is undermined by broken references to a missing assets/ directory.

Suggestions

Create the missing assets/ bundle files (test-workflow.yml, deploy-workflow.yml, matrix-build.yml) referenced in the body, or remove the 'Reference: See assets/...' lines so pointers are not broken.

Add an explicit validation/verification step to the production deploy and Docker build/push workflows (e.g., `kubectl rollout status`, image digest check, smoke test) to satisfy the destructive-operations feedback-loop requirement.

Trim the redundant Purpose and When-to-Use sections or fold them into the description, and consider moving the fully-inlined workflow YAMLs into the assets bundle with concise inline summaries to improve token efficiency and progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is dominated by lean, copy-paste YAML with only brief intros, and mostly assumes Claude's knowledge; not a 5 because the Purpose and When-to-Use sections restate the description and the 10-item best-practices list adds light padding.	4 / 5
Actionability	Seven complete, executable workflow YAML examples (test, docker build/push, k8s deploy, matrix, reusable, security scan, production deploy with approvals) are copy-paste ready and cover the common cases.	5 / 5
Workflow Clarity	Each template has a coherent internal step sequence and Pattern 3 includes a verification step (kubectl rollout status), but destructive deploy workflows lack consistent validation/feedback loops (the production deploy uses a placeholder echo with no verification), capping clarity at 3 per the destructive-operations rule.	3 / 5
Progressive Disclosure	Section structure is reasonable, but the three 'Reference: See assets/...' pointers target files in an assets/ directory that does not exist, so the references are broken; additionally most workflow YAML is fully inlined rather than split into the referenced bundle files.	2 / 5
	Total	14 / 20 Passed

Description

87%Weight 40%Scale 1-5

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 strong, third-person description that clearly states capabilities and provides an explicit 'Use when' trigger clause with natural keywords. Minor gaps in capability breadth and synonym coverage keep specificity and trigger quality just below perfect.

Dimension	Reasoning	Score
Specificity	"Create production-ready GitHub Actions workflows for automated testing, building, and deploying applications" names the domain plus several concrete actions (testing, building, deploying); not a 5 because matrix builds, security scanning, and reusable templates are only surfaced later in the 'when' clause rather than as named capabilities.	4 / 5
Completeness	Explicitly answers both what ("Create production-ready GitHub Actions workflows for automated testing, building, and deploying") and when ("Use when setting up CI/CD with GitHub Actions, automating development workflows, or creating reusable workflow templates") with concrete trigger phrases.	5 / 5
Trigger Term Quality	Natural terms users say are present ("GitHub Actions", "CI/CD", "automating development workflows", "reusable workflow templates"); falls short of 5 because common synonyms like ".github/workflows", "workflow YAML", or file extensions are absent.	4 / 5
Distinctiveness Conflict Risk	Scoped tightly to GitHub Actions with triggers like "CI/CD with GitHub Actions" and "reusable workflow templates", giving it a clear niche with minimal overlap risk against non-GitHub CI skills.	5 / 5
	Total	18 / 20 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
Path: plugins/cicd-automation/skills/github-actions-templates/SKILL.md
Commit: d6837ae

Reviewed: about 12 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.