메뉴
Read and hand off Buzz channels or threads in a private agent conversation using the installed Buzz CLI. Use when a user shares a buzz://message URL or Buzz channel UUID, asks to continue Buzz work privately, or explicitly approves a reply back to Buzz.
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/block/berd --skill buzz-handoff명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
Run a long-lived command outside the current Berd turn and wake the owning session with actionable stdout. Use for builds, tests, reviews, deployments, polling, watchers, and other external waits.
Coordinate work across Berd sessions while keeping one conversation available to the user. Use for a long-lived orchestration session.
Create, edit, or inspect Berd agents/personas stored as Agent Markdown files with YAML frontmatter under ~/.agents/agents. Use when user needs to manage Berd agents or personas.
SKILL.md 표시 중
| name | buzz-handoff |
| description | Read and hand off Buzz channels or threads in a private agent conversation using the installed Buzz CLI. Use when a user shares a buzz://message URL or Buzz channel UUID, asks to continue Buzz work privately, or explicitly approves a reply back to Buzz. |
| version | 1.0.0 |
This skill requires a Buzz CLI that implements the handoff contract introduced
by block/buzz@9e6ee814b:
buzz on PATHBUZZ_RELAY_URL configured in the agent process environmentBUZZ_PRIVATE_KEY configured in the agent process environmentBUZZ_AUTH_TAG when required by the configured identityBefore reading or writing, check only whether the required variables exist. Never print their values:
test -n "${BUZZ_RELAY_URL:-}" && test -n "${BUZZ_PRIVATE_KEY:-}"
If configuration is missing, stop and tell the user to configure the standard Buzz CLI environment outside the conversation, using their harness or operating system's secure environment mechanism, then retry. Never ask the user to paste, echo, or save a private key in chat. Do not read Buzz Desktop's keychain, credential store, app-data files, or managed-agent records. Do not discover or select a Buzz Desktop-managed identity.
Read a linked thread:
buzz --format compact messages thread --link '<buzz://message?...>' --limit 200
Read channel metadata and recent messages:
buzz channels get --channel '<channel-uuid>'
buzz --format compact messages get --channel '<channel-uuid>' --limit 100
thread parameter only as a consistency hint while resolving the thread.Writes use the identity represented by the configured Buzz CLI environment. This skill does not select or discover Buzz Desktop-managed identities.
Every write requires approval of the exact full text, channel, and reply target:
🤖 when using the user's
configured identity, unless that identity is intentionally configured as a
distinct agent identity.printf '%s' "$DRAFT_CONTENT" | buzz messages send \
--channel '<channel-uuid>' --content - [--reply-to '<event-id>']
Never externally auto-retry a write. The Buzz CLI owns any safe internal retry
behavior. If it reports delivery_unknown, times out, or returns an unclear
outcome, verify the result in Buzz before retrying.
For operations not covered here, inspect the installed CLI before relying on syntax:
buzz --help
buzz <noun> --help
buzz <noun> <verb> --help
Do not perform any additional Buzz mutation without showing what will change and receiving explicit user approval.