How to use the Antigravity Delegate agent skill (agy-delegate)

What is an agent skill, and what does agy-delegate do?

An agent skill is a folder of instructions and files that an AI agent loads when a task matches it. This one is named agy-delegate and is written for an orchestrator agent, meaning the agent you are talking to. The orchestrator writes a detailed brief for one coding task, sends it to Antigravity (agy) to make the edits, then re-runs the project's tests, reads the diff, and commits only if the work holds up.

The orchestrator keeps responsibility for judgment and the final commit. Antigravity does the typing in its own conversation and has no access to your chat history, so everything it needs must be in the brief.

• The orchestrator writes the brief and reviews the result.
• Antigravity makes the code changes in the working tree.
• The orchestrator re-runs the gates, reads the diff, and commits.

Install the agy-delegate skill

Download the ZIP from the skill's page and unzip it. Then place the folder in one of two locations: your personal skills directory at ~/.claude/skills/, or a project-specific .claude/skills/ folder inside the repository you are working in.

You can also upload the skill in the Claude apps under Settings → Capabilities → Skills.

• Personal install: unzip into ~/.claude/skills/
• Project install: unzip into .claude/skills/ in the project root
• Claude apps: Settings → Capabilities → Skills, then upload the skill

Set up the prerequisites

The skill needs the Google Antigravity CLI (agy), installed and authenticated, plus Node.js and git. The shell examples assume bash or zsh; on Windows, use Git Bash or WSL.

The source suggests two checks to run once. First, agy help should succeed. Second, agy models should succeed, which shows the CLI can authenticate and list model labels. Neither check proves that a headless write will be approved.

• Antigravity CLI (agy), installed and authenticated
• Node.js
• git
• A bash or zsh shell (Git Bash or WSL on Windows)
• The upstream relay.mjs helper, obtained separately

Important: the dispatch helper is not in this bundle

This skill is docs-only in this catalog. The scripts/relay.mjs helper that performs the dispatch is absent. You need to obtain a separately authorized upstream checkout and inspect its runtime, dependencies and license before running it. Do not run the dispatch commands from this directory or invent their output.

The flags and result format described in the skill come from the upstream contract and are not tested in this bundle.

Trigger the skill with natural requests

The skill is meant to run only when you explicitly ask for delegation to Antigravity. The description says it is used only when the user requests it. Phrase your request so it names Antigravity or agy, and say what the bounded task is.

Examples of requests that match the purpose of the skill include asking the agent to have Antigravity implement a specific, well-scoped change, or asking for a removal split across layers to be delegated.

• "Delegate this rename of the config loader to Antigravity, then review the diff before committing."
• "Have agy implement the pagination fix in the API handler; run the tests and commit only if they pass."
• "Use Antigravity for this refactor sweep, one task at a time."

Run the review-then-commit loop

The skill describes five steps per task. Writing the brief and reviewing the result are judgment steps for the orchestrator. Dispatch and waiting are mechanical. The orchestrator should check the touched files against the brief, re-run the project's gates, and avoid trusting the implementer's self-report.

Check existing tests first. Loosened assertions, added skips, or deleted tests can make a passing gate meaningless. Commit only verified work, one commit per task.

• Write the brief: goal, current state, changes, what to leave alone, real gate commands, and a report contract. Tell Antigravity not to commit.
• Dispatch the brief through the reviewed helper.
• Wait for result.json and the process to exit.
• Review: re-run gates, read the diff, check tests first.
• Land: commit yourself, or send a delta brief with --resume-last.

Safety notes: scripts, network and data

This skill runs scripts and uses the network. Briefs, workspace paths and related context are sent to an external provider and are kept in process arguments and logs. Do not include secrets in a brief, and confirm you are allowed to share the code before dispatch.

Antigravity owns its permission policy. The helper does not pass --dangerously-skip-permissions by default. That flag auto-approves all tool permission requests, so use it only if you explicitly accept that. --sandbox should not be treated as an enforced boundary when combined with that flag. --read-only runs in plan mode and cannot be combined with the skip-permissions flag.

• Do not use it on sensitive or confidential repositories.
• Do not put secrets in briefs.
• Avoid --dangerously-skip-permissions unless you accept auto-approval of tool requests.
• Treat a run with the skip-permissions flag as full access.