Browse Platform

PlatformProjectSkills

Platform · Project

Skills

Create and manage reusable Skill Collections for workspace agents, including their source, discovery, sharing, contributions, downloads, and sync state.

9 min read

Skills give agents reusable instructions for specialized work. A Skill can describe a review method, a repeatable business process, or how to use supporting files and scripts. Related Skills live together in a Skill Collection.

Use the links below to jump directly to a task:

Create a Skill Collection
Review every collection setting
Choose a source
Browse and sync a collection
View or download a Skill
Create and improve Skills in a Workspace

How Skills work

BotDojo repo • existing repo • external Git repo
                        ↓
                Skill Collection
       source • discovery • sharing • contributions
                        ↓
        Skill folders containing SKILL.md files
                        ↓
              Users and workspace agents

A Skill is a folder whose SKILL.md file gives the agent a name, description, and instructions. The folder can also contain examples, reference material, scripts, or other supporting files.
A Skill Collection is the repository-backed group that contains related Skills. The collection controls where those Skills come from, who can discover them, and whether permitted agents can publish improvements.
A Workspace is where users and agents apply, create, and improve Skills beside the work that needs them.

The Skill name and description help an agent decide when the Skill applies. Write them for discovery: identify the task, expected result, and important boundary. Put the complete procedure in SKILL.md.

Open Skills

In a project, select Skills under Context. BotDojo opens the Skill Collections list.

The light-mode Skill Collections page with Documentation Playbooks and my-skills collections

The list summarizes each collection:

Column	What it shows
Name	The collection label shown to project administrators and in workspace Skill browsers.
Slug	The collection's stable folder name and URI path.
Skills	The number of Skills found during the most recent successful repository sync.
Source	BotDojo for a BotDojo-managed repository, External for an external Git repository, or Account for a collection shared into the project.
Access	Direct contributions when permitted agents can publish edits, or Read-only when they can only use the approved Skills.
Sync	The current repository state: `never`, `syncing`, `ready`, or `error`.
Updated	When the collection record was last changed.

Select a row to open the collection. Use the table controls to search, refresh, choose columns, change density, or enter full screen.

Create a Skill Collection

Select New Collection from the Skill Collections page.

The New Skill Collection modal with Name, Description, Folder name, and Enabled by default

Enter a clear Name and a discovery-oriented Description.
Review the generated Folder name.
Choose whether the collection is Enabled by default.
Open Advanced settings to choose sharing, source, branch, and contribution behavior.
Select Create. BotDojo creates the collection, connects its repository, and starts the first sync.

Creating a collection does not create its individual Skills. Open a Workspace and ask the agent to create or publish Skills into the collection after setup.

Collection settings

The create and edit modals are organized around identity, discovery, source, and contributions.

Identity and discovery

Setting	What it does
Name	Sets the human-readable collection label. Users see it in the Skills list and Workspace Skill browser. Use a name that describes the team, workflow, or subject the collection supports.
Description	Tells users and agents what kinds of Skills the collection contains and when to search it. Do not place credentials or private setup notes here.
Folder name	Sets the collection slug used in its BotDojo URI and repository folder. New collections generate it from the Name. Use lowercase letters, numbers, and hyphens, and keep it stable after agents or instructions begin referring to the collection.
Enabled by default	When on, users and workspace agents with permission can discover and use the collection by default. When off, they must explicitly enable it. This changes discovery, not permission.

The folder name becomes part of the collection's stable BotDojo URI:

URI prefix	Scope
`botdojo://acme/skills/…/TOOLS.md`	An account-shared collection, using `acme` as the example account alias. Permitted users and agents can discover it from other account projects or personal workspaces.
`botdojo://project/skills/…/TOOLS.md`	A project-only collection available to permitted agents in this project's workspaces.
`botdojo://personal/skills/…/TOOLS.md`	A personal collection owned by a user and available to that user's personal workspaces.

The URI identifies the collection; it does not bypass access, discovery, or contribution controls.

Advanced settings

Advanced Skill Collection settings for account sharing, BotDojo repository source, default branch, and agent contributions

Setting	What it does
Share with this account	Makes a project collection eligible for discovery from other projects and personal workspaces in the same account. When off, only this project's permitted agents can use it. Personal-project collections cannot be account-shared.
Source Type	Chooses the repository that stores the collection. This is selected when the collection is created.
Default Branch	Sets the repository branch BotDojo reads and updates. Use the branch that represents the approved version of the collection.
Allow agents to contribute	Lets agents with permission publish Skill edits from Workspaces. When off, agents can read and use the collection but cannot publish changes to it.

