github-actions-templates
Build GitHub Actions workflows quickly
CI/CD workflows are time consuming to write and easy to misconfigure. This skill provides proven GitHub Actions templates for tests, builds, deployments, and security scans.
Download the skill ZIP
Upload in Claude
Go to Settings → Capabilities → Skills → Upload skill
Toggle on and start using
Test it
Using "github-actions-templates". Create a matrix build for Python 3.9 to 3.12 on Linux, macOS, and Windows.
Expected outcome:
- Runs on ubuntu-latest, macos-latest, and windows-latest
- Tests Python 3.9, 3.10, 3.11, and 3.12
- Installs dependencies with pip and runs pytest
- Triggers on push and pull requests
Using "github-actions-templates". Create a Docker workflow that pushes to GHCR on version tags.
Expected outcome:
- Logs in to GitHub Container Registry with GitHub_TOKEN
- Extracts metadata with Docker metadata action
- Builds and pushes with cache from GitHub Actions cache
- Tags with branch and semver patterns
Security Audit
SafeThis skill contains only static documentation with YAML workflow examples. All static findings are false positives: the scanner misinterpreted markdown code fences as backtick execution, GitHub Actions secret injection syntax as credential exposure, and YAML version pinning as weak crypto. The skill does not execute code, access files, or make network requests.
Risk Factors
🌐 Network access (2)
⚙️ External commands (25)
📁 Filesystem access (1)
🔑 Env variables (3)
Quality Score
What You Can Build
Launch a CI baseline
Start with a test and lint workflow for a new repository and keep builds reliable.
Standardize pipelines
Reuse templates for Docker builds, approvals, and reusable workflows across teams.
Add security scans
Adopt Trivy and Snyk workflow examples to catch vulnerabilities early.
Try These Prompts
Create a GitHub Actions workflow that runs npm ci, lint, and tests on pushes and pull requests using Node 20.
Provide a workflow to build and push a Docker image to GHCR with tags for branches and semver releases.
Draft a workflow that configures AWS credentials and deploys manifests from k8s/ to production.
Create a reusable workflow that accepts node-version input and uses NPM_TOKEN for private installs.
Best Practices
- Pin action versions instead of using latest
- Use secrets for tokens and credentials
- Limit workflow permissions to the minimum needed
Avoid
- Using unpinned actions from unknown sources
- Storing credentials directly in workflow files
- Deploying to production without approval gates
Frequently Asked Questions
What platforms are compatible?
What are the main limits?
How do I integrate with my repo?
Is my data safe?
What if a workflow fails?
How does this compare to writing from scratch?
Developer Details
Author
wshobsonLicense
MIT
Repository
https://github.com/wshobson/agents/tree/main/plugins/cicd-automation/skills/github-actions-templatesRef
main
File structure
📄 SKILL.md