antigravity-agents

Solid

Delegate coding, code review, analysis, and research jobs to Google Antigravity CLI (agy) sub-agents that run alongside your own work. Use this whenever the user asks to spin off, offload, or delegate a task to Antigravity, agy, Gemini, or an "external agent"; wants a second opinion or independent review from a different model; wants intensive repo work (audits, large refactors, research sweeps) run in the background while you keep working; or says things like "have Antigravity do it", "spin up a sub-agent for this", or "get more done in parallel". Also use it proactively when a task is a good fit for parallel delegation and the user has expressed a preference for using Antigravity workers.

AI & Automation 107 stars 31 forks Updated today MIT

Install

View on GitHub

Quality Score: 86/100

Stars 20%
68
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# Antigravity CLI Sub-Agents Google Antigravity CLI (`agy`) is an autonomous terminal coding agent (Gemini and other models) that can read a repo, edit files, and run commands. This skill uses its non-interactive print mode to run **delegated jobs**: you write a self-contained task prompt, launch `agy -p` in the background, keep doing your own work, then collect and verify the result. Treat an agy job like a contractor you briefed over email: it only knows what's in the prompt and the directory you point it at, and its work is unverified until you check it. ## Resolving the binary After install, `agy` is normally on your `PATH`. If a tool-spawned shell can't find it (some shells don't inherit a freshly updated PATH), fall back to the full path: - **Windows:** `%LOCALAPPDATA%\agy\bin\agy.exe` (in Bash-style shells: `"$LOCALAPPDATA/agy/bin/agy.exe"`) - **macOS / Linux:** check `which agy` **Critical: always close stdin.** `agy` blocks forever (0% CPU, no output, even in print mode) when stdin is an open pipe, which is exactly what non-interactive tool shells give it. Launch jobs with `</dev/null` appended (POSIX shells), or from PowerShell via `cmd /c '... < NUL'`. A "stalled" job with an empty log almost always means stdin was left open — kill it and relaunch with stdin closed. ## Preflight (once per session) Before the first job of a session, verify auth with a cheap probe: ```bash agy -p "Reply with exactly: OK" --print-timeout 60s </dev/null ``` - Replies `OK` → a...

Details

Author
markfulton
Repository
markfulton/claude-antigravity-agents
Created
3 weeks ago
Last Updated
today
Language
N/A
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category