Install and drive Google's Antigravity CLI (`agy`) as a non-interactive sub-agent. Use when orchestrating agy, running Antigravity agents from a script or sandbox, delegating a task to Google's agent harness, or wanting a Gemini-backed peer agent alongside Claude.
npx skills add https://github.com/oaustegard/claude-skills --skill invoking-antigravity
Run Google's Antigravity CLI (agy) headless, then call agy -p "<task>"
as an orchestrated sub-agent on Google's harness (Gemini 3.5 Flash).
Install, authenticate once, orchestrate. For the *why* behind any step —
the 30 s timeout, the keyring fallback, the token format, network hosts,
troubleshooting — read references/auth-internals.md.
agy as a sub-agent: shell out, capture stdout, fold back.For interactive local use, skip this — run agy directly and it opens a browser.
curl -fsSL https://antigravity.google/cli/install.sh | bash
Idempotent, ~3 s, installs ~/.local/bin/agy.
Export these in every shell that runs agy, so it stores the token in a
file rather than an OS keyring:
export SSH_CONNECTION="203.0.113.1 50000 203.0.113.2 22"
export SSH_CLIENT="203.0.113.1 50000 22"
export SSH_TTY="/dev/pts/0"
Run the broker, then relay the login to a human:
python3 scripts/agy_auth_broker.py & # spawns agy, captures the OAuth URL
sleep 15 && cat /tmp/agybroker/url # a human opens this and consents
printf '<code>' > /tmp/agybroker/code # paste the authorization code back
agy writes the token to ~/.gemini/antigravity-cli/antigravity-oauth-token;
later agy -p calls run silently. Complete the login within a few minutes —
an idle container pause kills the broker's agy process.
agy --dangerously-skip-permissions -p "<task>"
Place every flag before -p — it treats the next argument as the prompt.
Add --add-dir <path>, --print-timeout 10m, or --conversation <id> as
the task needs.
Save ~/.gemini/antigravity-cli/antigravity-oauth-token and write it back
(with the SSH vars set) — its refresh_token is durable, so no repeat
OAuth. Keep the file out of git and logs; it is a personal Google credential.
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
Replace with description of the skill and when Claude should use it.
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
This skill should be used when the user wants to "create a skill", "add a skill to plugin", "write a new skill", "improve skill description", "organize skill content", or needs guidance on skill structure, progressive disclosure, or skill development best practices for Claude Code plugins.
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
Use when creating new skills, editing existing skills, or verifying skills work before deployment
Take oaustegard/invoking-antigravity from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.