Repositories

A repository is a container for your AI resources — versioned, searchable, and (optionally) connected to Git for workflows your team already uses.

Create a repository

1. Open Repositories in the dashboard.
2. Create / New repository.
3. Set name, slug, and visibility.
4. Confirm. You are typically added as owner of the new repo.

Slugs

• Short, URL-safe strings (e.g. my-skill-pack).
• Unique within the owning organization (or within your user scope for personal repos).
• Changing a slug later may break bookmarks or integrations — treat it as stable.

Visibility

Type	Typical meaning
Private	Only members (and invited teams) can see or change content.
Public	Readable by a wider audience according to your product and compliance settings; write access still follows roles.

Exact behavior can depend on your plan and tenant configuration.

Members and roles

Repositories use role-based access:

Role	Typical capabilities
Owner	Full control: settings, dangerous actions, member management (as allowed by product).
Maintainer	Manage content and collaborators; cannot always transfer ownership or delete the org.
Reader	Read access; cannot change protected settings or content (unless your admin configured otherwise).

Inviting people

1. Open the repository’s Members (or Access) section.
2. Add a user by ID or email (depending on UI).
3. Assign a role.

Last owner

The platform usually prevents removing or demoting the last owner so the repository is never left without an owner.

Teams

If teams are enabled, you can attach a team to a repository with a role. Users in that team inherit access without individual invites.

API keys (optional)

Some repositories support API keys for automation (CLI, CI, integrations). Treat keys like passwords: rotate them if leaked and use the minimum scope your integration needs.

Deleting a repository

Deletion may be permanent. Export important resources and confirm with your compliance or security policy before removing production repositories.