migrate

Migrates Antigravity CLI skills and MCP server configuration from legacy agent records.

3|Updated May 24, 2026
One-click install
npx skills add https://github.com/shayne-snap/oh-my-antigravity --skill migrate-shayne-snap
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: migrate
Source: https://github.com/shayne-snap/oh-my-antigravity/tree/main/plugin/skills/migrate
Command: npx skills add https://github.com/shayne-snap/oh-my-antigravity --skill migrate-shayne-snap

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It resolves the pain of transferring native Antigravity CLI skills and MCP server configuration from other coding agents into your own local Antigravity environment without dragging along host-specific artifacts.

Core Features & Use Cases

  • Detect safe migration candidates: Runs a read-only reconciliation of source records against canonical Antigravity CLI targets, reporting what would be written.
  • Apply only safe, canonical items: Writes only applyable and mergeable skills/MCP configuration while skipping review-required and conflict entries, and never overwrites unmanaged user configuration.
  • Guide safe remediation: Reports status (ready/partial/blocked/empty), explains not-migratable reasons, and provides a manual resolution path for conflicts.
  • Use Cases: Consolidate skill libraries after switching IDEs/agents, standardize MCP server access across team members’ machines, and keep Antigravity CLI behavior consistent across long-lived sessions.

Quick Start

Run omagy migrate detect --json to see what would be migrated and whether you have any safe applyable targets.

Frequently Asked Questions about migrate

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I migrate MCP server configuration and native skills into Antigravity CLI?

To migrate MCP server configuration and native skills into Antigravity CLI, run a detect-then-apply flow that reconciles legacy agent records against canonical targets and writes only safe, mergeable items to your local user configuration.

What happens to conflicting skills during MCP configuration migration?

During MCP configuration migration, conflicting skills and review-required entries are explicitly skipped to enforce safety, preserving your unmanaged user configuration while reporting a blocked or partial status with manual resolution paths.

Can I migrate coding agent skills from codex, claude, or cursor into my local setup?

Yes, you can migrate coding agent skills from codex, claude, gemini, and cursor-native sources into your local Antigravity environment, provided the migration process successfully reconciles them as canonical, applyable targets.

How do I check if my skills are safe to migrate before applying changes?

To check if your skills are safe to migrate before applying changes, run a read-only detection command with JSON reporting to preview which candidates are applyable and which are blocked by conflicts or host-specific runtime dependencies.

Are host-specific runtime artifacts included when transferring Antigravity CLI skills?

No, host-specific runtime-dependent artifacts are explicitly excluded when transferring Antigravity CLI skills to ensure only canonical configuration and mergeable skills are written into the local Antigravity user configuration.