Github Actions Hardening

Use when reviewing, authoring, auditing, or hardening GitHub Actions workflows for trigger trust, expression injection, token permissions, action supply chain, secrets, outputs, OIDC, and runner exposure.

9 stars 3 forksGit & Code Review

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add sandbaseai/workbuddy-skill --skill github-actions-hardening
Manual install
git clone --depth 1 https://github.com/sandbaseai/workbuddy-skill.git /tmp/workbuddy-skill
mkdir -p ~/.claude/skills
cp -r /tmp/workbuddy-skill/skills/github-actions-hardening ~/.claude/skills/github-actions-hardening

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# GitHub Actions Hardening

## Purpose and boundary

Review GitHub Actions as a security-sensitive program: YAML triggers determine trust, `${{ }}`
expressions become runner input, `uses:` references execute dependency code, and permissions or
Secrets define blast radius. This workflow complements application-code scanning; it does not
prove that a workflow is safe merely because YAML parses or a linter passes.

Default to read-only inspection and a review report. Do not edit workflows, rotate credentials,
run untrusted workflow code, access cloud accounts, or apply remediations without authorization.
Never print secret values or copy private workflow logs into the report.

## Step 1: inventory and establish scope

List every `.github/workflows/*.{yml,yaml}` file, reusable workflow, local action, composite
action, environment rule, Dependabot action update, and referenced script that affects the job.
Record commit/revision, repository visibility, default token policy if observable, runner type,
deployment environments, and whether forks or external contributors can trigger execution.

For each workflow, capture trigger, jobs, `uses:`, `run:`, `with:`, `env:`, `permissions:`,
`secrets:`, checkout configuration, artifacts/caches, and deployment steps. Quote exact file and
line locations in findings. If a referenced file or repository setting cannot be inspected,
mark it unknown rather than assuming the secure or insecure state.

## Step 2: map trigger privilege
Read the full skill on GitHub

Details

Skill name
github-actions-hardening
Path
skills/github-actions-hardening/SKILL.md
License
MIT
Repo updated
8 September 2026

FAQ

What does the Github Actions Hardening skill do?

Use when reviewing, authoring, auditing, or hardening GitHub Actions workflows for trigger trust, expression injection, token permissions, action supply chain, secrets, outputs, OIDC, and runner exposure.

How do I install the Github Actions Hardening skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add sandbaseai/workbuddy-skill --skill github-actions-hardening. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Github Actions Hardening popular?

It lives in sandbaseai/workbuddy-skill, which has 9 GitHub stars and 3 forks.

Related skills

Browse the most popular Claude skills, all git & code review skills, or write your own with the skills generator.