Agent skill

Workflows

by get-bb in get-bb/bb

Author or run durable BB workflows when the user requests workflow execution or multi-agent orchestration.

MITAuto-check passedAgent Workflows

Install Workflows

skills CLI
$ npx skills add get-bb/bb --skill workflows -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install get-bb/bb workflows --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/get-bb/bb.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/workflows/skills/workflows .claude/skills/workflows && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
workflows
GitHub stars
4.2k
Token cost
~890 tokens
SKILL.md length
388 words
Files
4 (incl. references)
Skills in repo
33
Repo updated
First seen
Licence
MIT

At a glance

Author or run durable BB workflows when the user requests workflow execution or multi-agent orchestration.

  • Works in 7 steps: Inspect the task and repository before… → Confirm the provider, model, and… → Write the smallest workflow that gives… → …
  • Requests workflow execution
  • SKILL.md covers Start safely, Read only the required detail, Minimal source and Execute, plus 1 more section
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Workflows is an agent skill from get-bb/bb. Author or run durable BB workflows when the user requests workflow execution or multi-agent orchestration.

Its SKILL.md is about 890 tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including reference files (for example `references/authoring.md`, `references/orchestration.md` and `references/runs.md`).

It sits in Agent Workflows, covering Multi-agent orchestration. The repository describes itself as: The agent IDE that builds itself. The licence is MIT.

When your agent uses it

  • Requests workflow execution
  • Multi-agent orchestration

Example prompts

  • “/workflows”

Workflow steps

7 steps, taken from the first numbered list in SKILL.md.

  1. Inspect the task and repository before you choose the work list.
  2. Confirm the provider, model, and reasoning tuple from the live catalog.
  3. Write the smallest workflow that gives the requested coverage.
  4. Validate the exact source before execution.
  5. Start the background run.
  6. Emit the returned workflow preview directive exactly once.
  7. Use compact status for progress and paged history for details.

What it can do on your machine

Read from SKILL.md and the folder at commit 68a1e8b. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are bash and javascript).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Workflows loads about 890 tokens when it runs, and up to ~5.9k if it reads all its reference files. Until then it costs about 29 tokens; SKILL.md has 388 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~29
When it runs · the whole SKILL.md, loaded when a task matches
~890
With references · SKILL.md plus every file in references/, read only if the agent opens them
~5.9k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from get-bb/bb at commit 68a1e8b, republished under its MIT licence (© get-bb). 388 words, ~890 tokens.

Download SKILL.mdSave it as .claude/skills/workflows/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.
name
workflows
description
Author or run durable BB workflows when the user requests workflow execution or multi-agent orchestration.

BB workflows

Use a workflow when the user explicitly asks for multi-agent orchestration. Ordinary tasks do not authorize a workflow run.

A workflow puts deterministic control flow around normal BB worker threads. The script can fan out work, pipeline stages, verify results, and return structured data. Worker threads retain normal workspace tools and permissions.

Start safely

  1. Inspect the task and repository before you choose the work list.
  2. Confirm the provider, model, and reasoning tuple from the live catalog.
  3. Write the smallest workflow that gives the requested coverage.
  4. Validate the exact source before execution.
  5. Start the background run.
  6. Emit the returned workflow preview directive exactly once.
  7. Use compact status for progress and paged history for details.

Check an explicit model selection with:

sh
bb provider list --environment "$BB_ENVIRONMENT_ID" --json
bb provider models <provider-id> --environment "$BB_ENVIRONMENT_ID" --json

Do not guess model identifiers or partial selection tuples.

Read only the required detail

  • Read references/authoring.md when you write or change workflow source, schemas, agent options, or nested workflows.
  • Read references/orchestration.md when you design pipelines, barriers, verification, panels, loops, or other quality controls.
  • Read references/runs.md when you validate, start, inspect, stop, or resume a workflow.

Minimal source

Every script starts with a literal meta object:

js
export const meta = {
  name: "review-change",
  description: "Review a change and verify the findings",
  phases: [{ title: "Review" }, { title: "Verify" }],
};
const results = await pipeline(
  args.items,
  (item) => agent("Review " + item, { phase: "Review" }),
  (review, item) =>
    agent("Verify this review for " + item + ":\n" + review, {
      phase: "Verify",
    }),
);
return results;

Workflow source is JavaScript, not TypeScript. The script has no filesystem, shell, network, import, clock, or random access. Worker agents can use their normal tools.

Use pipeline for independent multi-stage items. Use a parallel barrier only when the next stage needs all prior results.

Use an agent schema when later stages need reliable structured data. A structured worker must return its value through the workflow result tool.

Show full SKILL.md (128 more words)Show less

Execute

Validate and run with the same source selector:

sh
bb workflows validate --file .bb/workflows/review-change.js
bb workflows run --file .bb/workflows/review-change.js --args '{"items":[]}'

The agent tool accepts script, scriptPath, or name. The CLI accepts --script, --file, or --name.

After a successful agent-tool call, copy its previewDirective into the assistant response as one standalone line. Do not edit or repeat it.

Use bb workflows status for compact progress. Redirect bounded history pages into BB_THREAD_STORAGE before inspection because history can contain full prompts and results.

Quality check

  • The user explicitly requested workflow orchestration.
  • The source passes bb workflows validate.
  • Every explicit provider tuple exists in the live catalog.
  • Each phase name matches its meta entry.
  • Independent items use pipeline without an unnecessary barrier.
  • Bounded coverage logs what it omits.
  • Structured consumers receive schema-validated results.
  • The final response uses status or inspected history, not assumptions.

© get-bb, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 3 other files (references) in plugins/workflows/skills/workflows of get-bb/bb.

  • SKILL.md
  • references/authoring.md
  • references/orchestration.md
  • references/runs.md

