Local Action Verification

Sets up act so you can run GitHub Actions workflows locally before pushing, which is exactly what you want if you're tired of using CI as your debugger. Drops two scripts into your repo (one to install act, one to run it without timing out) and adds instructions to AGENTS.md so Claude knows how to verify changes pass CI. The run script polls logs in the background instead of blocking, which matters for agent workflows. You'll need Docker running, and first pulls are slow (2GB+ images), but after that you get real CI feedback in minutes instead of waiting for remote runners. Honest take: this should probably be standard setup for any repo with non-trivial CI.

skills.sh installs: 699
GitHub stars: 103
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add google-labs-code/jules-skills --skill local-action-verification --agent claude-code

Installs into .claude/skills of the current project.

Files

Local Action Verification with act

You are setting up a repository so that Jules (or any agent) can run GitHub Actions workflows locally using act to verify code changes pass CI before pushing.

What You're Setting Up

Two scripts and an agents.md section that enable local CI verification:

install-act.sh — Installs act if missing (platform-aware, sudo fallback)
run-act.sh — Runs act in the background with log polling to avoid agent timeouts
AGENTS.md section — Instructions Jules reads to know how to use these scripts

Setup Steps

Step 1: Copy scripts to the repository

Copy the scripts/ directory from this skill into the target repository at scripts/act/:

Target structure:
scripts/act/
├── install-act.sh
└── run-act.sh

Make sure the scripts are executable:

chmod +x scripts/act/install-act.sh scripts/act/run-act.sh

Step 2: Add instructions to AGENTS.md

Append the following section to the repository's AGENTS.md file (create it if it doesn't exist). This is how Jules discovers the local verification capability: