github-actions · wendylabsinc — Claude Code skill: CI workflow rules
A skill that steers the agent through GitHub Actions authoring: vendor actions over shell scripts, verified versions, minimal job permissions.
npx skills add wendylabsinc/claude-skills --skill github-actions -a claude-codeWhat github-actions does
The skill fires on anything inside .github/workflows/: a test job, a release pipeline, a deploy. Its first rule is to reach for an existing action rather than write shell in run:. Checkout, image build and push, artifact upload, releases are all covered by vendor actions under actions/* and docker/*. A hand-rolled step needs a stated reason in the pull request.
Versions are the part it refuses to do from memory. Before pinning, the agent runs gh api repos/actions/checkout/releases/latest --jq .tag_name for every action in the file and uses what comes back. The normal pin is a major tag. A commit SHA goes in when the job carries production credentials. If gh is not logged in, only the releases page is left to check by hand.
Access is scoped tight. Each job gets an explicit permissions: block, starting at contents: read with id-token: write added where OIDC is in play. Cloud login runs through OIDC federation. Long-lived cloud keys sitting in secrets are out. The checklist also asks for a concurrency: group on deploys and split triggers: default branch to dev, v* tags to production.
What it helps with
- write a deploy workflow in
.github/workflows/without shell workarounds - check the latest major of an action before pinning it
- trim job permissions to what the job actually uses
- move cloud auth off stored keys onto OIDC
- split deploy triggers between branch and tag
Example prompts for the agent
- Draft
.github/workflows/ci.ymlwith tests on pull requests and a release onv*tags. - Review this workflow PR: are the action versions current and the permissions minimal?
- Switch the GCP auth step to OIDC and drop
credentials_json.
How to install github-actions
1Skills CLI (Vercel)
npx skills add wendylabsinc/claude-skills --skill github-actions -a claude-code2Manually: put the files in place
~/.claude/skills/github-actions/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/github-actions/
1Skills CLI (Vercel)
npx skills add wendylabsinc/claude-skills --skill github-actions -a codex2Manually: put the files in place
.agents/skills/github-actions/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add wendylabsinc/claude-skills --skill github-actions -a cursor2Manually: put the files in place
.cursor/skills/github-actions/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install wendylabsinc/claude-skills github-actions2Manually: put the files in place
.github/skills/github-actions/SKILL.md1Skills CLI (Vercel)
npx skills add wendylabsinc/claude-skills --skill github-actions -a gemini-cli2Platform CLI
gemini skills install https://github.com/wendylabsinc/claude-skills --path github-actionsManually: put the files in place
.devin/skills/github-actions/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add wendylabsinc/claude-skills --skill github-actions -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about github-actions
How do I install the github-actions skill in Claude Code?
Run npx skills add wendylabsinc/claude-skills --skill github-actions -a claude-code. The skill lands at ~/.claude/skills/github-actions/SKILL.md.
What does the github-actions skill do?
It gives the agent a set of workflow rules: use maintained actions instead of shell, verify tags before pinning, keep permissions: minimal and authenticate to clouds through OIDC.
Why verify action versions with gh api?
The agent's idea of the current major goes stale, so it checks with gh api repos/<owner>/<repo>/releases/latest --jq .tag_name while the workflow is being written.
Similar skills
All skills for DevOps and infrastructure →github-actions by other authors comes first.