Keeping agent skills in a shared Git repo works well when everyone is comfortable with Git and can read the same files. Things get awkward when Finance, HR, and IT need to use and update them too.
My co-founder Ali wrote about that transition at Bevel. The tricky example: one change touches an IT offboarding instruction and a Finance document. Both owners need to approve it, but neither should automatically get access to the other department's contents.
That leaves three separate things to design:
- Who can read each skill and its supporting documents.
- Who can propose changes, and whose approval is required.
- How someone who doesn't use Git can participate.
We built Hexis around those requirements: keep Markdown and Git history, put permissions and review around them, and let people connect through their agent. It's open source.
If a shared repo already meets your team's needs, that's a good place to stay. The extra layer becomes useful when access and ownership differ across teams.
Ali's full article, with the review workflow and screenshots.
Top comments (0)