BotDojoDocs
Search BotDojo Docs
Search every guide

Try “stop a run,” “connect an app,” or “daily briefing.”

Browse Platform
PlatformAccountShared Skill Collections
Platform · Account

Shared Skill Collections

Create shared skill collections, choose a source, allow contributions, and review proposed team changes.

2 min readLast reviewed July 27, 2026

#Create a shared skill collection

A shared collection keeps related team playbooks together under one managed source.
Screenshot previewA shared collection keeps related team playbooks together under one managed source.
Shared Acme Sales Playbooks collection with several sales skills
  1. 01

    Open account Skills

    Choose Skills from account navigation.

  2. 02

    Choose New Skill Collection

    Select the project that will own the collection.

  3. 03

    Name and describe it

    Make the intended team and type of work clear.

  4. 04

    Share with this account

    Enable account sharing when other projects and groups should be able to use it.

#Choose a source

Choose a new or existing BotDojo repo when BotDojo should maintain the collection source.
Screenshot previewChoose a new or existing BotDojo repo when BotDojo should maintain the collection source.
Shared skill collection setup showing BotDojo repository source choices
SourceChoose it when
New BotDojo RepoYou are starting a new collection managed in BotDojo.
Existing BotDojo RepoA BotDojo repo already contains the skills.
External Git URLYour team maintains the approved collection in an external Git repository.

#Configure an External Git URL

Enter the remote URL and branch, provide access when needed, and test the connection before depending on it.
Screenshot previewEnter the remote URL and branch, provide access when needed, and test the connection before depending on it.
Shared skill settings showing an external Git URL, branch, token, and Test action

#Configure sharing and contributions

Enable Allow agents to contribute when permitted workspace agents should be able to publish proposed edits. Leave it off for a read-only collection. Group policy still determines who receives the shared collection.

Share the collection, choose its approved branch, and decide whether agents may contribute proposed edits.
Screenshot previewShare the collection, choose its approved branch, and decide whether agents may contribute proposed edits.
Advanced shared skill settings for account sharing, default branch, and agent contributions

#Review and Approve Changes

The Skill Collections list shows how many change requests are open for each collection. Select the open count, or open a collection and choose Change Requests, to review them there. Approve Changes merges the request without leaving the page. If it conflicts with newer changes, nothing is merged, and Fix in Chat opens a workspace in the same project where an agent resolves the conflict; then approve again.

Inspect the requested file changes and their reason before choosing Approve Changes.
Screenshot previewInspect the requested file changes and their reason before choosing Approve Changes.
Administrator confirmation dialog for approving a shared skill change request
  • Confirm the request targets the correct collection and branch.
  • Read the changed skill files rather than approving from the summary alone.
  • Reject or request revision when the guidance is unsupported or too broad.
  • Verify the approved behavior with a representative workspace request.

#Confirm the approved result

The approved request updates the collection’s reviewed version for future use.
Screenshot previewThe approved request updates the collection’s reviewed version for future use.
Shared skill change request showing its approved status and completed update
Personal and Shared ResourcesUnderstand ownership, account sharing, group assignment, user defaults, and Workspace overrides before granting access.Build and Manage SkillsOpen Skills in a workspace, use or improve My Skills and shared collections, and review change requests from the same working context.