What a workflow was
A workflow was a saved, named sequence inside the Antigravity IDE — "review this diff, then summarize, then draft the pull-request body" — invoked as a single unit. Where a rules pack shapes how the agent behaves, a workflow scripted what it did next: a fixed chain of prompts and tool calls that ran end to end. Teams used workflows to pin down repetitive multi-step tasks so nobody had to re-type the chain or remember its order.
Why it was deprecated
Google deprecated workflows in May 2026 when it adopted the open Agent Skills standard — existing workflows still run today, and a successor workflows system is announced but not yet shipped. Skills cover the same ground — a packaged procedure the agent executes — but in a portable, documented format (skills/<name>/SKILL.md) that also works across agents and editors. A workflow only ever ran inside Antigravity, and a skill written for Antigravity can travel. The official migration path is the /migrate-workflows command built into Antigravity App 2.12 and newer: it converts most single-file workflows directly, and flags the ones that need splitting into a skill plus a rule.
Should you still use these entries
Only as migration source material. Every entry below is kept on the map because its underlying logic is still sound — the steps, the prompts and the ordering all transfer cleanly into a SKILL.md. What does not transfer is the packaging: install one as a starting point for a skill, not as a workflow you intend to keep running.
For anything new, go to the skills hub — that is where the maintained ecosystem lives now. Entries that already document a clean migration path say so on their entry page; where porting is non-trivial (multi-step chains that assumed IDE state between steps), the entry describes the split the author used. And if you are still on a pre-2.12 install for other reasons, these packs still work exactly as they did — the deprecation is a statement about the future of the format, not a switch that was flipped.
The migration is usually mechanical rather than conceptual: a workflow's numbered steps become the skill's procedure, its trigger phrase becomes the skill's description, and any per-step tools become the skill's assumptions. The exceptions are chains that branched on intermediate output — those need a rule to guard the decision plus a skill for each branch, which is the one case where /migrate-workflows asks for human help instead of converting silently. The entries below record which of the two shapes each pack falls into.