When I was recommended to upgrade from Gemini CLI to Antigravity CLI, which was released at the same time as Antigravity 2.0, I should have known. Not only was the interface degraded and the amount of information insufficient, but the shared skills deployment method also failed. I don’t understand why the released product is unstable and unusable, and why more important issues like unresponsive servers weren’t prioritized.
│[Bug Report] Antigravity CLI /skills menu fails to list skills on
│ Windows using Junctions
│
│ Environment:
│
│ • OS: Windows 10/11
│ • CLI Version: agy (Latest)
│ • Skills path: C:\Users.gemini\antigravity-cli\skills
│
│ Steps to Reproduce:
│
│ 1. Create a Directory Junction ( mklink /J ) in the skills folder
pointing
│ to a library folder.
│ 2. Ensure each skill folder contains a valid SKILL.md .
│ 3. Launch CLI and type /skills .
│
│ Actual Result:
│ Displays 0 skills and lists default search paths as empty.
│
│ Expected Result:
│ Should list all skills found via junctions, as they are fully functional
│ when called directly using @skill-name .
│
│ Notes:
│ Manual generation of skills.json index file also fails to force the UI
│ to populate the list.