gh-actions-validator
Use when validating GitHub Actions workflows for Google Cloud and Vertex AI deployments. Trigger with phrases like "validate github actions", "setup workload identity federation", "github actions security", "deploy agent with ci/cd", or "automate vertex ai deployment". Enforces Workload Identity Federation (WIF), validates OIDC permissions, ensures least privilege IAM, and implements security best practices.
When & Why to Use This Skill
This Claude skill automates the validation and hardening of GitHub Actions workflows specifically for Google Cloud and Vertex AI deployments. It enhances security by enforcing Workload Identity Federation (WIF) and OIDC authentication, ensuring least-privilege IAM roles and eliminating the risks associated with long-lived service account keys.
Use Cases
- 1. Security Auditing: Scan existing .github/workflows/ directories to identify insecure practices and replace hardcoded JSON service account keys with secure OIDC-based authentication.
- 2. Secure Vertex AI Deployment: Automate the setup and validation of CI/CD pipelines for deploying AI agents and models to Vertex AI, ensuring all deployment steps follow Google Cloud security best practices.
- 3. IAM Policy Enforcement: Validate and implement least-privilege IAM permissions for GitHub Actions, preventing 'Owner' or 'Editor' role over-permissioning and reducing the attack surface of cloud environments.
| name | gh-actions-validator |
|---|---|
| description | | |
| allowed-tools | Read, Write, Edit, Grep, Glob, Bash(git:*), Bash(gcloud:*) |
| version | 1.0.0 |
| author | Jeremy Longshore <jeremy@intentsolutions.io> |
| license | MIT |
Gh Actions Validator
Overview
Validate and harden GitHub Actions workflows that deploy to Google Cloud (especially Vertex AI) using Workload Identity Federation (OIDC) instead of long-lived service account keys. Use this to audit existing workflows, propose a secure replacement, and add CI checks that prevent common credential and permission mistakes.
Prerequisites
Before using this skill, ensure:
- GitHub repository with Actions enabled
- Google Cloud project with billing enabled
- gcloud CLI authenticated with admin permissions
- Understanding of Workload Identity Federation concepts
- GitHub repository secrets configured
- Appropriate IAM roles for CI/CD automation
Instructions
- Audit Existing Workflows: Scan .github/workflows/ for security issues
- Validate WIF Usage: Ensure no JSON service account keys are used
- Check OIDC Permissions: Verify id-token: write is present
- Review IAM Roles: Confirm least privilege (no owner/editor roles)
- Add Security Scans: Include secret detection and vulnerability scanning
- Validate Deployments: Add post-deployment health checks
- Configure Monitoring: Set up alerts for deployment failures
- Document WIF Setup: Provide one-time WIF configuration commands
Output
- uses: actions/checkout@v4
- name: Authenticate to GCP (WIF)
- name: Deploy to Vertex AI
--project=${{ secrets.GCP_PROJECT_ID }} \
--region=us-central1
- name: Validate Deployment
Error Handling
See {baseDir}/references/errors.md for comprehensive error handling.
Examples
See {baseDir}/references/examples.md for detailed examples.
Resources
- Workload Identity Federation: https://cloud.google.com/iam/docs/workload-identity-federation
- GitHub OIDC: https://docs.github.com/en/actions/deployment/security-hardening-your-deployments
- Vertex AI Agent Engine: https://cloud.google.com/vertex-ai/docs/agent-engine
- google-github-actions/auth: https://github.com/google-github-actions/auth
- WIF setup guide in {baseDir}/docs/wif-setup.md