Learn how to migrate your legacy Antigravity workflows to modern, standard Agent skills.

Workflows were originally introduced in the Antigravity IDE as single Markdown files designed for repeatable prompt sequences. While effective for simple instructions, monolithic files presented challenges as tasks grew in complexity.

In May 2026, Antigravity adopted the open industry standard for Agent Skills. Migrating to skills provides significant architectural and operational improvements:

---

Feature	Legacy Workflows (.md)	Agent Skills (SKILL.md)
Specification	Proprietary Antigravity format	Open Agent Skills Standard (agentskills.io)
Structure	Single standalone .md file	Directory bundle (<skill-name>/SKILL.md + assets)
Workspace Path	.agents/workflows/<name>.md	.agents/skills/<name>/SKILL.md
Global Path	~/.gemini/config/workflows/<name>.md	~/.gemini/config/skills/<name>/SKILL.md
Context Loading	Entire file loaded into prompt	Progressive: Metadata indexed upfront; body loaded on demand
Bundled Assets	Not supported (everything must fit in one prompt)	Supported (scripts/, references/, examples/)
Slash Commands	Supported (/<workflow-name>)	Supported (/<skill-name>)
Autonomous Discovery	Supported	Supported (enhanced semantic matching using description)
File Size Limit	12,000 characters	Unrestricted bundle; modular multi-file architecture

---

Antigravity provides an automated migration command that discovers your existing workflows and converts them to skill directory bundles.

Complete the following steps to automatically migrate your workflows:

1. Open Antigravity 2.0.
2. Run the migration command:

   /migrate-workflows

3. The agent performs the following actions:
   • Scans both global (~/.gemini/config/workflows/) and workspace-level (.agents/workflows/) directories.
   • Parses each workflow’s YAML frontmatter and body.
   • Scaffolds .agents/skills/<workflow-name>/SKILL.md with compliant metadata.
   • Archives original workflow files by appending .bak (for example, deploy.md becomes deploy.md.bak).
   • Immediately activates the new skills for slash commands and autonomous agent usage.

---

If you prefer to migrate your workflows manually or want to refactor monolithic prompts into modular skill packages, follow these steps:

1. Create the skill directory

   Section titled “Create the skill directory”

   In your workspace or global configuration directory, create a new folder named after your workflow under skills/:

   • Workspace Skill
   • Global Skill

   mkdir -p .agents/skills/deploy-staging

2. Create and populate SKILL.md

   Section titled “Create and populate SKILL.md”

   Move your existing workflow Markdown file to SKILL.md inside the new folder:

   mv .agents/workflows/deploy-staging.md .agents/skills/deploy-staging/SKILL.md

3. Standardize the YAML frontmatter

   Section titled “Standardize the YAML frontmatter”

   Ensure your SKILL.md begins with the standard name and description frontmatter fields. The description should clearly explain what the skill does and when the agent should use it:

   ---
   name: deploy-staging
   description: Deploys the current project build to the staging preview environment on App Engine. Use when testing staging releases or verifying PR previews.
   ---
   
   # Deploy Staging
   
   Follow these instructions to deploy the current build to staging...

4. (Optional) Extract scripts and resources

   Section titled “(Optional) Extract scripts and resources”

   If your workflow contains embedded scripts, code snippets, or lengthy reference documentation, extract them into dedicated subdirectories to keep SKILL.md lean:

   .agents/skills/deploy-staging/
   ├── SKILL.md
   ├── scripts/
   │   └── deploy.sh
   └── references/
       └── staging-endpoints.json

   In SKILL.md, instruct the agent to run or inspect those files when needed rather than duplicating them in the prompt.

5. Verify the migrated skill

   Section titled “Verify the migrated skill”

   Invoke the skill directly in Antigravity 2.0:

   /deploy-staging

   The agent loads the skill metadata and executes the steps.

---

---
name: build-and-test
description: Run test suites and verify build
---

Run the following checks sequentially:
1. First run `npm run check` to verify TypeScript and template integrity.
2. Next execute `npm run test` for unit tests.
3. If tests pass, run `npm run build` and report the generated bundle size.

.agents/skills/build-and-test/
├── SKILL.md
└── scripts/
    └── verify-bundle.js

---
name: build-and-test
description: Runs full validation suite including TypeScript checks, unit tests, and production build verification. Use before submitting changes.
---

# Build and Test Suite

Execute the project verification pipeline:

1. **Type & Template Diagnostics**:
   ```bash
   npm run check
   ```

2. **Unit Tests**:
   ```bash
   npm run test
   ```

3. **Production Build & Bundle Size Analysis**:
   ```bash
   npm run build
   node scripts/verify-bundle.js
   ```

No. Workflows remain operational in Antigravity until November 1, 2026. After this date, workflow directories are no longer indexed or executable using slash commands.

Yes. You can invoke any skill located in .agents/skills/<name>/ or ~/.gemini/config/skills/<name>/ by typing /<name> in chat, just like legacy workflows.

Skills take precedence over legacy workflows. If both .agents/skills/deploy/ and .agents/workflows/deploy.md exist, Antigravity executes the skill.

Place global skills in ~/.gemini/config/skills/<skill-name>/SKILL.md to make them accessible across all your workspaces.

Explore the following resources to learn more:

• Agent skills overview: Full guide on creating, configuring, and organizing skills.
• Customizing agent rules: Learn how to define persistent workspace and global rules.
• Antigravity CLI plugins and skills: Manage skills in the Antigravity CLI.