How to Install Skills in Antigravity

Installing skills in Antigravity should feel predictable and fast. A good install flow minimizes manual steps, verifies what was installed, and keeps your workspace clean. This guide covers the prerequisites, two installation methods, and the verification steps you should use to confirm everything is ready before you rely on a skill in production work.

What You Need Before You Start

Prepare these items to avoid failed installs and confusing errors:

• A working Antigravity environment that can read from your local filesystem.
• Permission to create or update files in your skills directory.
• A list of the skills you want to install (by name or repository URL).
• A basic understanding of your team’s naming conventions and folder structure.

If you are installing skills for a team, align on a shared directory structure first. That makes updates and reviews much simpler later.

Method 1: Standard Step-by-Step Install

This method is best when you want full control and visibility.

1. Locate the target skill

   • Get the official source URL or package reference.
   • Confirm you are using a trusted source.

2. Choose the installation directory

   • Use a dedicated skills/ directory in your workspace.
   • Keep skills separate from project source code.

3. Install the skill files

   • Copy or pull the skill folder into the directory.
   • Ensure the SKILL.md file is included at the root of the skill.

4. Check dependencies

   • If the skill references scripts, confirm they exist and can run locally.
   • Validate any required tools are installed.

5. Register the skill

   • Add the skill to Antigravity’s list of available skills.
   • Confirm it appears in the UI or CLI list.

This method is slower but gives you visibility into every moving part.

Method 2: One-Click Install

One-click install is for speed. It automates the download and registration process.

A typical flow looks like this:

• Click “Install” from the skill listing or marketplace.
• Antigravity downloads the skill into your designated directory.
• The system registers the skill and validates the SKILL.md file.

This method is convenient but should still end with a verification step.

Verification Checklist

After installation, validate the skill before using it on real tasks:

• The skill appears in the available skills list.
• The SKILL.md file is readable and complete.
• Any referenced scripts exist and run without errors.
• The skill can run a basic “hello” workflow without editing real files.

This quick check prevents subtle failures later.

Common Issues and Fixes

• Skill does not appear: confirm you registered it and that the folder name matches expected patterns.
• Missing scripts: check that the repository contains the referenced files and that paths are correct.
• Permission errors: verify write access to the skills directory.
• Version conflicts: remove older copies and reinstall from a single source.

Most install problems are caused by incorrect paths or incomplete skill folders.

Best Practices for Teams

If multiple people are installing skills, standardize your process:

• Use a shared naming convention for skill folders.
• Document approved sources and versions.
• Add a lightweight review step for new skills.
• Maintain a changelog for important skill updates.

This keeps the skill library predictable and reduces debugging time later.

Final Notes

Installing skills in Antigravity is straightforward when you treat it like a software dependency: verify the source, install cleanly, and confirm the result. A few minutes of validation saves hours of troubleshooting down the road.

Once your install process is reliable, you can scale with confidence and let skills power more of your daily workflows.