github-actions-advanced
Design, debug, and harden GitHub Actions CI/CD workflows, including reusable workflows, matrix builds, self-hosted runners, OIDC authentication, caching, environments, secrets, and release automation.
npx skills add sickn33/agentic-awesome-skills --skill github-actions-advanced --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
What it does
Guides design, debugging, and hardening of GitHub Actions workflows, including reusable workflows, matrix builds, self-hosted runners, OIDC authentication, caching, environments, secrets, and release automation. The skill targets users who want production-grade CI/CD pipelines using GitHub Actions and related security and reliability practices.
How it works
- When to use: invoked for users dealing with GitHub Actions, workflows in .github/workflows, CI/CD pipelines, runners, or who need matrix builds, reusable workflows, composite actions, or self-hosted runners; also for questions about OIDC, caching, secrets, environments, and release automation.
- It provides concrete guidance on workflow structure, triggers, permissions, environments, and security considerations, including examples for:
- Reusable workflows with caller and reusable workflow definitions
- Matrix builds with strategy configurations and dynamic matrix generation
- Caching strategies for languages (Node, Python, Go, Java) and Docker layer caching
- OIDC authentication flows for AWS, GCP, and Azure
- Environments and deployment protections (approval gates, environment secrets)
- Secrets management and masking in workflows
- Composite actions usage and definition
- Self-hosted runners configuration and best practices
- Conditional execution and flow control across jobs and steps
- It presents concrete YAML code blocks and command examples to implement these patterns within GitHub Actions workflows.
When to use it
- User mentions GitHub Actions, .github/workflows, CI/CD pipelines, runners, jobs, steps, or actions
- User wants to automate builds, tests, deployments, or releases via GitHub
- User asks about matrix builds, reusable workflows, composite actions, or self-hosted runners
- User needs help with OIDC authentication, caching strategies, or secrets management
- User says "my GitHub pipeline is failing" or "set up CI for my repo"
- User asks about workflow security, hardening, or environment protection rules
What it can touch
- Tools declared: claude-code, codex, cursor
- The skill instructs the agent to inspect repository structure (e.g., .github/workflows, .github/actions) and detect tech stack files (package.json, requirements.txt, etc.) to tailor recommendations
- It uses concrete commands and file names exactly as shown in the examples (e.g., actions/checkout, setup-node, build-push-action, workflow_call, docker/build-push-action) to illustrate integration points
Caveats
- The skill focuses on guidance and patterns; it does not guarantee that a given workflow will pass all tests or security reviews without implementation and testing
- Security recommendations emphasize least privilege, proper use of environments, and careful handling of secrets and OIDC configurations
- Licensing noted as MIT in the skill metadata
# GitHub Actions Advanced Skill Expert guidance for designing, writing, debugging, and securing **production-grade** GitHub Actions workflows. --- ## When to Use This Skill - User mentions GitHub Actions, `.github/workflows`, CI/CD pipelines, runners, jobs, steps, or actions - User wants to automate builds, tests, deployments, or releases via GitHub - User asks about matrix builds, reusable workflows, composite actions, or self-hosted runners - User needs help with OIDC authentication, caching strategies, or secrets management - User says "my GitHub pipeline is failing" or "set up CI for my repo" - User asks about workflow security, hardening, or environment protection rules ## When NOT to Use This Skill - The user is working with GitLab CI/CD → recommend `gitlab-ci-patterns` - The user is working with CircleCI, Jenkins, or other CI platforms - The task is purely about Docker image building without GitHub context → recommend `docker-expert` - The task is about Kubernetes deployment configuration → recommend `kubernetes-architect` --- ## Step 1: Understand Context Before Responding When invoked, first gather context: ```bash # Discover existing workflows in the repo find .github/wor
- When to Use This Skill
- When NOT to Use This Skill
- Step 1: Understand Context Before Responding
- Workflow Structure Reference
- Triggers (on:)
- Common Patterns
- Reusable Workflows
- Caller (.github/workflows/deploy.yml)
- Reusable Workflow (.github/workflows/build.yml)
- Matrix Builds
- Dynamic Matrix via Script
- Caching Strategies
- Language Setup Actions (Preferred — No Extra Step Needed)
- Manual Cache (Any Tool)
Discover existing workflows in the repo find .github/workflows -name "*.yml" -o -name "*.yaml" 2>/dev/null | head -20 Check for composite actions find .github/actions -name "action.yml" 2>/dev/null Detect tech stack (influences runner OS, language setup actions) ls package.json requirements.txt Gemfile go.mod Cargo.toml pom.xml 2>/dev/null Actions Runner Controller (Kubernetes) — recommended for ephemeral runners helm install arc \
What does the github-actions-advanced skill do?
Design, debug, and harden GitHub Actions CI/CD workflows, including reusable workflows, matrix builds, self-hosted runners, OIDC authentication, caching, environments, secrets, and release automation.
How do I install it?
Run `npx skills add sickn33/agentic-awesome-skills --skill github-actions-advanced --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From sickn33/agentic-awesome-skills, a repository with 44,414 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.