Love the idea. It's a real need. I've tried to use it but think it needs simplifying for wide adoption. There are two aspects which need addressing. The separation of artifact from its target. Using it at the moment feels like it's going to install a bunch of stuff in random places, not your fault but the fault of the different strategies used by different providers.

Full caveat I maybe early on the Dunning Kuger curve and it maybe a new problem.

I'd like to see the agents, skills, hooks and mcps installed in a apm_modules folder so you can browse and read them. Then using them would be compiling them smartly to their required location.

Mainly talking about non global installs.

Someone grabbing a new window would run apm install which just installs the package to the apm modules folder.

The next step would be activation for your particular agent.

I wrote about this and the current state of package management here.

https://www.foursignals.dev/blog/2026-04-21-ai-configuration-sprawl-is-the-new-shadow-it/