Kubeshark Installer
kubeshark/kubeshark
Installs and configures Kubeshark on a Kubernetes cluster, choosing between the quick CLI path and a Helm install with custom values.
Run a long-lived command outside the current Berd turn and wake the owning session with actionable stdout.
Install Berd Monitor
$ npx skills add block/berd --skill berd-monitor -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install block/berd berd-monitor --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/block/berd.git skills-src && mkdir -p .claude/skills && cp -r skills-src/distro/skills/berd-monitor .claude/skills/berd-monitor && rm -rf skills-srcUse ~/.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/
Install the "berd-monitor" agent skill from https://github.com/block/berd/tree/main/distro/skills/berd-monitor into .claude/skills/berd-monitor/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "berd-monitor", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/block/berd/tree/main/distro/skills/berd-monitorType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add block/berd --skill berd-monitor -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install block/berd berd-monitor --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/block/berd.git skills-src && mkdir -p .agents/skills && cp -r skills-src/distro/skills/berd-monitor .agents/skills/berd-monitor && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "berd-monitor" agent skill from https://github.com/block/berd/tree/main/distro/skills/berd-monitor into .agents/skills/berd-monitor/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "berd-monitor", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add block/berd --skill berd-monitor -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install block/berd berd-monitor --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/block/berd.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/distro/skills/berd-monitor .cursor/skills/berd-monitor && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "berd-monitor" agent skill from https://github.com/block/berd/tree/main/distro/skills/berd-monitor into .cursor/skills/berd-monitor/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "berd-monitor", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/block/berd.git --path distro/skills/berd-monitor--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add block/berd --skill berd-monitor -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install block/berd berd-monitor --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/block/berd.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/distro/skills/berd-monitor .gemini/skills/berd-monitor && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "berd-monitor" agent skill from https://github.com/block/berd/tree/main/distro/skills/berd-monitor into .gemini/skills/berd-monitor/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "berd-monitor", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install block/berd berd-monitorInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add block/berd --skill berd-monitor -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/block/berd.git skills-src && mkdir -p .github/skills && cp -r skills-src/distro/skills/berd-monitor .github/skills/berd-monitor && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "berd-monitor" agent skill from https://github.com/block/berd/tree/main/distro/skills/berd-monitor into .github/skills/berd-monitor/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "berd-monitor", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add block/berd --skill berd-monitor -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install block/berd berd-monitor --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/block/berd.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/distro/skills/berd-monitor .opencode/skills/berd-monitor && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "berd-monitor" agent skill from https://github.com/block/berd/tree/main/distro/skills/berd-monitor into .opencode/skills/berd-monitor/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "berd-monitor", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
berd-monitor- GitHub stars
- 975
- Token cost
- ~467 tokens
- SKILL.md length
- 203 words
- Files
- 1
- Skills in repo
- 11
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Run a long-lived command outside the current Berd turn and wake the owning session with actionable stdout.
- Other external waits
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Tasks that involve Deployment
What it does
Berd Monitor is an agent skill from block/berd, published by the product's own GitHub organization. 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.
Its SKILL.md is about 470 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in DevOps & Cloud, covering Deployment. 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
- Other external waits
- Tasks that involve Deployment
Example prompts
- “/berd-monitor”
What it can do on your machine
Read from SKILL.md and the folder at commit d980f51. 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).
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 Monitor loads about 467 tokens when it runs. Until then it costs about 52 tokens; SKILL.md has 203 words of instructions outside code blocks.
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 d980f51, republished under its Apache-2.0 licence (© block). 203 words, ~467 tokens.
Download SKILL.mdSave it as
.claude/skills/berd-monitor/SKILL.md (or your agent's skills folder).- name
- berd-monitor
- description
- 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.
- metadata.berdBundled
- true
Berd Monitor
Use berd-monitor when a command may outlive the current turn. It detaches the
producer from Berd and the agent harness, buffers output across delivery
failures, and sends complete stdout lines to the exact originating session.
Run short, bounded commands normally. Do not hold a turn open with sleep,
polling, log tailing, or a foreground timeout.
Start
berd-monitor run \
--state-key <stable-key> \
--label '<concise source name>' \
--instructions '<short event-handling guidance>' \
-- <producer-command> [args...]AGENT_SESSION_ID selects the current session. Use --session-id only for
another positively identified session; never infer a session from the working
directory. The command prints the detached monitor PID. After checking the
monitor's watcher.log under the printed state directory when diagnosis is
needed, continue other work or end the turn—never wait on the detached PID.
The producer's stdout is the event API:
- emit concise, newline-terminated milestones and flush promptly;
- put verbose output and diagnostics in durable logs or stderr;
- avoid NUL bytes and emit a final summary when practical.
Default --if-running steer adds an event to an active run or starts a new
turn. Use --if-running queue only when the active run must not be steered.
Pending events retry without being dropped, and a trailing partial line is
delivered when the producer exits.
Delivered messages are visibly labeled as coming from berd-monitor. Stop a
monitor with:
berd-monitor stop --state-key <stable-key>© 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-monitor of block/berd.
Open the folder on GitHubat commit d980f51
Compare with similar skills
Berd Monitor 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Berd Monitor this skillblock/berd | 975 | — | ~467 | Automated safety check: Pass | Apache-2.0 | |
| Kubeshark Installerkubeshark/kubeshark | 12k | — | ~3.6k | Automated safety check: Notes | Apache-2.0 | |
| GreptimeDB Dev Docker ImageGreptimeTeam/greptimedb | 6.7k | — | ~4k | Automated safety check: Notes | Apache-2.0 | |
| Mirrord Operatormetalbear-co/mirrord | 5.4k | 1 repos | ~4.6k | Automated safety check: Pass | MIT | |
| KubeSphere ServiceMesh Managerkubesphere/kubesphere | 17k | — | ~2.4k | Automated safety check: Pass | Custom licence | |
| Vercelremotion-dev/remotion | 63k | — | ~1.2k | Automated safety check: Pass | Custom licence |
Similar skills
GreptimeDB Dev Docker Image
GreptimeTeam/greptimedb
Packages a locally built GreptimeDB debug binary into a development-only Docker image for local-cluster testing, with an optional push to a dev registry.
Mirrord Operator
metalbear-co/mirrord
Help users install and configure the mirrord Operator for team/enterprise environments.
KubeSphere ServiceMesh Manager
kubesphere/kubesphere
Installs, checks and troubleshoots the KubeSphere ServiceMesh extension (Istio, Kiali, Jaeger), including grayscale release, sidecar injection, topology and tracing issues.
- Official
Vercel
remotion-dev/remotion
Set up a Codex monitor for Vercel deployments and preview URLs.
AWS Cdk Development
zxkane/aws-skills
AWS Cloud Development Kit (CDK) expert for building cloud infrastructure with TypeScript/Python.
More from block/berd
All 11 skills in this repo- Official
Agent Builder
block/berd
Create, edit, or inspect Berd agents/personas stored as Agent Markdown files with YAML frontmatter under ~/.agents/agents.
- Official
Assistive UX
block/berd
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…
- Official
Buzz Handoff
block/berd
Read and hand off Buzz channels or threads in a private agent conversation using the installed Buzz CLI.
- Official
Create PR
block/berd
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…
- Official
Experimental Features
block/berd
A skill your agent uses when adding, reviewing, configuring, graduating, or removing Berd experiments.
- Official
Skill Builder
block/berd
Create, edit, or inspect Berd skills stored as skill folders with SKILL.md files.
Related
Categories
Questions about Berd Monitor
What does Berd Monitor do?
Run a long-lived command outside the current Berd turn and wake the owning session with actionable stdout. Berd Monitor is an agent skill from block/berd, published by the product's own GitHub organization. Run a long-lived command outside the current Berd turn and wake the owning session with actionable stdout.
When should I use Berd Monitor?
Berd Monitor fits situations like: other external waits; tasks that involve Deployment.
How do I install Berd Monitor in Claude Code?
Run `npx skills add block/berd --skill berd-monitor -a claude-code`. Or copy the skill folder (distro/skills/berd-monitor in block/berd) into .claude/skills/berd-monitor in your project. Claude Code loads it when a task matches its description.
How do I install Berd Monitor in Codex?
Run `npx skills add block/berd --skill berd-monitor -a codex`. Or copy the skill folder (distro/skills/berd-monitor in block/berd) into .agents/skills/berd-monitor in your project. Codex loads it when a task matches its description.
Can I use Berd Monitor 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-monitor -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-monitor, .gemini/skills/berd-monitor, .github/skills/berd-monitor and .opencode/skills/berd-monitor in your project.
What does Berd Monitor need to run?
SKILL.md names no scripts, command-line tools or credentials: Berd Monitor is instructions for the agent only.
Does Berd Monitor 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 Monitor 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 Monitor use?
Berd Monitor 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 Monitor use?
About 467 tokens (SKILL.md is roughly 1.9k 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 Monitor?
Skills that share tags, products or a category with Berd Monitor: Kubeshark Installer (kubeshark/kubeshark, 12k stars), GreptimeDB Dev Docker Image (GreptimeTeam/greptimedb, 6.7k stars), Mirrord Operator (metalbear-co/mirrord, 5.4k stars) and KubeSphere ServiceMesh Manager (kubesphere/kubesphere, 17k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Berd Monitor?
block (a GitHub organization, an official publisher) maintains it in block/berd, which has 975 GitHub stars. The repository holds 11 skills in this directory. The repository was last updated on October 9, 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.