Skills

Skills teach Beyond Better how to do a particular kind of task your way: summarizing meeting notes in your team's format, reviewing a chapter for pacing, preparing a report from a spreadsheet. A skill is a short set of written instructions, sometimes with reference documents, templates, or small programs alongside.

Why Use Skills?

Without Skills

  • You explain the same format and steps at the start of each conversation
  • Results vary depending on how you phrased the request
  • Putting every procedure in your guidelines makes every conversation longer

With Skills

  • Write the procedure once, and BB follows it every time
  • Share skills across every project in your workspace
  • BB reads a skill only when the task calls for it, so you can install many without making conversations longer or more expensive

How BB Uses Skills

In every conversation, BB sees a short list of the skills available in your project: each skill's name and description. When your request matches one, BB loads that skill's full instructions and follows them. You don't need to ask, but you can name one if you want it: "use the meeting-notes skill".

When BB loads a skill, the conversation shows a skills tool call with the skill's name. If the skill comes with reference documents, BB opens them only when it needs them.

Skills That Come with BB

Every data source you connect brings its own skill with detailed instructions for working in it, for example filesystem for project files, google-drive or google-gmail for Google, and notion for Notion. BB loads these when it does more than simple reading in that data source. They're always available while the data source is connected, you don't install them, and they don't appear in the Skills lists described below.

Coming Soon

A library of general-purpose skills that ship with BB.

Workspace and Project Skills

You install each skill at one of two levels:

Workspace Skills

Available in every project in the workspace. Use these for skills you want everywhere.

Project Skills

Belong to one project. If a project skill has the same name as a workspace skill, the project skill is used in that project, so you can adapt a shared skill for one project.

Installing a Skill

Where to Install

  • Workspace skills: Settings > Workspace > Project Defaults > Skills tab.
  • Project skills: Settings > Projects > choose the project > Skills tab. From here you can install to the project or to the workspace.
  • In a conversation: ask BB, for example "install the skill at https://github.com/acme/skills/tree/main/meeting-notes".

Who can change workspace skills: only team leads and owners of the workspace's team (and organization owners and admins) can add, change, or remove workspace skills. Everyone else sees them read-only.

Install New Skill

The Install New Skill form in each Skills tab offers three ways to add a skill:

  • URL / Path: paste a GitHub address (the full https://github.com/... address of the repository, or of the folder that holds the skill), a direct link to a SKILL.md file, or a folder path on the computer running BB.
  • File Browser: pick a skill folder, a SKILL.md file, or a .zip of a skill on the computer running BB.
  • Upload: upload a SKILL.md file or a .zip of a skill folder from your own computer. The .zip must have SKILL.md at the top level or inside one top-level folder.

Tip: A direct link to SKILL.md installs only the instructions, not any reference files or programs next to it. Use the GitHub address to get the whole skill. Installing a skill with the same name again, at the same level, replaces it with the new version.

Only Install Skills You Trust

A skill tells BB how to behave, and skills with programs can run them on any data source that allows running commands. Read a skill before you install it, just as you would a script from the internet.

Seeing, Editing, and Removing Skills

  • In a conversation: open Skills in the conversation header to see the skills installed for the project. You can read each one, copy it, edit its description and instructions, or delete it.
  • In Settings: the Skills tabs show where each skill came from and let you remove it. In a project's Skills tab, workspace skills are shown read-only; remove them from the workspace Skills tab.
  • By asking BB: for example "add a step to the meeting-notes skill to list open questions". BB can edit the instructions of skills you installed, but not the data source skills that come with BB.

Want BB to ask first? Turn on Require approval for changes in the project's Tools tab (with Allow questions and approval requests left on, as it is by default), and BB asks before it installs or removes a skill in a conversation. With approval for changes off, the default, BB does it when asked. See Questions & Approvals.

Skills with Programs

Some skills include small programs, for example to read or create Word documents. When BB loads such a skill, it copies the programs to a data source that can run commands, such as a local folder data source with command running allowed, or a Deno Deploy sandbox. It installs anything the skill says it needs, then runs the programs there as part of the task.

  • If none of your data sources can run commands, BB still follows the skill's written instructions, and tells you it can't run the programs.
  • If more than one data source can run commands, choose which one BB uses in the data source's settings under Execute Routing.

Writing Your Own Skill

A skill is a folder with a file called SKILL.md. The file starts with a short header, then the instructions written for BB:

---
name: meeting-notes
description: Turns rough meeting notes into a summary with decisions,
  action items and owners. Use when the user shares meeting notes or
  asks for a meeting summary.
---

# Meeting notes

1. Read the notes and list who attended.
2. Summarize the discussion in five bullet points or fewer.
3. List each decision on its own line.
4. List action items as a table with owner and due date. If an owner
   or date is missing, write "not given".
5. Save the summary next to the notes, with "-summary" added to the
   file name.

Use the house style in references/style.md.

The Header

  • name: lowercase letters, numbers, and hyphens only, up to 64 characters.
  • description: what the skill does and when to use it, up to 1024 characters. This is all BB sees until it loads the skill, so make it specific.

Optional Folders

  • references/ for longer documents, such as a style guide. Mention them by path in the instructions.
  • assets/ for templates and examples.
  • scripts/ for programs BB can run.

Anything else in the folder is not installed.

Writing Good Instructions

  • Write them as you would brief a capable colleague: the steps, the format you want, and the mistakes to avoid.
  • Keep the description short and specific. Every installed skill's description is part of every turn.
  • To try a skill out, install it as a project skill, start a new conversation, and give BB a task the skill is for. To improve it, edit it from the Skills panel or ask BB to change it.

Skills follow the open Agent Skills format, so skills written for other tools in that format can usually be installed in BB as they are.

Tips and Current Limits

  • If BB doesn't seem to know about a skill you just installed, ask it to load the skill by name. The list BB sees may not include brand-new skills straight away.
  • Removing a workspace skill removes it from every project in the workspace.
  • Settings has no switch yet for turning an installed skill off without removing it.

Next Steps

Last updated: November 13, 2026