How to Migrate from the Claude Ecosystem to the Antigravity Ecosystem

Description and use

The author migrated reusable agent skills from Claude to Antigravity by auditing, deduplicating, and linking skill directories into each agent’s discovery path, ensuring bidirectional updates and preserving credentials and context.

Problem

The author hit Claude’s usage limit and needed to continue work without losing custom reusable skills, preferences, and project context.

Outcome

The migration preserved all reusable skills and preferences while enabling them to be discovered by Antigravity and Copilot. Bidirectional filesystem links prevented drift, and the author avoided re‑writing skills or losing context.

Workflow

• Audit existing skill directories and count entries
• Separate reusable global skills from project‑specific and broken links
• Resolve duplicate skill names before choosing source of truth
• Identify each agent’s discovery path (Claude, Copilot, Antigravity)
• Create idempotent shell script to link missing skill directories into each agent’s path
• Verify links by writing through each path and confirming reads
• Maintain bidirectional updates via filesystem aliases
• Keep credentials, conversation history, and usage limits separate

Evidence

I hit Claude's usage limit while I still had work to finish.

Source

The migration: bring my reusable skills into Google Antigravity, keep GitHub Copilot connected to the same source, and separate the parts that genuinely transfer from the parts that only look portable.

Source

For each skill, I checked: Where does the directory actually resolve? Does it contain a readable SKILL.md?

Source