Open the folder on GitHubat commit 68a1e8b

Compare with similar skills

Workflows next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Workflows compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Workflows this skillget-bb/bb4.2k—~890Automated safety check: PassMIT
Orca CLIstablyai/orca87k2 repos~593Automated safety check: PassMIT
Paseo Advisor Second Opiniongetpaseo/paseo20k1 repos~756Automated safety check: PassCustom licence
O2 Review Loopopenobserve/openobserve22k—~3.7kAutomated safety check: PassAGPL-3.0
Paseo Committeegetpaseo/paseo20k1 repos~496Automated safety check: PassCustom licence
Mission Control Agent APIbuilderz-labs/mission-control6.3k—~2.1kAutomated safety check: PassMIT

Similar skills

  • Orca CLI

    stablyai/orca

    Operate Orca-managed worktrees, folder contexts, terminals, repos, automations, artifacts, skill sharing, worktree comments, and Orca's embedded browser…

    87k GitHub starsUsed in 2 repos~593 tokens
    Agent WorkflowsAuto-check passed
  • Launches one separate agent through Paseo to give a second opinion on the current task, with a self-contained briefing and no permission to edit files.

    20k GitHub starsUsed in 1 repo~756 tokens
    Agent WorkflowsAuto-check passed
  • O2 Review Loop

    openobserve/openobserve

    Splits a change into planner, coder and independent reviewer roles: you confirm a spec, a subagent implements it, and a separate reviewer checks each round's local WIP commit.

    22k GitHub stars~3.7k tokensUpdated today
    Agent WorkflowsAuto-check passed
  • Paseo Committee

    getpaseo/paseo

    Forms a two-agent committee with contrasting profiles to analyze a stuck problem in parallel, reconcile their views and return a consensus plan without editing files.

    20k GitHub starsUsed in 1 repo~496 tokens
    Agent WorkflowsAuto-check passed
  • Mission Control Agent API

    builderz-labs/mission-control

    Teaches an agent to use the Mission Control dashboard API: register, send heartbeats, fetch assigned tasks, report progress and disconnect, with API key auth.

    6.3k GitHub stars~2.1k tokensUpdated 9 days ago
    Agent WorkflowsAuto-check passed
  • Paseo Agent Handoff

    getpaseo/paseo

    Hands off the current task, including context, decisions and failed attempts, to a fresh agent through Paseo by writing a self-contained briefing prompt and launching that agent.

    20k GitHub starsUsed in 1 repo~606 tokens
    Agent WorkflowsAuto-check passed

More from get-bb/bb

All 33 skills in this repo
  • Bb CLI

    get-bb/bb

    Inspect or manage BB state with the bb CLI; use for BB commands and configuration.

    4.2k GitHub stars~3.4k tokensUpdated today
    Auto-check passed
  • Skill Creator

    get-bb/bb

    Create or improve BB skills, including their triggers, instructions, and supporting resources.

    4.2k GitHub stars~702 tokensUpdated today
    Auto-check passed
  • Prepare and submit a BB plugin to the Community marketplace when publication or a marketplace PR is requested.

    4.2k GitHub stars~873 tokensUpdated today
    Auto-check passed
  • Verify Bb

    get-bb/bb

    Verify BB user journeys in an isolated source dev app using dev-browser@next and the matching source CLI.

    4.2k GitHub stars~3.2k tokensUpdated today
    Auto-check passed
  • Create or edit BB color themes and inspect them in the Theme Preview panel.

    4.2k GitHub stars~1.2k tokensUpdated today
    Auto-check passed
  • Tasks

    get-bb/bb

    Work on or manage records in BB Tasks, including task keys such as ABC-12.

    4.2k GitHub stars~1.4k tokensUpdated today
    Auto-check passed

Categories

Questions about Workflows

What does Workflows do?

Author or run durable BB workflows when the user requests workflow execution or multi-agent orchestration. Workflows is an agent skill from get-bb/bb. Author or run durable BB workflows when the user requests workflow execution or multi-agent orchestration.

When should I use Workflows?

Workflows fits situations like: requests workflow execution; multi-agent orchestration.

How do I install Workflows in Claude Code?

Run `npx skills add get-bb/bb --skill workflows -a claude-code`. Or copy the skill folder (plugins/workflows/skills/workflows in get-bb/bb) into .claude/skills/workflows in your project. Claude Code loads it when a task matches its description.

How do I install Workflows in Codex?

Run `npx skills add get-bb/bb --skill workflows -a codex`. Or copy the skill folder (plugins/workflows/skills/workflows in get-bb/bb) into .agents/skills/workflows in your project. Codex loads it when a task matches its description.

Can I use Workflows in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add get-bb/bb --skill workflows -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/workflows, .gemini/skills/workflows, .github/skills/workflows and .opencode/skills/workflows in your project.

What does Workflows need to run?

SKILL.md names no scripts, command-line tools or credentials: Workflows is instructions for the agent only.

Does Workflows access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Workflows safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Workflows use?

Workflows is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Workflows use?

About 890 tokens (SKILL.md is roughly 3.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 5k tokens, read only when the agent opens those files.

What are the alternatives to Workflows?

Skills that share tags, products or a category with Workflows: Orca CLI (stablyai/orca, 87k stars), Paseo Advisor Second Opinion (getpaseo/paseo, 20k stars), O2 Review Loop (openobserve/openobserve, 22k stars) and Paseo Committee (getpaseo/paseo, 20k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Workflows?

get-bb (a GitHub organization) maintains it in get-bb/bb, which has 4,155 GitHub stars. The repository holds 33 skills in this directory. The repository was last updated on October 7, 2026.

Source: get-bb/bb on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.