github-actions-templates skill (wshobson) for Claude: CI/CD workflows

Gives your agent GitHub Actions patterns for tests, Docker builds, Kubernetes deploys and security scans. For developers setting up CI/CD.

Installs: 17.8K; on skills.sh
Stars: 42.1K; on GitHub
Updated: Oct 2026; last repo commit

github-actions-templates makes your agent write GitHub Actions workflow files from ready-made patterns. It has templates for a test matrix, building and pushing a Docker image, deploying to Kubernetes on AWS, a multi-OS and multi-version build, reusable workflows, security scanning and a tag-triggered production deploy that uses a GitHub environment.

It loads when you ask for CI/CD with GitHub Actions. Several templates use repository secrets, such as AWS keys, an NPM token, a Snyk token and a Slack webhook, so the workflows it writes act on your cloud and registry accounts when they run.

Good for

Developers setting up CI for a new repository
Teams deploying containers to Kubernetes from GitHub
Anyone adding security scanning or production approvals to a pipeline

Install github-actions-templates

Claude Code

Copy this prompt.

Install the github-actions-templates skill in Claude Code. Run this command:

npx skills add https://github.com/wshobson/agents --skill github-actions-templates

Then check that it loaded and tell me how to use it.

2
Paste it into Claude Code. It shows the change and asks before running it.

Requires Node.js.

From its listing on skills.sh. Source.

What's in the skill

When it loads

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.

Sections in SKILL.md

Purpose
When to Use
Common Workflow Patterns
Pattern 1: Test Workflow
Pattern 2: Build and Push Docker Image
Pattern 3: Deploy to Kubernetes
Pattern 4: Matrix Build
Workflow Best Practices
Reusable Workflows
Security Scanning
Deployment with Approvals
Related Skills

Key facts

Author: wshobson
License: MIT
Installs on skills.sh: 17,813 (Nov 2, 2026)
GitHub stars: 42,081 for the whole repo (Nov 2, 2026)
Last commit: Oct 30, 2026
Files: 1 file including SKILL.md
Bundles: No scripts or reference files
Related skills it names: gitlab-ci-patterns, deployment-pipeline-design, secrets-management

What it includes

Node matrix, lint, tests, coverage upload
Runs on push and pull request across Node 18.x and 20.x, then uploads coverage to Codecov.
Try: “Create a GitHub Actions workflow that tests my Node app on 18 and 20.”
Write · Pattern 1: test workflow
Build an image and push to ghcr.io
Runs on pushes to main and version tags. Logs in with the repository token, builds with cache, and pushes to ghcr.io with tag rules for branches, pull requests and semver releases.
Write · Pattern 2: Docker build and push
Deploy to EKS with AWS credentials
Configures AWS credentials from secrets, updates the kubeconfig, applies k8s manifests and checks the rollout.
Write · Pattern 3: Kubernetes deploy
Test on three operating systems and four Python versions
Builds across ubuntu, macOS and Windows with Python 3.9 to 3.12.
Write · Pattern 4: matrix build
A workflow other workflows can call
A workflow_call example with a Node version input and an NPM token secret.
Write · Reusable workflows
Trivy and Snyk scans
Runs Trivy on the repo, uploads results to GitHub Security, and runs a Snyk scan with a token.
Write · Security scanning
Tag-triggered deploy using a production environment
Runs on version tags with environment: production. Approval rules are set in GitHub, not by the file. The deploy step is a placeholder echo, and a Slack message is sent on success.
Write · Production deploy with an environment
Ten rules to follow
Pin action versions, cache dependencies, use secrets, set permissions, use reusable workflows and add approval gates.
Best practices

From the official docs

Permissions

Medium risk

What it can do

Read your data
Create and change things
Delete things
Read-only mode

Watch out for

Workflows it writes can deploy and use your secrets
The Kubernetes template runs kubectl apply on every push to main with AWS credentials from secrets, and the example has no approval step. Others use NPM, Snyk and Slack secrets. Review each file and limit secret scope before merging. github.com
It adds files under .github/workflows
Workflow files start running as soon as they are pushed. Commit them on a branch and check the first run. github.com

Technical details

Talks to	Docker registry, AWS, Codecov, Snyk, Slack, per the templates
Sign-in and keys	The templates read secrets from GitHub repository settings.
Scopes	Repository secrets used by the workflows (AWS, NPM, Snyk, Slack)

Questions

What does the github-actions-templates skill do?

It gives your agent ready workflow patterns for GitHub Actions: testing, Docker images, Kubernetes deploys, matrix builds, reusable workflows, security scans and a tag-triggered release that uses a production environment.

How do I install it in Claude Code, the Claude app or Codex?

Use the install box above. The wshobson/agents README documents installing a single skill with npx skills add or gh skill, and lists Claude Code and Codex plugin routes. The cicd-automation plugin also carries 5 agents, a workflow-automate command and 3 other skills. The README does not document a Claude app upload.

Does it need an API key?

The skill needs none to install. The workflows it writes can reference secrets such as AWS keys, NPM_TOKEN, SNYK_TOKEN and a Slack webhook that you add in your repository settings.

Is it safe to install?

It is one instruction file with no scripts. The risk is the workflows it writes, which run in CI with your secrets and can deploy to your cluster. Review each workflow before committing it and scope secrets to the minimum.

Does it work with GitLab CI?

Not directly. It is about GitHub Actions. It names gitlab-ci-patterns as a related skill for GitLab, and also names deployment-pipeline-design and secrets-management.

Does the Kubernetes template deploy to production?

The example runs on every push to main, with no approval step, and applies manifests to a cluster named production-cluster and the production namespace in us-west-2. Change those names, add an environment with required reviewers, and test on a non-production cluster first.

Information

updated Nov 2, 2026

Repository: wshobson/agents
Folder: plugins/cicd-automation/skills/github-actions-templates

wshobson/agents skills.sh

Sources

Docs, issue trackers and discussions this page is built from.

Show all 2

github-actions-templates SKILL.md · github.com
wshobson/agents README · github.com