New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Official agent skill

Berd Help

by block in block/berd

Help with Berd the desktop app: how-to, troubleshooting, settings, agents, skills, automations, projects, sessions, providers, connections, feedback, or berdctl.

OfficialApache-2.0Auto-check passed

Install Berd Help

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

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

GitHub CLI
$ gh skill install block/berd berd-help --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-help .claude/skills/berd-help && 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-help
GitHub stars
969
Token cost
~1.4k tokens
SKILL.md length
731 words
Files
11 (incl. references)
Skills in repo
11
Repo updated
First seen
Licence
Apache-2.0

At a glance

Help with Berd the desktop app: how-to, troubleshooting, settings, agents, skills, automations, projects, sessions, providers, connections, feedback, or berdctl.

  • Not harness-specific behavior
  • SKILL.md covers First Principles, Scope, What To Check and Topics, plus 2 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Berd Help is an agent skill from block/berd, published by the product's own GitHub organization. Help with Berd the desktop app: how-to, troubleshooting, settings, agents, skills, automations, projects, sessions, providers, connections, feedback, or berdctl. Use for app questions, not harness-specific behavior.

Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 11 other files, including reference files (for example `references/agents.md`, `references/ai-providers.md` and `references/automations.md`).

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

  • Not harness-specific behavior

Example prompts

  • “/berd-help”

What it can do on your machine

Read from SKILL.md and the folder at commit 5bcf29b. 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 Help loads about 1.4k tokens when it runs, and up to ~4.9k if it reads all its reference files. Until then it costs about 56 tokens; SKILL.md has 731 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~56
When it runs · the whole SKILL.md, loaded when a task matches
~1.4k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~4.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 block/berd at commit 5bcf29b, republished under its Apache-2.0 licence (© block). 731 words, ~1,359 tokens.

