askagy

Ask Agy

Overview

agy is the Antigravity CLI — a separate agent process on this machine, reachable non-interactively. It is a cold-start agent: it cannot see this conversation, the files you have open, or anything you already know. Its answer is only as good as the context you hand it in a single string.

Core principle: the prompt is the entire interface. Build it deliberately, then relay the reply as agy's, not your own.

Step 0 — Find agy, or stop

Resolve the binary before doing anything else. First hit wins:

AGY="$(command -v agy 2>/dev/null)"
[ -z "$AGY" ] && [ -x "$HOME/AppData/Local/agy/bin/agy.exe" ] && AGY="$HOME/AppData/Local/agy/bin/agy.exe"
[ -z "$AGY" ] && [ -x "$HOME/.local/bin/agy" ]                && AGY="$HOME/.local/bin/agy"
[ -z "$AGY" ] && [ -x "/usr/local/bin/agy" ]                  && AGY="/usr/local/bin/agy"
echo "${AGY:-NOT_FOUND}"

If it resolves, carry $AGY through every call below. If it prints NOT_FOUND:

Say so plainly and stop. Tell the user the Antigravity CLI is not installed or not on PATH, and that /askagy needs it. Offer to answer the question yourself instead, clearly labelled as your own view rather than a second opinion.

Never fabricate a second opinion. A made-up "agy says…" is worse than no second opinion at all — the entire value of this skill is that the answer came from a different process.

The Prompt Recipe

Write the prompt as these four parts, in this order:

1. Task framing — one sentence naming the role and the job. "You are reviewing a Python data pipeline for correctness bugs."
2. Context agy cannot see — the relevant code, error text, file paths, versions, constraints, and what has already been tried and ruled out.
3. The specific question — one question, sharply stated. Not three loosely related ones.
4. Output shape — how you want the answer back. "List each bug as: file:line, one-sentence cause, minimal fix." Or "Answer in under 200 words, no preamble."