Delegate repository analysis and coding tasks to Antigravity CLI without an interactive session. The skill checks structured results and errors, and supports comparing its work with results from another coding agent.
Runs Antigravity CLI headlessly for repository analysis and coding tasks. Use when the user asks to delegate work to Antigravity CLI or compare its result with another coding agent.
Review the instructions the agent will receive before you install.
command -v agy. If it is missing, stop and ask the user to install Antigravity CLI in Code Mate.agy -p "<prompt>" --output-format json
Pass the prompt as one quoted argument. Print mode waits up to --print-timeout (5m by default); pass a shorter value when the caller's own timeout is tighter.
Parse the JSON result and read its status field: anything other than a success status is a failure, and error carries the reason. Treat unparseable output as failure too. Never start interactive Antigravity or an authentication flow.
Antigravity refuses to run headlessly until it is signed in — it returns status: "ERROR" with authentication failed or timed out and tells you to run agy to log in. Do not do that: stop and ask the user to finish Antigravity setup in Code Mate. Never request, read, print, or copy credentials.
Headless mode inherits the permission mode persisted in user settings, and reading and writing files inside the active workspace are auto-approved by default — the default is not a read-only boundary, and a prompt cannot make it one. Do not run it against a writable project for a read-only task. Use a disposable or read-only copy instead. Run against the real project only when the user explicitly requests workspace changes, constrain the directory, and inspect the diff afterward. Never pass --dangerously-skip-permissions, which auto-approves every tool request including outside the workspace.
Example: for an approved edit, ask Antigravity to touch only named files, run it in that project, parse the response and any reported error, and inspect the resulting diff before reporting success.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Record durable Cherry Studio engineering decisions in Agent Notes. Determine which changes need a note, prepare specifications with verifiable acceptance criteria, and manage approval, implementation, rejection, and replacement while preserving the reasoning behind decisions.
Get answers about Cherry Studio from the installed version’s product information. The skill explains features, settings locations, and shortcuts, provides clickable navigation entries, and helps diagnose connection failures, configuration problems, and runtime errors.
Operate the visible browser pane in a Cherry Studio conversation to navigate pages, click controls, fill forms, capture screenshots, and investigate browser issues. It can work with authenticated websites while checking page state and action outcomes.
Operates native desktop apps through Cherry Studio Computer Use. It reads interface information, types, clicks, and captures windows, using fresh observations to choose actions and verify results within the permissions and capabilities available.
Develop and verify changes in a tracked Cherry Studio Electron instance, a running desktop app. Use real UI behavior, logs, and performance measurements to investigate problems, compare fixes, or test a pull request and report the results.
Run repeatable tests of Cherry Studio’s key workflows with Playwright, which checks application behavior through automated interactions. Collect results on macOS and Windows and produce English reports for release acceptance or development validation.