Skip to main content
Better Skills uses vaults to organize and share skills. Enterprise vaults enable team collaboration with role-based permissions.

​
Vault Types

Better Skills supports three vault types:

​
Personal Vault

Every user has one personal vault. You are the owner and have full control.
  • Permissions: Full read/write/admin access
  • Membership: Owner only (you)
  • Use case: Private skills and personal workflows

​
Enterprise Vault

Shared vaults for teams and organizations with role-based access control.
  • Permissions: Based on role (owner, admin, member)
  • Membership: Multiple users
  • Use case: Team-wide skills and shared knowledge

​
System Default Vault

The system-default vault contains default skills provided by Better Skills.
  • Permissions: Read-only for all users
  • Membership: Automatic for all users
  • Use case: Official default skills
The system default vault is managed by Better Skills and cannot be modified by users.

​
Creating Enterprise Vaults

Create an enterprise vault through the web console:
1

Navigate to Vaults

Go to your Better Skills dashboard and click Vaults in the sidebar.
2

Create New Vault

Click Create Vault and fill in:
  • Name: Display name for the vault
  • Slug: URL-friendly identifier (lowercase, hyphens)
  • Type: Select “Enterprise”
  • Color (optional): Theme color for the vault
3

Set as Owner

You are automatically assigned the “owner” role on creation.
Enterprise vaults support multiple members with different permission levels.

​
Inviting Team Members

Add collaborators to your enterprise vault:
1

Open Vault Settings

Navigate to the vault and click Settings → Members.
2

Send Invitation

Click Invite Member and enter:
  • Email: Team member’s email address
  • Role: Select member, admin, or owner
  • Expiration (optional): Invitation expiry time
3

Invitation Status

The invitation is sent via email. Track status:
  • Pending: Invitation sent, awaiting response
  • Accepted: Member joined the vault
  • Declined: Member declined the invitation
  • Revoked: Invitation canceled by owner/admin
  • Expired: Invitation passed expiry time
Members must have a Better Skills account to accept invitations.

​
Roles and Permissions

Enter prise vaults use role-based access control.

​
Owner

Full administrative control over the vault. Permissions:
  • Read all skills and resources
  • Create, update, and delete skills
  • Manage vault settings (name, slug, color)
  • Invite and remove members
  • Assign and change roles (including promoting to admin)
  • Delete the vault
Use case: Vault creator and primary administrator

​
Admin

Elevated permissions for managing content and members. Permissions:
  • Read all skills and resources
  • Create, update, and delete skills
  • Invite and remove members
  • Assign member and admin roles (cannot assign owner)
Restrictions:
  • Cannot delete the vault
  • Cannot change vault settings
  • Cannot promote others to owner
Use case: Trusted team leads managing skills and members

​
Member

Read-only access to vault skills. Permissions:
  • Read all skills and resources
  • Clone skills to personal vault (creates a copy)
  • Use skills in agent sessions
Restrictions:
  • Cannot create, update, or delete skills
  • Cannot invite or manage members
  • Cannot change vault settings
Use case: Team members consuming shared skills

​
Permission Model

Permissions are derived from vault type and membership role.

​
Permission Matrix

Vault TypeRoleReadWriteAdmin
PersonalOwner✓✓✓
EnterpriseOwner✓✓✓
EnterpriseAdmin✓✓Partial
EnterpriseMember✓✗✗
System Default(any)✓✗✗

​
Vault Boundaries

Skills can only reference resources and skills within the same vault:
Valid: Skill in “team-vault” mentions another skill in “team-vault”
Invalid: Skill in “team-vault” tries to mention resource in “other-vault”
This ensures vault isolation and prevents accidental cross-vault dependencies.

​
Sharing Skills

​
Within a Vault

All vault members automatically see skills in that vault. No additional sharing needed.

​
Across Vaults

To share a skill from one vault to another:
1

Clone to Personal Vault

better-skills clone skill-slug --to ./skill-copy
2

Create in Target Vault

Update the skill if needed, then create it in your personal or another enterprise vault where you have write access.
better-skills create --from ./skill-copy
Cloning creates an independent copy. Changes to the original skill do not affect the copy.

​
Managing Memberships

​
Viewing Memberships

List all vault memberships via CLI: 
better-skills config
This shows:
  • Vault name and slug
  • Your role (owner, admin, member)
  • Enabled status

​
Disabling Vaults

Disable a vault membership to hide it from active views: 
better-skills disable <vault-slug-or-id>
Behavior:
  • Vault skills remain visible in list, search, and sync
  • Disabled status is a user preference only
  • Does not remove the membership
  • Can be re-enabled through the web console
Disabling is reversible and does not affect other vault members.

​
Leaving a Vault

To leave an enterprise vault:
  1. Navigate to vault settings in the web console
  2. Click Leave Vault
  3. Confirm removal
Owners cannot leave until transferring ownership or deleting the vault.

​
Use Cases

​
Team Skill Library

Create an enterprise vault for shared coding standards:
  1. Owner creates “engineering-standards” enterprise vault
  2. Admins add skills for code review guidelines, API patterns, testing workflows
  3. Members invited as “member” role for read-only access
  4. Engineers use skills across projects

​
Department-Specific Knowledge

Organize skills by department:
  • marketing-vault: Brand guidelines, content templates, campaign workflows
  • sales-vault: Pitch decks, proposal templates, CRM workflows
  • support-vault: Troubleshooting guides, escalation procedures
Each vault has its own members and permissions.

​
Cross-Team Collaboration

Admins from different vaults collaborate:
  1. Frontend admin creates “react-patterns” skill in “frontend-vault”
  2. Backend admin references it in “api-integration” skill in “backend-vault” (by cloning and adapting)
  3. Both teams benefit from shared patterns

​
Next Steps

Creating Skills

Learn how to create skills in your vaults

Backup & Restore

Back up local skills before syncing to vaults

Build docs developers (and LLMs) love

Get started for freeTalk to us