Based on Google’s official docs, checked November 1, 2026

Antigravity skills: create, store and run SKILL.md skills

Skills in Google Antigravity are folders with a SKILL.md file that teach the agent how to do one kind of task. On every turn the agent sees each skill’s name and description, and reads the full instructions only when a skill looks relevant. Skills are an open standard, so the same folder format works in other agents too. This guide follows Antigravity’s Agent skills docs, checked November 1, 2026, and covers where the App, CLI and IDE look for skills.

1. 1. Create the skill folder

   Antigravity defaults to .agents/skills in your workspace (it still reads the older .agent/skills). Each skill is its own folder with a required SKILL.md and optional scripts/, examples/ and resources/ folders.

   mkdir -p .agents/skills/code-review

2. 2. Write SKILL.md with frontmatter

   description is required and is what the agent reads to decide whether to use the skill; name is optional and defaults to the folder name (lowercase, hyphens). Write the description in the third person with keywords for when it applies.

   ---
   name: code-review
   description: Reviews code changes for bugs, style issues, and best practices. Use when reviewing pull requests or checking code quality.
   ---
   
   # Code Review Skill
   
   1. Correctness: verify the code meets the spec.
   2. Edge cases: check error conditions and boundaries.

3. 3. Run it

   You don’t have to name a skill; the agent picks it from context. To force it, type / and the skill name in the App message box or the CLI prompt. In the CLI, every skill becomes a slash command; run /skills reload after adding one mid-session.

   /code-review

4. 4. Share skills globally or as a plugin

   Put skills you want in every project in ~/.gemini/config/skills/, which the App and CLI share. In the CLI you can install skill bundles packaged as plugins with agy plugin install, from the official marketplace, a GitHub URL or a local path.

   agy plugin list --json
   agy plugin install ./my-skills-plugin

Where each surface looks for skills

App: .agents/skills/ in the workspace (and in each parent folder up to the repository root) and ~/.gemini/config/skills/ globally.

CLI: the same two locations plus plugin skills under ~/.gemini/config/plugins/, and ~/.gemini/antigravity-cli/skills/ and ~/.gemini/skills/, which the App doesn’t read.

IDE: .agents/skills/ in the workspace and ~/.gemini/config/skills/ globally, with the legacy ~/.gemini/antigravity/skills/ still supported. Check active skills from the Customizations menu in the agent side panel.

How the agent uses a skill

Antigravity uses progressive disclosure: discovery (names and descriptions on every turn), activation (it reads the full SKILL.md when relevant) and execution (it follows the instructions). That keeps unused skills cheap, so the description is the part worth the most care.

Best practices from the docs

Keep each skill focused on one job instead of a do-everything skill. Make the description specific about what the skill does and when. If a skill ships scripts, tell the agent to run them with --help rather than reading their source, to keep context focused. For complex skills, add a decision tree that helps the agent pick an approach.

Tips

• Commit .agents/skills/ so your whole team gets the same skills.
• Because skills are an open standard, a well-written SKILL.md can be reused in Claude Code, Codex or Copilot; see our portable skills guide for each agent’s folder.
• Review third-party skill plugins before installing; a skill’s scripts run with your agent’s permissions.

Next steps

Sources

• https://antigravity.google/docs/skills · checked 2026-11-01