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.

1.13x

Quality

—

Does it follow best practices?

Impact

98%

1.13x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Quality

Content

57%

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 executable templates, but it is padded with inline workflows that duplicate non-existent asset files, and the referenced bundle files are missing entirely. Deploy workflows lack validation checkpoints.

Suggestions

Move the full workflow YAMLs into the referenced asset files (assets/test-workflow.yml, deploy-workflow.yml, matrix-build.yml) and keep only concise summaries or key snippets inline in SKILL.md.

Actually create the referenced files (including references/common-workflows.md) or remove the dangling references, since progressive disclosure depends on the bundle structure being real.

Add explicit validation/verification steps to the production and Kubernetes deploy workflows (e.g., rollout status checks, smoke tests, rollback on failure) rather than placeholder echo commands.

Dimension	Reasoning	Score
Conciseness	Six complete YAML workflows are inlined in full and then also pointed to as asset files ("See assets/test-workflow.yml"), duplicating content that should live in references; mostly efficient but could be tightened.	2 / 3
Actionability	Provides complete, copy-paste-ready executable GitHub Actions YAML for each pattern with concrete actions, versions, and secrets usage.	3 / 3
Workflow Clarity	Patterns are organized by use case, but destructive/deploy workflows lack validation/feedback loops — the production deploy step is a placeholder "echo" with no verification — capping clarity at 2.	2 / 3
Progressive Disclosure	The body is a monolithic wall of inline workflow YAMLs, and its references (assets/*.yml, references/common-workflows.md) point to files that do not exist in the bundle — broken, dangling references with poor organization.	1 / 3
	Total	8 / 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.

The description is concise, third-person, and clearly states both capability and trigger conditions with natural keywords. It is well-distinguishable from other skills.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "automated testing, building, and deploying applications" — rather than vague language, matching the anchor for multiple specific concrete actions.	3 / 3
Completeness	Explicitly answers what ("Create production-ready GitHub Actions workflows for automated testing, building, and deploying") and when ("Use when setting up CI/CD with GitHub Actions..."), with an explicit Use-when trigger clause.	3 / 3
Trigger Term Quality	Natural user-facing terms appear — "GitHub Actions", "CI/CD", "automating development workflows", "reusable workflow templates" — giving good coverage of phrases a user would actually say.	3 / 3
Distinctiveness Conflict Risk	Scoped to a clear niche (GitHub Actions workflows) with distinct triggers, making it unlikely to fire for unrelated 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: 7 missing	Warning

	Total	15 / 16 Passed

Repository: Dicklesworthstone/pi_agent_rust
Commit: abece4a

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.