Claude Skill MartBrowse skillsQuick linesLearn by videoTerminal guideWhat is a Skill?
← Back to list

agy-worker (Antigravity Delegation Worker)

Delegates repository exploration or implementation to the Google Antigravity CLI (agy), then reviews, verifies, repairs and delivers the result under strict approval bindings.

Dev & CodingAdvanced★ 433⑂ 46AI score 8/10Last updated: Oct 10, 2026

What it does

  • Defines how Claude Code or Codex hands heavy repository work to an external provider (agy) instead of doing it directly.
  • Offers three workflows — explore, task, project — with cycle budgets, and enforces the sequence workflow.sh run --preview → approval → run → status → verify-finalize.
  • Bounds what the provider can read/write via a JSON provider-scope file and binds the human approval to a launch_approval_sha256 digest.
  • Treats worker envelopes as non-evidence: the driver must run its own build/test/lint in an isolated copy and report verified, partially_verified, rejected or blocked.
  • Spells out hard stops: secrets in approved inputs, writes escaping the worktree or entering .git, and unapproved Git, install or publication actions.

Who it's for

  • Developers already using (or evaluating) the Google Antigravity CLI (agy).
  • Teams that want to offload coding work to an external agent while tightly controlling data exposure.
  • Senior engineers running large refactors or project-wide audits that need layered approvals.

Examples

  1. Understanding an unfamiliar monorepo: run the explore workflow, then spot-check the findings and state coverage limits.
  2. Adding tests: write a scope file allowing read of src/parser.py and writes under tests, approve with --approve-transmission-sha, then run the resulting tests in a separate verification copy.
  3. Project-wide audit-and-fix: use the project workflow (up to 5 cycles), request repairs in the same worker conversation on failure, and close out with verify-finalize.

· · · Install guide · · ·

Try it now, no install

Paste this into Claude to use the skill without installing anything.

Read the instructions in this file and follow them to help me:
https://raw.githubusercontent.com/aiskillstore/marketplace/HEAD/pending/cagdasyurekli/agy-worker/SKILL.md

What I want: (describe your task here)

If Claude can't open the link, open it yourself and paste the contents instead.

↓ If it works for you, download the ZIP below and install it. Then it runs on its own — no pasting each time.

Install in the Claude app (no terminal)
  1. Download the ZIP with the button below.
  2. In Claude, open Settings → Capabilities and turn on 'Code execution and file creation'. (one time)
  3. Go to Customize → Skills → + → 'Upload a skill' and upload the ZIP.
↓ Download ZIP
Install in Claude Code

Let Claude do it — paste this into Claude Code

Install the skill I found on Claude Skill Mart.
Copy the pending/cagdasyurekli/agy-worker folder from the GitHub repo aiskillstore/marketplace into my ~/.claude/skills/agy-worker/.
When it's done, tell me in one line what this skill can do.

Install with a command instead

git clone https://github.com/aiskillstore/marketplace.git /tmp/marketplace && mkdir -p ~/.claude/skills/agy-worker && cp -r /tmp/marketplace/pending/cagdasyurekli/agy-worker/* ~/.claude/skills/agy-worker/

⚠ This is a third-party skill. Check the source repository before installing.

  1. Open a terminal and change into a scratch directory.
  2. Clone the repo: git clone https://github.com/aiskillstore/marketplace.git
  3. Create the skill folder: mkdir -p ~/.claude/skills/agy-worker
  4. Copy the files: cp -r marketplace/pending/cagdasyurekli/agy-worker/* ~/.claude/skills/agy-worker/
  5. Install prerequisites: Bash, Python 3, git, and the agy CLI with provider network access.
  6. Restart Claude Code and ask something like "use the agy-worker skill to delegate exploration of this repo".
  7. Before the first live run, resolve the package with scripts/resolve-pipeline.sh and check readiness via doctor.sh --repo /absolute/path.
  8. Always run --preview first to review the approval hash, and keep the scope file outside the target repo with mode 0600.