Turns out Google’s new coding tool speaks a different language than Claude Code, and it’s breaking every community skill built for the other side. A developer who goes by u/Top_Midnight_68 ran into that wall and built a fix instead of waiting for one. Antigravity, Google’s fresh agentic IDE, doesn’t understand Bash, Read, Glob, or Edit calls, the tool calls every Claude Code or Cursor skill relies on.
What’s new
The project is called antigravity-skill-porter, and it’s a direct shot at that compatibility gap. Feed it a SKILL.md file written for Claude Code or Cursor, and it rewrites the tool calls so Antigravity can run them natively. Bash becomes run_command. Read becomes view_file. Edit becomes replace_file_content. No more silent failures because the IDE doesn’t recognize a function name it’s never seen.
Skills built for Claude Code also tend to look for a CLAUDE.md file for project context, something Antigravity has no concept of. The porter accounts for that mismatch too, so a skill doesn’t just fail quietly when it can’t find the file it expects. Small detail, but it’s exactly the kind of thing that turns a “should just work” import into an hour of debugging if nobody handles it.
The twist
Here’s the part that makes this more than a find-and-replace script. The porter doesn’t just translate syntax, it upgrades the workflow underneath it. Most community skills assume one agent working through steps in a strict line, because that’s how Claude Code and Cursor operate. Antigravity supports parallel subagents instead. So the tool scans each skill for multi-persona or review-style patterns, the kind where a workflow says “have three experts weigh in.” It then automatically injects native invoke_subagent batch arrays in their place. A skill that used to run five checks one after another can now fire all five at once inside Antigravity. That’s a real speed upgrade, not just a format conversion. It’s the difference between porting a skill and actually making it better on the new platform.
The creator tested the porter on some well-known skills before posting it. Andrej Karpathy’s LLM Council, Anthropic’s frontend-design skill, and Sahil Lavingia’s minimalist-entrepreneur skill all imported clean. Those three cover pretty different territory too: one is a multi-model debate framework, one is design guidance, one is a business-strategy workflow. Getting all three to convert cleanly is a decent sign the tool mapping is solid, not just tuned to one narrow case.
Try it yourself
If you want to run this on your own skill collection, here’s the short version:
- 🔄 Point the tool at any GitHub repo, subfolder, or multi-skill bundle. It reads a normal skills repo, no special packaging needed.
- 🔍 Run the dry-run diff first. It shows every change before anything touches your Antigravity setup, so nothing gets overwritten blind.
- ⚡ Let the porter flag parallel-friendly workflows and inject the subagent batch arrays on its own.
- 📦 Install with one command once the diff looks right.
Pro tips
Run the dry-run on every skill before trusting it, even the ones from big names. One commenter, u/Majestic_Log_4429, said the tool call mismatch had been driving them up the wall all week. They called the dry-run diff “a smart touch” because they’re always paranoid about scripts bulldozing their setup. That instinct is the right one here, and it applies to any tool that touches your local config automatically.
Second tip: if you write your own skills and want them portable across IDEs, keep the tool call logic simple and predictable. A clean SKILL.md with obvious, single-purpose steps is far easier for a porter to map correctly. Skip the custom shell tricks and nested conditionals. Write for portability now, and you won’t be rewriting skills every time a new agentic IDE shows up.
Third tip: don’t skip the parallel-detection step even if your skill looks purely sequential at first glance. Review workflows and comparison tasks are prime candidates for the subagent upgrade. Anything with “check this from multiple angles” logic probably qualifies too, and you might not notice the opportunity until the porter flags it for you.
This is a young, one-person project sitting on a single upvote so far, and it’s not pretending to be a finished product. There’s no mention of a plugin marketplace or auto-update system yet. Treat every import as a one-time conversion you should recheck when the source skill changes. But it’s solving a problem that’s about to get bigger. Every new agentic IDE fragments the skills ecosystem a little more, and skill authors are not going to rewrite their work for each one.
I think tools like this matter more than they get credit for. Someone building a bridge instead of picking a side is worth watching, especially this early while the agentic IDE landscape is still splitting into camps.
Go grab the repo, run the dry-run on one skill you actually use, and see what changes before you commit anything. 🚀
Frequently Asked Questions
Q: What tool mappings happen during conversion?
Bash → run_command, Read → view_file, Edit → replace_file_content, Glob → list_files. The mapping is deterministic, so conversions are predictable, use the dry-run diff to verify everything before applying.
Q: Will chained Edits from complex Cursor skills actually work?
Individual Edits map fine, but complex chaining patterns can be tricky. Check the dry-run diff carefully, if something looks off, you can tweak the skill by hand before running the conversion.
Q: How safe is the converter? Will the dry-run actually prevent accidents?
The dry-run shows exactly what would change before anything applies, giving you a chance to review everything. This is way safer than blind automation. Check the diff, and if anything looks wrong, you can fix it before converting.
Q: Can I convert my own skills, or just famous ones like Karpathy’s?
Any SKILL.md workflow from any GitHub repo works. The creator tested on well-known skills (Karpathy’s LLM Council, Anthropic’s frontend-design, etc.), but your community skills should convert just fine. Cursor-heavy skills might need manual tweaking, but that’s totally doable.
I built an open-source tool to port & optimize Claude Code / Cursor skills for Google Antigravity
by u/Top_Midnight_68 in PromptEngineering