DEV Community

John Banker
John Banker

Posted on Originally published at getvibekits.com

Antigravity is retiring workflows. Here's how to move them to skills in 2 minutes

#ai #beginners #productivity #tutorial

If you used workflows in Google Antigravity (the step-by-step routines you ran with /workflow-name), here's the news: Antigravity's docs say "current workflows will stop working on October 19, 2026", and that instructions for a new workflows system will follow "shortly". When I checked on Oct 30, those instructions still weren't up, and the docs point you to skills in the meantime.

The good news is that moving over takes about two minutes, and you keep running things the same way, with /name.

The 2-minute fix

  1. Open the Antigravity app and start a chat.
  2. Run /migrate-workflows.
  3. It turns each workflow in .agents/workflows/ (and your global ones in ~/.gemini/config/workflows/) into a skill, and renames the old file to .bak so nothing is lost.
  4. Run it like before: /deploy-check, /release, whatever you named it.

That's it. If you'd rather do it by hand, keep reading.

What a skill looks like

A skill is a folder with a SKILL.md inside. Only the name and description load up front; the rest loads when the agent actually needs it, so a long skill costs you very little context the rest of the time.

.agents/skills/deploy-check/SKILL.md

---
name: deploy-check
description: "Runs the pre-deploy checks for this project (lint, tests, production build) and reports pass or fail for each. Use before deploying or when asked if the app is ready to ship."
---

# Deploy check

Run these one at a time and report pass or fail for each:
1. npm run lint
2. npm test
3. npm run build
If something fails, explain why in plain English. Don't fix anything until I say so.
Enter fullscreen mode Exit fullscreen mode

Global skills (every project) go in ~/.gemini/config/skills/<name>/. If you use the Antigravity CLI, it's ~/.gemini/antigravity-cli/skills/<name>/.

Write the description with the words you'd actually type when asking for it. That's how the agent decides when to pull it in.

Rule or skill?

Antigravity's docs draw the line simply:

  • Rule = a constraint that should always hold ("always use zod for validation"). Goes in AGENTS.md or .agents/rules/.
  • Skill = a multi-step job ("how to run database migrations"). Goes in .agents/skills/<name>/SKILL.md.

If your old workflow was really just "always do X", it probably belongs in a rule instead.

While you're in there: 3 rule mistakes that fail silently

  1. Trigger spelling. Files in .agents/rules/ need a --- header with trigger: set to exactly always_on, model_decision, glob or manual. alwaysOn isn't one of them, so a rule with that spelling won't load the way you expect.
  2. Subfolders. Antigravity only scans files directly inside .agents/rules/. .agents/rules/frontend/react.md is ignored unless you list it in .agents/rules.json.
  3. Size. A single rule file is cut off at 24,000 bytes, and all global and always-on rules share a 20,000-token budget. Keep always-on rules short.

Coming from Gemini CLI?

For unpaid and Google One users, Gemini CLI was replaced by Antigravity CLI on June 18, 2026. Your GEMINI.md and AGENTS.md files keep working with no changes. Workspace skills are the exception: move them from .gemini/skills/ to .agents/skills/.

Did /migrate-workflows work cleanly for you, or did anything break? Tell me in the comments and I'll add the fix.

I keep a fuller version on my site, with 8 copy-paste Antigravity rules (one for each trigger), the rules.json example and links to Google's docs: https://getvibekits.com/rules/antigravity-rules/ . It's free, no signup.

Top comments (0)