Skills availability for agents that work directly against the repository (without node_modules)

[fguini]

Hey! First of all, great work on Intent — the idea of versioning skills alongside the package is really elegant.

I have a question about a scenario I'm running into: when intent install sets up the skill mappings, the load paths point to node_modules/.... That works perfectly for local development, but I use GitHub PR reviewing agents that work directly against the repository without running npm install first, so those paths are dead references and the skills never load.

I'm also evaluating other automation workflows where we'd like to use the repository itself as the source of truth (no installation step, to keep things fast and simple) — so the same problem applies.

I was wondering if there's any plan to handle this kind of scenario in the future — for example, resolving skills through the registry as a fallback when the local path isn't available. Or is there another approach you'd recommend?

Thanks!

[KyleAMathews]

Yeah you could ask your agent when running intent install to get paths to unpkg or some other hosted version instead of an installed version. intent install just loads a SKILL so you can override it easily with custom instructions.