agy-delegate

Featured

Delegate a coding task to the Google Antigravity CLI (`agy`) as a background implementer, then review its diff and land it yourself. Use this whenever the user wants to hand implementation work to Antigravity or agy - phrasings like "have Antigravity do X", "delegate this to agy", "run it through agy", or "use Antigravity to implement/fix/refactor" - or wants to run a queue of coding tasks through agy while staying the reviewer. DO NOT USE for tasks small enough to do inline, or when the user wants the code written directly without delegating.

Code & Development 1,207 stars 113 forks Updated today MIT

Install

View on GitHub

Quality Score: 99/100

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

Skill Content

# Antigravity Delegate You are the **orchestrator**. This skill lets you hand a bounded coding task to a separate **implementer** - the Google Antigravity CLI (`agy`) - then review what it produced and land it yourself. You write the brief and own the judgment; Antigravity does the typing in its own conversation; you verify and commit. Nothing here is specific to one orchestrating agent. The loop needs only the ability to run a shell command and read a file, so any comparable agent can drive it. It is designed for and run on Claude Code; treat other orchestrators as designed-for, not yet proven. ## When NOT to use this - The task is small enough to just do inline - delegation overhead is not worth it. - The `agy` CLI is not installed or not authenticated. Install it from Antigravity's CLI docs and run the first-launch setup. - You want to write the code yourself, or you only need a review without edits. This relay does not expose a proven CLI-enforced read-only mode yet. ## Prerequisites (check once) 1. `agy help` succeeds. If not, install the Antigravity CLI and complete first-launch setup. 2. `agy models` succeeds. That proves the CLI can authenticate and list the available model labels. 3. You are in (or will point `--cd` at) the target git repository. ## Choose the implementer model `agy` has a configured default model, so `--model` is optional. Use it when the human has a preferred Antigravity model label for the task. Otherwise let Antigravity use its own cu...

Details

Author
amElnagdy
Repository
amElnagdy/delegate-skills
Created
2 months ago
Last Updated
today
Language
JavaScript
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Solid

antigravity-agents

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.

114 Updated 3 weeks ago
markfulton
Code & Development Listed

agy-implement

Delegate an implementation task to a headless Antigravity (`agy`) session in write mode, inside an isolated git worktree, then verify the result with a cross-family review pass before it merges. Use when the user wants a second model family's implementation attempt, wants to offload a well-scoped coding task, or explicitly asks to let agy implement something.

0 Updated today
aarontzeng
AI & Automation Listed

agy-agents

Use when setting up or adopting a repository where Claude plans and the Antigravity CLI (`agy`, Gemini) implements; when the user asks to delegate implementation to Gemini or Antigravity; when installing or authenticating `agy` itself; when an `agy` run reports SUCCESS but nothing changed, hangs without ever finishing, hits RESOURCE_EXHAUSTED or a rate limit, or writes outside its scope; or when a fence, tripwire, or gate check fails in a repo using this harness.

0 Updated yesterday
DIGX