validate-github-actions
Skill7 starsChanged 2 months agoMITView on GitHub
Use when auditing or validating GitHub Actions workflows for syntax, action pinning, least-privilege permissions, fork safety, caching, artifacts, matrices, and CI security. Defaults to read-only analysis; mutations require explicit confirmation.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- jorgeazevedo/skillstheir own version, first seen Oct 1, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- jorgeazevedo/skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository29 other files it gives its agents.
- AGENTS.mdAGENTS.md
- address-pr-commentsSkill
- build-and-scan-container-imageSkill
- execute-database-migrationSkill
- generate-adrSkill
- generate-service-documentationSkill
- get-pr-commentsSkill
- incident-triageSkill
- install-dev-toolsSkill
- prepare-releaseSkill
- remediate-dependency-vulnerabilitiesSkill
- review-configurationSkill
- twg-agentic-searchSkill
- twg-artifactsSkill
- twg-code-reviewSkill
- twg-confluenceSkill
- twg-context-discoverySkill
- twg-engineering-workSkill
- twg-jira-resolve-merged-workSkill
- twg-jiraSkill
- twg-operational-healthSkill
- twg-responsibility-routingSkill
- twgSkill
- twg-space-creationSkill
- twg-status-rollupsSkill
- validate-and-deploy-iacSkill
- validate-and-deploy-kubernetesSkill
- validate-documentationSkill
- verify-service-healthSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 5 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 26
Check action references for immutable SHAs and readable version comments.
- Very specific: line 29
When fixUnpinned is true, propose pinning changes.
- Distinctive: line 35
Never execute a workflow as part of static validation.
- Distinctive: line 36
Do not expose secrets from workflow files or logs.
- Distinctive: line 37
Treat fork workflows as untrusted.
- Distinctive: line 38
Do not rewrite action references without recording the resolved version.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Validate GitHub Actions
Audit workflow files against githubactions.md, security.md, and repository
conventions.
Parameters
workflowPath: workflow directory or file; default.github/workflows.mode:syntax,security,best-practices, orfull; defaultfull.requireSHA: defaulttrue.auditPermissions: defaulttrue.checkForks,checkMatrices,checkCaching,checkArtifacts: defaulttrue.fixUnpinned: defaultfalse.format:summary,json, orsarif; defaultsummary.
Workflow
- Discover YAML workflow files and parse them without executing workflows.
- Validate triggers, jobs, matrices, expressions, permissions, and dependencies.
- Check action references for immutable SHAs and readable version comments.
- Audit token permissions, fork behavior, secret exposure, concurrency, timeouts, caching, artifacts, environments, and deployment gates.
- When
fixUnpinnedis true, propose pinning changes. Apply them only after explicit confirmation and record each resolved action SHA. - Re-run validation and return findings by severity.
Safety
- Never execute a workflow as part of static validation.
- Do not expose secrets from workflow files or logs.
- Treat fork workflows as untrusted.
- Do not rewrite action references without recording the resolved version.
Output
Return files checked, syntax status, security findings, best-practice findings, changes applied, unresolved risks, and CI recommendations.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.