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

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

80%Weight 40%Scale 1-3

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 and token-efficient, built from complete executable workflow templates with minimal padding. Its weak points are workflow clarity — risky deploy patterns lack explicit validation feedback loops — and progressive disclosure, since everything lives inline with no reference files.

Suggestions

Add explicit validate→fix→retry feedback loops to the destructive/batch deploy patterns (e.g., after kubectl rollout status, branch on failure to rollback or re-apply before proceeding).

Split the larger pattern blocks (e.g., Kubernetes deploy, security scanning) into reference files under ./references/ and link to them from a concise overview, so SKILL.md acts as a navigable index.

Replace the generic Instructions/Purpose boilerplate with skill-specific guidance (e.g., which pattern to pick based on target environment) or remove it to tighten the body further.

Dimension	Reasoning	Score
Conciseness	The body is almost entirely executable YAML patterns with minimal prose and no explanation of concepts Claude already knows; the small Instructions/Purpose boilerplate is minor enough that the bulk stays lean and token-efficient, fitting the top anchor better than the padded anchor at 2.	3 / 3
Actionability	Provides complete, copy-paste-ready GitHub Actions workflow YAML across test, build/push, k8s deploy, matrix, reusable, security, and approval patterns, matching the fully-executable anchor.	3 / 3
Workflow Clarity	Patterns include some checkpoints (kubectl rollout status, a verify step) but the production-deploy pattern has no validation step and none of the destructive/batch deploy patterns include an explicit validate→fix→retry feedback loop, which caps clarity at 2 per the destructive-operations guideline.	2 / 3
Progressive Disclosure	No bundle files exist and the >50-line body keeps all workflow patterns inline in a single monolithic SKILL.md despite clear section headings; content that could be split into reference files is inline, matching the structured-but-inline anchor at 2 rather than the well-signaled external-reference anchor at 3.	2 / 3
	Total	10 / 12 Passed

Description

100%Weight 40%Scale 1-3

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 is strong: it states concrete capabilities, provides explicit 'Use when' triggers with natural vocabulary, and is clearly scoped to GitHub Actions CI/CD. It uses third-person voice and avoids vague fluff.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'automated testing, building, and deploying applications' — matching the multiple-specific-actions anchor rather than the single-domain anchor at 2.	3 / 3
Completeness	Explicitly answers both 'what' ('Create production-ready GitHub Actions workflows...') and 'when' ('Use when setting up CI/CD with GitHub Actions...') with an explicit trigger clause, satisfying the top anchor.	3 / 3
Trigger Term Quality	Includes natural terms users would say — 'CI/CD with GitHub Actions', 'automating development workflows', 'reusable workflow templates' — giving good coverage rather than the partial set at 2.	3 / 3
Distinctiveness Conflict Risk	GitHub Actions is a clear, narrow niche with distinct triggers unlikely to fire for unrelated skills, matching the clear-niche anchor.	3 / 3
	Total	12 / 12 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: rmyndharis/antigravity-skills
Path: skills/github-actions-templates/SKILL.md
Commit: e63f7dd

Reviewed: 13 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.