Official agent skill

Berd Orchestrator

by block in block/berd

Coordinate work across Berd sessions while keeping one conversation available to the user.

OfficialApache-2.0Auto-check passed

Install Berd Orchestrator

skills CLI
$ npx skills add block/berd --skill berd-orchestrator -a claude-code

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

GitHub CLI
$ gh skill install block/berd berd-orchestrator --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/block/berd.git skills-src && mkdir -p .claude/skills && cp -r skills-src/distro/skills/berd-orchestrator .claude/skills/berd-orchestrator && 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
berd-orchestrator
GitHub stars
969
Token cost
~277 tokens
SKILL.md length
136 words
Files
1
Skills in repo
11
Repo updated
First seen
Licence
Apache-2.0

At a glance

Coordinate work across Berd sessions while keeping one conversation available to the user.

  • A long-lived orchestration session
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Berd Orchestrator is an agent skill from block/berd, published by the product's own GitHub organization. Coordinate work across Berd sessions while keeping one conversation available to the user. Use for a long-lived orchestration session.

Its SKILL.md is about 280 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

The repository describes itself as: a desktop app for getting work done with any model. The licence is Apache-2.0.

When your agent uses it

  • A long-lived orchestration session

Example prompts

  • “/berd-orchestrator”

What it can do on your machine

Read from SKILL.md and the folder at commit bbdb311. 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.

    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

Berd Orchestrator loads about 277 tokens when it runs. Until then it costs about 38 tokens; SKILL.md has 136 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~38
When it runs · the whole SKILL.md, loaded when a task matches
~277

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 block/berd at commit bbdb311, republished under its Apache-2.0 licence (© block). 136 words, ~277 tokens.

