Guides

Who owns a team's skill library

In SkillRelay, the workspace's admins own the library, every skill records its individual authors, and the whole library is exportable at any time, so ownership never depends on staying a customer. The practical ownership questions are role control, offboarding, and custody of the underlying data.

Roles

Three roles: Admins manage everything; Editors create and change skills; Readers use skills and browse but cannot change anything. New members join as Readers and are promoted deliberately. Skills additionally record a creator, and each pack records an owner, who reviews changes to that pack when approvals are on.

Offboarding

Removing a member revokes their connector access immediately, in the same action, so an ex-employee's AI tools stop reaching the library the moment they are removed. Their name stays in the version history of the changes they made, which is the point of attribution: the record of who wrote the team's working knowledge survives the departure.

Data custody

The library lives in SkillRelay's database and is also continuously rendered into a private GitHub repository. By default SkillRelay hosts that repository (one isolated repo per workspace); teams that want custody connect their own GitHub organization during setup, and the repo lives with them, with SkillRelay granted access to that single repository only. Skill content is never used for anything except serving the workspace.

Leaving

The exit is built in: the plugin ZIP and the Markdown export both contain the complete current library, and the rendered GitHub repository is itself a portable, standard-format copy (Agent Skills directories plus the vendor plugin manifests). Deleting a workspace removes its skills, history, members, tokens, and the hosted repository.

SkillRelay is a hosted skill library that syncs across the AI tools a team uses. Overview · Product reference · How it works