Download SKILL.mdSave it as .claude/skills/berd-help/SKILL.md (or your agent's skills folder). This skill also uses 10 other files; get the full folder from GitHub.
name
berd-help
description
Help with Berd the desktop app: how-to, troubleshooting, settings, agents, skills, automations, projects, sessions, providers, connections, feedback, or berdctl. Use for app questions, not harness-specific behavior.
metadata.berdBundled
true

Berd help

Use this skill to help users operate, troubleshoot, and script Berd — the desktop app — from a normal chat. Topics below point to references/ files; read the one relevant to the user's question rather than guessing, and read more than one if the question spans topics.

First Principles

  • Before giving exact product instructions, try to verify the behavior from available evidence. If source code is available, inspect it first. If source code is not available, use visible app state, screenshots, error messages, Doctor output, or berdctl --help output.
  • Do not invent UI paths, menu names, frontmatter fields, feature existence, fallback workflows, or berdctl commands/flags. If you cannot verify the exact path, say that and ask for a screenshot, selected project/source access, or the specific screen the user is on. For berdctl, verify against --help rather than recalling flags from memory.
  • Treat the current app behavior as the source of truth. Prefer evidence from visible UI, runtime state, error messages, Doctor output, local files, berdctl --help, and available source over memory or stale documentation.
  • Give practical steps the user can try now. Keep the answer short unless the problem needs a deeper diagnosis.
  • Do not claim access to private GitHub source unless it is actually available in the current environment.
  • Berd changes fast. Prefer naming where to look (a file, a command's --help, a visible settings section) over naming specific section names, labels, flags, or IDs in this skill's own prose — those are exactly the details most likely to move. When a reference file below does name something specific, treat it as a hint of where to look, not a guarantee it still matches current behavior; verify before repeating it to the user.

Scope

This skill is about Berd the app — not about any one harness running inside a session (goose, claude-acp, codex-acp, copilot-acp, amp-acp, cursor-agent). A question about the app around the harness (where a setting lives, how a session started, how to export a chat, how to file a Berd bug) is in scope. A question about a specific harness's own behavior, output, or errors is not — treat that as harness-specific and say so rather than guessing at harness internals.

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

What To Check

For how-to questions:

  • Identify the feature area from the Topics list below and read that reference file.
  • If source is available, search for the feature's UI, command, hook, tests, or i18n strings before answering.
  • Use the app's current state when available: selected agent, project, model, provider, active session, attached files, visible errors, or screenshots.
  • Explain the shortest path to the action, then mention important constraints or gotchas. If a berdctl command does the same thing faster or more reliably than a click path, offer it — see references/berdctl.md.

For troubleshooting:

  • Ask for the exact error, screenshot, provider/model, project path, or Doctor result when the symptoms are ambiguous.
  • Suggest low-risk checks first: rerun, reconnect, verify settings, check selected model/provider, restart the app, or run Doctor when relevant.
  • Separate likely causes from confirmed causes.
  • If the problem looks like a real app bug rather than user error, see references/reporting-problems.md instead of guessing at a fix.

Topics

Read the matching reference file for a specific question. Read more than one when a question spans topics (for example, an automation failure that might be a provider problem needs both):

  • references/berdctl.md — the berdctl CLI, when to prefer it over UI steps
  • references/agents.md — agents/personas
  • references/skills.md — skills, source kinds, precedence
  • references/automations.md — automations
  • references/projects.md — projects and workspaces
  • references/sessions.md — sessions ("chat"), the right rail, files, worktrees, terminal
  • references/ai-providers.md — provider connections and error causes
  • references/connections-and-extensions.md — connections vs. extensions
  • references/settings.md — settings structure and gotchas
  • references/reporting-problems.md — filing feedback or a bug

Working With Bundled Builder Skills

  • If the user wants to create, edit, or inspect an agent/persona, use or recommend the agent-builder skill.
  • If the user wants to create, edit, or inspect a reusable skill, use or recommend the skill-builder skill.
  • Do not duplicate those workflows inside this skill or its references. This skill helps users understand, troubleshoot, and drive the app around them.

Source Of Truth

When source code is available, use it to verify behavior — the reference files above may lag actual behavior since Berd changes fast. Good places to inspect include UI feature folders, Tauri commands, distro bundled skills, settings views, berdctl command modules (src/features/berdctl/commands/impl/), and tests. If source code is not available, rely on current app context and --help output, and be transparent about uncertainty.

© 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

SKILL.md and 10 other files (references) in distro/skills/berd-help of block/berd.

  • SKILL.md
  • references/agents.md
  • references/ai-providers.md
  • references/automations.md
  • references/berdctl.md
  • references/connections-and-extensions.md
  • references/projects.md
  • references/reporting-problems.md
  • references/sessions.md
  • references/settings.md
  • references/skills.md

Open the folder on GitHubat commit 5bcf29b

Compare with similar skills

Berd Help 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 Help compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Berd Help this skillblock/berd969—~1.4kAutomated safety check: PassApache-2.0
Manage Settingsasgeirtj/system_prompts_leaks69k—~3.1kAutomated safety check: PassCC0-1.0
Warp Settings Editorwarpdotdev/warp65k1 repos~675Automated safety check: PassAGPL-3.0
Startup It Troubleshootingsickn33/agentic-awesome-skills47k2 repos~3.6kAutomated safety check: NotesMIT
Warp Settings Page Builderwarpdotdev/warp65k1 repos~4.5kAutomated safety check: PassAGPL-3.0
Setting Up DevboxPostHog/posthog40k—~2.6kAutomated safety check: NotesCustom licence

Similar skills

  • Manage Settings

    asgeirtj/system_prompts_leaks

    Any explicit Muse Code setting question or change (model, reasoning effort, /settings) requires a silent readskill call for bundled:manage-settings as FIRST ACTION—no assistant text or other tool…

    69k GitHub stars~3.1k tokensUpdated today
    Auto-check passed

  • Warp Settings Editor

    warpdotdev/warp

    Finds and changes Warp application settings by searching a bundled JSON schema and editing the matching TOML settings file at the right nesting depth.

    65k GitHub starsUsed in 1 repo~675 tokens
    Productivity & AutomationAuto-check passed

  • Startup It Troubleshooting

    sickn33/agentic-awesome-skills

    Practical IT troubleshooting playbooks for small teams without dedicated IT staff.

    47k GitHub starsUsed in 2 repos~3.6k tokens
    Auto-check: notes

  • Warp Settings Page Builder

    warpdotdev/warp

    How to build a settings page in the Warp desktop client so widgets, page titles and settings search behave correctly, and which common mistakes to avoid.

    65k GitHub starsUsed in 1 repo~4.5k tokens
    Frontend & DesignAuto-check passed

  • Setting Up Devbox

    PostHog/posthog

    Official

    Starts, connects to, and troubleshoots a PostHog devbox, a remote Coder workspace for PostHog development that can also run the full stack, through hogli devbox: commands.

    40k GitHub stars~2.6k tokensUpdated today
    Auto-check: notes

  • Add Server Env Var for User Setting

    lobehub/lobehub

    Adds a server-side environment variable that sets the default for a user setting in LobeHub, wired from the env schema through server config to the user store and docs.

    83k GitHub stars~644 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

  • Experimental Features

    block/berd

    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 Help

What does Berd Help do?

Help with Berd the desktop app: how-to, troubleshooting, settings, agents, skills, automations, projects, sessions, providers, connections, feedback, or berdctl. Berd Help is an agent skill from block/berd, published by the product's own GitHub organization. Help with Berd the desktop app: how-to, troubleshooting, settings, agents, skills, automations, projects, sessions, providers, connections, feedback, or berdctl.

When should I use Berd Help?

Berd Help fits situations like: not harness-specific behavior.

How do I install Berd Help in Claude Code?

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

How do I install Berd Help in Codex?

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

Can I use Berd Help 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-help -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-help, .gemini/skills/berd-help, .github/skills/berd-help and .opencode/skills/berd-help in your project.

What does Berd Help need to run?

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

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

Berd Help 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 Help use?

About 1.4k tokens (SKILL.md is roughly 5.4k 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 3.5k tokens, read only when the agent opens those files.

What are the alternatives to Berd Help?

Skills that share tags, products or a category with Berd Help: Manage Settings (asgeirtj/system_prompts_leaks, 69k stars), Warp Settings Editor (warpdotdev/warp, 65k stars), Startup It Troubleshooting (sickn33/agentic-awesome-skills, 47k stars) and Warp Settings Page Builder (warpdotdev/warp, 65k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Berd Help?

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 7, 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.