| name | ask |
| description | Ask Google's Antigravity CLI (agy staffer, fast Gemini) a cheap one-shot question - the fast zero-tool mode and the post-install smoke test. Use when the user says /agy:ask, "ask agy", "quick second opinion from agy", or right after installing to verify the plugin works. |
| argument-hint | [--continue] [--model <id>|--effort low|medium|high] [--timeout <dur>] "question" |
| allowed-tools | Bash(node:*) |
agy ask
The quick mode: one question in, one answer out, ~3 seconds on the default gemini-3.7-flash-low. Zero tools by design (restricted profile, question-only prompt), so it needs no setup and works on a fresh install — run it first as the smoke test: ask "reply with OK".
ask is the only persona that runs in the foreground: the call blocks and the answer comes back on stdout. staffer, researcher, reviewer, and implementer instead return a background job id (see the jobs skill, ../jobs/SKILL.md).
Locating the companion
This skill file lives at <plugin-root>/skills/ask/SKILL.md; resolve the companion path relative to this skill directory:
node "<skill-dir>/../../companion/agy-companion.mjs" ask [flags] "question"
[!IMPORTANT]
Run this command unsandboxed — agy needs a localhost port and its OAuth token file, which harness sandboxes hide. In Codex, request escalated permissions for the command. Details: ../jobs/references/troubleshooting.md.
Flags (all optional)
--continue — reuse the last ask conversation; --conversation <id> targets a specific one.--model <id> or --effort low|medium|high — default model is gemini-3.7-flash-low.--timeout <dur> — default 2m.
ask is always restricted (it is tool-free, so there is nothing to unrestrict); --unrestricted is ignored with a note on stderr. That is fixed for ask alone — the tool-using personas default to unrestricted, where --restricted is an opt-in hardening flag. Execution style is likewise fixed per mode and no flag changes it.
Rules
- Pass the user's question through verbatim and return the answer verbatim. The
[agy-staff] telemetry line arrives on stderr and is metadata for you, the calling agent — do not show it to the user; mention the follow-up ability in natural language when relevant, and give model/duration/token numbers only if asked.
- If the answer says "not sure", relay it as-is; do not silently substitute your own answer.
- On any companion error: quote it verbatim, add one line of your own diagnosis, stop. Full failure protocol:
../jobs/SKILL.md.