Download SKILL.mdSave it as .claude/skills/berd-orchestrator/SKILL.md (or your agent's skills folder).
name
berd-orchestrator
description
Coordinate work across Berd sessions while keeping one conversation available to the user. Use for a long-lived orchestration session.
metadata.berdBundled
true

Berd Orchestrator

Keep this session available for conversation. Use berdctl session list, get, create, and send to delegate substantial work to other sessions instead of doing it here.

Prefer an existing session that owns the relevant context. Create one when work has no owner, and give it a complete task. Do not approve, merge, or archive work without the user's direction.

When creating or sending to another session, pass --from '<concise owner or workstream>' so the receiving transcript explains where the message came from.

Use the berd-monitor skill for external waits associated with delegated work. End the turn after starting a monitor; do not poll in the foreground.

Stay quiet while work is progressing. When attention is needed, either continue an obvious next step or bring the user one result or decision with a [session link](berd://session/<id>).

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

Files

Just SKILL.md in distro/skills/berd-orchestrator of block/berd.

Open the folder on GitHubat commit bbdb311

Compare with similar skills

Berd Orchestrator 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.

Berd Orchestrator compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Berd Orchestrator this skillblock/berd969—~277Automated safety check: PassApache-2.0
Orchestratesickn33/agentic-awesome-skills47k1 repos~692Automated safety check: PassMIT
Session Handoffsickn33/agentic-awesome-skills47k—~1.8kAutomated safety check: NotesMIT
Team Agent Orchestrationaffaan-m/ECC274k1 repos~1.2kAutomated safety check: PassMIT
Orca Orchestrationstablyai/orca87k—~916Automated safety check: PassMIT
Agent Orchestrator Taskruvnet/ruflo74k3 repos~1kAutomated safety check: PassMIT

Similar skills

  • Orchestrate

    sickn33/agentic-awesome-skills

    Coordinate focused subagents on substantial work, keep their ownership non-overlapping, and integrate verified results.

    47k GitHub starsUsed in 1 repo~692 tokens
    Agent WorkflowsAuto-check passed
  • Session Handoff

    sickn33/agentic-awesome-skills

    A skill your agent uses when context approaches capacity, before /clear or /compact, when switching tasks, or when ending a coding session: produces a structured handoff artifact for the next session.

    47k GitHub stars~1.8k tokensUpdated yesterday
    Agent WorkflowsAuto-check: notes
  • Run team-based orchestration for agent squads: work items with owners and scope, agent Kanban state, branch isolation, control pane visibility, and merge gates.

    274k GitHub starsUsed in 1 repo~1.2k tokens
    Productivity & AutomationAuto-check passed
  • Orca Orchestration

    stablyai/orca

    Coordinate supervised Orca workers: threaded messages, blocking ask/reply, task dispatch, worker_done/escalation waits, task DAGs, decision gates, coordinator…

    87k GitHub stars~916 tokensUpdated today
    Agent WorkflowsAuto-check passed
  • Agent skill for orchestrator-task - invoke with $agent-orchestrator-task

    74k GitHub starsUsed in 3 repos~1k tokens
    Agent WorkflowsAuto-check passed
  • Multi-agent swarm coordination for complex tasks. An agent skill from ruvnet/ruflo.

    74k GitHub stars~261 tokensUpdated today
    DevelopmentAuto-check passed

More from block/berd

All 11 skills in this repo
  • Agent Builder

    block/berd

    Official

    Create, edit, or inspect Berd agents/personas stored as Agent Markdown files with YAML frontmatter under ~/.agents/agents.

    969 GitHub stars~644 tokensUpdated today
    Auto-check passed
  • Assistive UX

    block/berd

    Official

    A skill your agent uses when adding, reviewing, designing, testing, or managing Assistive UX moments in Berd, including discover, suggest, and autoApply guidance, adaptive settings, behavior…

    969 GitHub stars~706 tokensUpdated today
    Auto-check passed
  • Buzz Handoff

    block/berd

    Official

    Read and hand off Buzz channels or threads in a private agent conversation using the installed Buzz CLI.

    969 GitHub stars~893 tokensUpdated today
    Auto-check passed
  • Create PR

    block/berd

    Official

    Create a GitHub PR from the current branch: handle uncommitted changes, generate a summary, submit via gh CLI, then watch the PR to a ready state — fixing failing checks and addressing review…

    969 GitHub stars~2.6k tokensUpdated today
    Auto-check passed
  • Official

    A skill your agent uses when adding, reviewing, configuring, graduating, or removing Berd experiments.

    969 GitHub stars~1.5k tokensUpdated today
    Auto-check passed
  • Skill Builder

    block/berd

    Official

    Create, edit, or inspect Berd skills stored as skill folders with SKILL.md files.

    969 GitHub stars~1.2k tokensUpdated today
    Auto-check passed

Questions about Berd Orchestrator

What does Berd Orchestrator do?

Coordinate work across Berd sessions while keeping one conversation available to the user. Berd Orchestrator is an agent skill from block/berd, published by the product's own GitHub organization. Coordinate work across Berd sessions while keeping one conversation available to the user.

When should I use Berd Orchestrator?

Berd Orchestrator fits situations like: A long-lived orchestration session.

How do I install Berd Orchestrator in Claude Code?

Run `npx skills add block/berd --skill berd-orchestrator -a claude-code`. Or copy the skill folder (distro/skills/berd-orchestrator in block/berd) into .claude/skills/berd-orchestrator in your project. Claude Code loads it when a task matches its description.

How do I install Berd Orchestrator in Codex?

Run `npx skills add block/berd --skill berd-orchestrator -a codex`. Or copy the skill folder (distro/skills/berd-orchestrator in block/berd) into .agents/skills/berd-orchestrator in your project. Codex loads it when a task matches its description.

Can I use Berd Orchestrator 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 block/berd --skill berd-orchestrator -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/berd-orchestrator, .gemini/skills/berd-orchestrator, .github/skills/berd-orchestrator and .opencode/skills/berd-orchestrator in your project.

What does Berd Orchestrator need to run?

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

Does Berd Orchestrator 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 Berd Orchestrator 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 Berd Orchestrator use?

Berd Orchestrator is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Berd Orchestrator use?

About 277 tokens (SKILL.md is roughly 1.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Berd Orchestrator?

Skills that share tags, products or a category with Berd Orchestrator: Orchestrate (sickn33/agentic-awesome-skills, 47k stars), Session Handoff (sickn33/agentic-awesome-skills, 47k stars), Team Agent Orchestration (affaan-m/ECC, 274k stars) and Orca Orchestration (stablyai/orca, 87k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Berd Orchestrator?

block (a GitHub organization, an official publisher) maintains it in block/berd, which has 969 GitHub stars. The repository holds 11 skills in this directory. The repository was last updated on October 6, 2026.

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