@mega__d@steipete I believe so. If you put all skills in global scope, the context is easily flooded.
I build a npm-inspired skill manager which creates a project-level skills contract to resolve skills automatically:
https://t.co/C1NCkuEOO7
@mkralla11@steipete You are right. The tool's main purpose is actually to manage skills from different sources and to create a project-level skill contract per repository.
@mkralla11@steipete Actually that is just a transformation. To deal with this, I wrote a skill package manager with provider adapters so that it doesn’t matter which format the skill has. You can check it out here:
https://t.co/C1NCkuEOO7
I’m building AgentPM:
A flexible skill package manager for AI agents.
Install skills like packages.
Reuse workflows.
Share skills across projects.
npm-style architecture for AI agents.
https://t.co/C1NCkuEOO7
#BuildInPublic#OpenSource#Skills#AI
I have so much gratitude to people who wrote extremely complex software character-by-character. It already feels difficult to remember how much effort it really took.
Thank you for getting us to this point.