Sharing agent skills across a company: where a Git repo falls short

Description and use

Hexis provides secure, department‑specific access to agent skills while preserving Git history and enabling non‑technical users to participate.

Problem

A shared Git repository for agent skills works when all users are comfortable with Git, but fails when departments like Finance, HR, and IT need to use and update skills without exposing each other’s confidential content.

Outcome

Hexis enabled secure, department‑specific access to agent skills while preserving Git history and allowing non‑technical users to participate, solving the access and approval bottleneck.

Workflow

• Define read permissions per skill and supporting documents
• Set proposal permissions and required approvers per department
• Configure Hexis to enforce these rules
• Users submit changes via Hexis interface
• Approvers review and approve or reject changes
• Approved changes are merged into the Git repo
• Non‑Git users interact with skills through their agent interface

Evidence

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.

Source