Antigravity's Graphify skill uses pip to install graphifyy instead of uv, even when uv is available and graphify was installed with uv

[zenwav]

Graphify is installed system-wide using uv

Antigravity Build Information

Version: 1.118.1 (system setup)
Commit: 034f571df509819cc10b0c8129f66ef77a542f0e
Date: 2026-04-29T17:36:44+03:00
Electron: 39.8.8
ElectronBuildId: 13870025
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
OS: Windows_NT x64 10.0.19045

Graphify Version Information

PS C:\> graphify -v
graphify 0.7.15

[safishamsi]

Fixed in v0.7.16 — Step 1 install fallback in skill.md and skill-windows.md now checks for uv first and runs uv tool install --upgrade graphifyy before falling back to pip.

[zenwav]

@safishamsi, Latest update didn't resolve my issue.

[safishamsi]

Hey @zenwav — thanks for the screenshot, it made the root cause clear.

What was wrong: The skill was checking python import graphify, failing, installing via uv tool install, but then saving the path of bare python to .graphify_python — not the uv-managed Python where graphify actually lives. Every subsequent step then used the wrong interpreter and hit ModuleNotFoundError.

What we fixed: When uv or pipx installs graphify, graphify.exe and python.exe sit in the same Scripts\ directory. The skill now uses Get-Command graphify to find that directory and picks up the co-located Python directly. We also replaced all bare python calls throughout the skill with & (Get-Content graphify-out\.graphify_python) so every step consistently uses the saved interpreter.

Pushed in commit 1ac3b96 on v8. To get the fix, reinstall the skill:

graphify install

Let me know if it works.

[zenwav]

@safishamsi, On Windows, running graphify antigravity install installs SKILL.md to C:\Users\user\.agents\skills\graphify\SKILL.md, so Antigravity (Gemini/Claude) reads SKILL.md instead of skill-windows.md. Shouldn't it be installing skill-windows.md instead, just like it does when running graphify install --platform windows?

Also, running uv tool install graphifyy will, by default, place a shim called graphify.exe directly into C:\Users\user\.local\bin (this is the folder that uv asks to add to the PATH), while the Python executable is located at C:\Users\user\AppData\Roaming\uv\tools\graphifyy\Scripts. If the UV_TOOL_DIR environment variable is set to, say, D:\uv\tools, then the Python executable will be present at D:\uv\tools\graphifyy\Scripts\python.exe.

[safishamsi]

Two more fixes pushed in ac9587b:

1. graphify antigravity install now installs the correct skill on Windows
Previously it always copied skill.md (bash syntax). On Windows it now installs skill-windows.md (PowerShell) to .agents/skills/graphify/SKILL.md automatically.

2. Python detection completely rewritten
The previous fix (Get-Command graphify → same Scripts dir) was wrong — uv places a shim in ~\.local\bin while Python lives in AppData\Roaming\uv\tools\graphifyy\Scripts. We now ask the tools directly:

• uv: uv tool dir → constructs <dir>\graphifyy\Scripts\python.exe — handles UV_TOOL_DIR automatically
• pipx: pipx environment --value PIPX_LOCAL_VENVS → handles PIPX_HOME automatically
• fallback: bare python with an import check

To get the fix: uv tool upgrade graphifyy then graphify antigravity install

Also let me know if it is resolved on your end.

[zenwav]

It's creating these temporary files in the root project directory. Shouldn't these files be created inside the graphify-out directory?

[safishamsi]

I’ll look into it tonight then, interesting. Thanks for promptly testing the fixes pushed

…

On Fri, 15 May 2026 at 14:25, Nehal Choudhury ***@***.***> wrote: *zenwav* left a comment (Graphify-Labs/graphify#831) <#831 (comment)> Now, it's creating these files in the root project directory. Shouldn't these files be created inside the graphify-out directory? ***@***.*** (view on web) <https://github.com/user-attachments/assets/25e6c406-40c8-445a-86f4-f214c5056a88> — Reply to this email directly, view it on GitHub <#831 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BTSTP67BWSHVLLSKSSSLGNL424LDVAVCNFSM6AAAAACY2EZY36VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DINRQGEZDOMBTGU> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[zenwav]

@safishamsi, Kiro IDE throws "Invalid SKILL.md frontmatter" error for graphify skill.

Also, both Antigravity and Kiro IDE support global-scope skills that work across all projects. Running graphify install --platform windows installs skills for Claude at the global level, making them available everywhere. Maybe you should consider doing the same for Antigravity and Kiro IDE, instead of installing their skills only in the current workspace. Oh, and on Windows, instead of using skill.md when running graphify kiro install, you should use skill-windows.md. Let me know if you'd like me to open separate GitHub issues for these.

Source:

1. https://kiro.dev/docs/skills/
2. https://antigravity.google/docs/skills