Support keyword: antigravity cli skills
Skills are reusable agent workflows, so migration is not just a file copy. Confirm scope, project context, and behavior before relying on them.
Updated on 2026-05-27. Independent guide. Use official Google links for downloads and account actions.
Not affiliated with Google. No binaries, mirrors, login forms, or copied install commands are hosted here.
When users search for antigravity cli skills, they usually want to know whether their Gemini CLI custom workflows still work. A useful answer should explain skill scope, workspace instructions, and test prompts rather than only defining the word "skill".
Skills can encode powerful habits: how to debug, how to write docs, how to deploy, how to review code, or how to use internal tools. That makes them valuable, but also risky when moved into a new agent environment without testing.
AGENTS.md, GEMINI.md, or both.| Skill type | Best for | Risk if misplaced |
|---|---|---|
| Global skill | General workflows you use across many projects. | Project-specific assumptions leak everywhere. |
| Workspace skill | One repo, product, or deployment workflow. | The CLI may miss it if the path or context file is wrong. |
| Instruction file | Stable repo rules, test commands, and coding conventions. | Outdated instructions can steer the agent into wrong commands. |
After migration, keep a small smoke-test prompt for each important skill. The prompt should prove that the skill loads, understands the workspace, and does not assume an old command name or path. If the skill can trigger writes, package installs, or external tool calls, test it in a branch and pair it with the permissions guide before using it on a real task.
Sources: official Google Antigravity product pages, Google Antigravity CLI documentation, and the Google Developers transition announcement. This site is an independent guide and is not affiliated with Google.
Do not assume that. Inventory, move, and test skills explicitly.
No. Project-specific skills should stay close to the workspace so they do not affect unrelated projects.
Run it on a harmless read-only prompt, then test a small edit in a disposable branch.