3 ms·
The main problem I encountered around this is that skills need to be edited across projects and across team members in a controlled way. Git is of course requir
by mstr32 27d ago
The main problem I encountered around this is that skills need to be edited across projects and across team members in a controlled way. Git is of course required for this but is not enough so I built a tool to do just that:
https://github.com/genged/capshelf https://github.com/genged/capshelf
Using capshelf I manage my skills across projects.
When I start a new project I can just:
$ capshelf add security-review
From the skill repo.
And if I create a new skill I can promote it to the repo so everyone can install it:
$ capshelf promote security-review
It pins the skill content hash so there are no unexpected edits that can break your flow. It also supports MCP configs and agent configs.