Google’s Antigravity is evolving the IDE into an agent-first paradigm. While the agent itself is powerful, its true potential is unlocked when you equip it with Skills.
The best part? You don’t have to build everything from scratch. The developer community has already created a vast ecosystem of skills for Claude (Anthropic). With a simple tweak, you can port these high-quality skills directly into Antigravity.
In this guide, we will walk through how to download skills from GitHub and configure them either Globally (for your entire machine) or Locally (for a specific project).
Step 1: Download Skills from GitHub
First, you need the source files. You can download skills as ZIP files from GitHub. We recommend two primary sources:
- Option A: Antigravity-Ready Skills (Easiest)
- Repository: rominirani/antigravity-skills
- Why: These are already formatted for Antigravity.
- Examples:
git-commit-formatter,xml-formatter.
- Option B: Official Claude Skills (Huge Variety)
- Repository: anthropics/skills
- Why: Contains powerful tools for documentation and coding.
- Examples:
docx(Word),pdfparsing,frontend-design. - Note: These require a small renaming step, explained in Step 4.
How to Download:
- Navigate to the GitHub repository link above.
- Click the green Code button.
- Select Download ZIP.
- Unzip the file on your computer. You will see a
skillsfolder containing sub-folders for each tool.
Step 2: Choose Your Scope (Global vs. Project)
Before installing, decide where you want the skill to live. Antigravity supports two distinct scopes:
1. 🌍 Global Scope (The Toolkit Strategy)
- Best for: General utilities you use across multiple projects.
- Examples:
git-commit-formatter,json-validator,code-reviewer. - Behavior: These skills are available in every Antigravity session on your machine, regardless of which project you open.
2. 📂 Project Scope (The Workspace Strategy)
- Best for: Tasks specific to a single repository or team standards.
- Examples:
database-migration-script,deploy-to-prod,framework-scaffolding. - Behavior: These skills are only available when you open that specific project. If you commit this folder to Git, your entire team gets access to these skills.
Step 3: Installation Guide
Copy the specific skill folder (e.g., git-commit-formatter) from your download and paste it into the correct path below.
Path A: For Global Scope
Use your file explorer to navigate to this directory:
- Mac / Linux:
~/.gemini/antigravity/skills/ - Windows:
%USERPROFILE%\.gemini\antigravity\skills\(UsuallyC:\Users\YourName\.gemini\antigravity\skills\)
Path B: For Project Scope
Navigate to the root folder of your specific project and paste the skill here:
- All OS:
<your-project-root>/.agent/skills/
Note: If the
.agentorskillsfolders do not exist in your project, create them manually.
Step 4: The “Magic” Tweak (Crucial!)
If you downloaded a skill designed for Claude (from Option B in Step 1), you must perform one small edit for Antigravity to recognize it.
- Open the skill folder you just pasted (e.g., inside
.agent/skills/docx/). - Look for the main description file. It is usually named
README.md,CLAUDE.md, orprompt.md. - Rename this file to:
SKILL.md
Why? Antigravity specifically looks for a SKILL.md file to understand the tool’s instructions. Once renamed, the agent can read the prompt and execute scripts just like Claude.
Step 5: Verification
To verify the installation, restart Antigravity or simply start a New Task. Ask the agent:
“List your available skills.”
- Global Check: Open any random project. If the skill appears, it is successfully installed globally.
- Project Check: Open your specific project. If the skill appears there (but not in others), it is successfully scoped to that project.
Quick Summary
| Scope | Location (Mac) | Location (Windows) | Use Case |
| Global | ~/.gemini/antigravity/skills/ | %USERPROFILE%\.gemini\antigravity\skills\ | Personal utilities |
| Project | <Project>/.agent/skills/ | <Project>\.agent\skills\ | Team scripts, App logic |
Ready to build? Start by adding the git-commit-formatter to your Global Scope today and never write a messy commit message again.