agy

Delegate scoped code tasks to the Antigravity CLI as a headless subagent.

Updated May 10, 2026
One-click install
npx skills add https://github.com/cookkie03/skills --skill agy-cookkie03
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agy
Source: https://github.com/cookkie03/skills/tree/main/agy
Command: npx skills add https://github.com/cookkie03/skills --skill agy-cookkie03

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Delegating bounded coding work to a subagent CLI requires careful briefing, scoping, and verification; this Skill provides a disciplined workflow for running the Antigravity (agy) CLI headlessly while you stay in control of review and final judgment. ## Core Features & Use Cases - Headless Delegation: Run agy in print mode with self-contained briefs covering goal, scope, constraints, and required reports. - Workspace Scoping: Restrict agy to specific repositories with --add-dir and explicit rules against touching out-of-scope paths. - Robust Execution & Verification: Capture stdout/stderr logs separately, check exit codes, and validate results with git status and diffs. - Use Case: You need a scoped refactor across a repository. Write a brief file, pipe it to agy with the repo added as workspace, then inspect the logs and diff before reporting the outcome. ## Quick Start Ask the assistant to delegate a scoped code edit to agy by writing a brief and running it against your repository, then verify the resulting diff.

Frequently Asked Questions about agy

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run the Antigravity agy CLI as a headless subagent?

Use print mode with agy -p followed by a self-contained prompt, and scope the workspace with --add-dir pointing at your repository. The prompt must be complete because agy cannot ask follow-up questions in non-interactive mode.

What should an agy task brief include?

A brief should state the goal, target paths, constraints, allowed scope, tests to run, and the exact report format expected. Explicitly tell agy not to commit, push, delete, or touch out-of-scope paths.

How do I verify agy completed a task successfully?

Check for an acceptable exit code, non-empty output, and no CLI usage or auth errors in the logs. Then confirm with git status and diff that changes match the requested scope.

Why does agy exit immediately or produce empty output?

Immediate exits are usually caused by bad flags that prevent startup, so inspect stderr and logs first. Confirm current flag names with agy -h since CLI options change between versions.

What do I do when agy authentication fails?

Stop the run and run agy once interactively in a terminal to complete login. After authentication succeeds, retry the headless delegation with the same brief and workspace scope.

Can I run multiple agy jobs in parallel?

Yes, but only for independent chunks of work with no overlapping files. You must reconcile any overlapping edits manually after the parallel runs complete.