Sharing makes a collection available for account-level assignment; it does not grant every user or agent access automatically. Account administrators can manage broader availability through Shared Skill Collections.

Source Type

Source	Choose it when
New BotDojo Repo	You are starting a new collection and want BotDojo to create and manage its repository.
Existing BotDojo Repo	A BotDojo repository already contains the collection files. Select the repository from Select Repo. An In use label means another collection already uses it, so confirm that reuse is intentional.
External Git URL	Your team maintains the approved Skills in an external Git repository. Enter the repository URL, an access token when the repository is private, and the branch BotDojo should sync.

For an external repository, leave Access Token blank for a public repository. When editing an existing private source, leave it blank to retain the stored token. Treat the token as a secret: never put it in the collection name, description, Skill content, screenshots, or agent instructions.

Edit or archive a collection

Open a collection and select Settings to change its name, description, folder name, discovery, sharing, branch, or contribution settings.

Save applies the edited settings.
Archive removes the collection from active use after confirmation. The backing repository is not archived.
Cancel or closing the modal leaves unsaved changes unapplied.

Before archiving, check Workspaces, agents, and instructions that refer to the collection URI.

Work with a collection

Select a collection row to see the Skills found in its source repository.

The Documentation Playbooks collection with three sample Skills and collection actions

The collection page shows each Skill's Name, Description, and Slug. Select a row or View to read its SKILL.md; select its Download action to prepare a Zip containing that Skill and its supporting files.

The page-level actions control the collection:

Action	What it does
Sync	Appears when the repository has newer changes or a sync is in progress. It reads the configured branch again and refreshes the collection's Skill records.
Download	Opens options to download the complete collection as a Zip or clone it with Git.
Settings	Opens the collection settings described above.

The Git clone option creates a temporary read token and a ready-to-copy clone command. Store the token only in an appropriate secret store and do not paste the command into documentation, screenshots, chat, or logs. The dialog shows when the temporary token expires.

Understand sync state

State	Meaning
`never`	BotDojo has not completed the first repository sync.
`syncing`	BotDojo is currently reading the configured branch.
`ready`	The most recent sync completed and the displayed Skill list reflects it.
`error`	BotDojo could not read or process the source. Check the repository URL, branch, access token, and Skill file format.

If BotDojo reports that the repository has newer changes, select Sync and review the resulting Skill list. A successful Git commit alone does not prove that BotDojo has indexed valid Skill metadata.

View and download a Skill

Select View beside a Skill to inspect the content BotDojo read from its source.

The individual Skill viewer showing its description, repository path, SKILL.md content, and Download Zip action

The viewer shows:

the Skill name and discovery description;
its path inside the collection repository;
the current SKILL.md content; and
Download Zip, which includes the Skill folder and supporting files.

Review the visible source before depending on a Skill for consequential work. If the description does not match the procedure, update both so agent discovery and execution stay aligned.

Manage Skills from a Workspace

Skill Collections are configured under Platform Skills, but individual Skills are created and improved in a Workspace. This keeps the instructions, supporting files, conversation, proposed changes, and test result together.

Open the Workspace where the Skill is needed.
Open Skills from the Workspace toolbar and choose the target collection.
Ask the agent to create or update a focused Skill and show the changed files.
Review the SKILL.md, supporting files, and a representative result.
Publish the change when the collection allows contributions. For a shared review flow, submit and follow the change request instead of bypassing the review.
Return to the Platform collection and confirm the Skill appears after sync.

See Build and Manage Skills for the complete Workspace workflow, including personal Skills, shared collections, change requests, and approvals.

Troubleshooting

The collection is missing in a Workspace — Check Enabled by default, account sharing or project scope, and the user's or agent's access.
An agent can use Skills but cannot publish changes — Confirm Allow agents to contribute and the agent's permission. Shared collections may require a change request and reviewer approval.
The Skill count is zero — Confirm the configured branch contains valid Skill folders with SKILL.md files, then wait for or start a sync.
Sync reports an error — Check the repository URL, default branch, credential, and the name and description metadata in each SKILL.md.
External changes do not appear — Open the collection, select Sync when offered, and confirm the sync returns to ready.
A folder-name conflict is reported — Choose a unique folder name. Two collections cannot use the same BotDojo URI in the same scope.