Run Navi’s installer from the project you want your coding agent to review:
The installer creates two symlinks and one ownership receipt:
The skill and launcher remain in the installed package. Navi does not copy
either file into your project, so package updates cannot leave a stale second
copy behind.
Verify the project-local launcher:
To connect a different project, pass its path:
The symlink installer is supported on macOS and Linux.
Remove Navi’s links
From the connected project:
Or name another project:
Navi removes only links that still match its ownership receipt. It leaves
foreign files, changed links, and non-empty directories alone.
Alternative: let the Skills CLI manage the skill
Use this route when you want npx skills to own agent discovery instead of
Navi’s symlink installer:
This installs the interop skill and its lockfile. It does not install Navi or
create .agents/bin/navi, so keep the project dependency:
Without the symlink launcher, the interop skill calls the project dependency
without downloading another copy:
Choose one owner for navi-interop in each project. Navi’s installer owns the
symlink and receipt; npx skills owns a managed copy and lockfile.