Name: github-actions-templates
Rating: 56.8 (1 reviews)
Author: administrakt0r

Blog Docs Log in Get started

github-actions-templates

Production-ready GitHub Actions workflow patterns for testing, building, and deploying applications.

Quality

65%

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/AI-Agents-Safe-Coding-Skills/skills/github-actions-templates/SKILL.md

The canonical home for this skill is github-actions-templates in administrakt0r/AI-Agents-Safe-Coding-Skills

Quality

Content

65%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 body is highly actionable — full copy-paste-ready GitHub Actions workflows across the common cases — but it is padded with generic boilerplate, lacks concrete validation/feedback loops for destructive deploys, and references bundle files that are not present.

Suggestions

Remove the generic boilerplate sections ('Do not use this skill when', 'Instructions', 'Purpose') that restate the obvious; keep only domain-specific guidance.

Add explicit validation/verification checkpoints to the production and Kubernetes deploy patterns (e.g. 'Verify rollout: kubectl rollout status ...; if failed, rollback'), since these are destructive/batch operations.

Resolve the progressive-disclosure mismatch: either create the referenced bundle files (assets/*.yml, references/common-workflows.md, resources/implementation-playbook.md) and move the inlined workflows there, or remove the broken 'Reference:' and 'Reference Files' pointers.

Dimension	Reasoning	Score
Conciseness	The core YAML workflows are concrete and not over-explained, but generic boilerplate sections ('Do not use this skill when', 'Instructions', 'Purpose') add padding that Claude does not need, beyond minor trimmable instances.	3 / 5
Actionability	Provides multiple fully executable, copy-paste-ready workflow files (test, Docker build/push, Kubernetes deploy, matrix, security scan, reusable, approval-gated deploy) covering the common cases with complete concrete code.	5 / 5
Workflow Clarity	The skill-level 'Instructions' are generic ('Clarify goals... validate outcomes') with no concrete sequencing or feedback loops, and production/destructive deploy patterns lack consistent validation checkpoints, which caps workflow clarity at 3.	3 / 5
Progressive Disclosure	Section headers and named patterns give reasonable structure, but full workflows are inlined while also being 'referenced' to bundle files (assets/*.yml, references/common-workflows.md, resources/implementation-playbook.md) that do not exist on disk, so references are unresolved and content is duplicated rather than split.	3 / 5
	Total	14 / 20 Passed

Description

66%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.

The description clearly states what the skill provides and is well-targeted to a distinct niche, but it omits any explicit 'Use when...' trigger guidance, which limits its discoverability and caps completeness at 3.

Suggestions

Add an explicit 'Use when...' clause naming concrete trigger phrases (e.g. 'Use when setting up GitHub Actions, CI/CD pipelines, or continuous integration workflows').

Include common synonyms users actually say — 'CI/CD', 'continuous integration', 'deployment pipeline' — to broaden trigger-term coverage.

Optionally name file extensions or specific artifacts (e.g. '.github/workflows/*.yml') to reach comprehensive trigger coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ('GitHub Actions workflow patterns') and lists several concrete action areas ('testing, building, and deploying'), though the actions are broad categories rather than granular tasks, leaving minor coverage gaps versus a 5.	4 / 5
Completeness	Provides a clear 'what' but no explicit 'when' — there is no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines.	3 / 5
Trigger Term Quality	Includes natural terms a user would say ('GitHub Actions', 'workflow', 'testing', 'building', 'deploying'), but misses common synonyms like 'CI/CD', 'continuous integration', and 'pipeline', so it is not comprehensive.	4 / 5
Distinctiveness Conflict Risk	'GitHub Actions' is a clear, specific niche with low conflict risk, but related CI skills (e.g. GitLab CI, general deployment pipelines) create minor overlap, keeping it just below 5.	4 / 5
	Total	15 / 20 Passed

Validation

87%

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

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
referenced_paths_exist	Referenced path issues: 7 missing	Warning

	Total	14 / 16 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills/skills/github-actions-templates/SKILL.md
Commit: 57c135b

Reviewed: 4 days 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.