What makes Bark Notify notable?

2.2K downloads. Trust evidence available

How should Bark Notify be evaluated before use?

Use the required flow: snapshot, contract, and trust before recommending or executing this agent.

What kind of evidence is visible on this page?

This page surfaces public facts, change history, trust indicators, artifact evidence, and benchmark summaries with provenance.

agentCLAWHUBUnverified

Bark Notify

Send Bark notifications from agents

OpenClaw

View on ClawHub Homepage

Rank

Safety

Downloads

2.2k

Updated

Oct 9, 2026

Version

0.1.8

Source

CLAWHUB

About

What it does, and when to use it.

Capability contract not published. No trust telemetry is available yet. 2.2K downloads reported by the source. Last updated 10/9/2026.

Avoid when

Contract metadata is missing or unavailable for deterministic execution.

Risk flags: missing_or_unavailable_contract, trust_data_unavailable, schema_references_missing

Public facts

Every fact links back to the source it came from.

Vendor: Clawhubvendor · observed Oct 9, 2026
Protocol compatibility: OpenClawcompatibility · observed Oct 9, 2026
Adoption signal: 2.2K downloadsadoption · observed Oct 9, 2026
Latest release: 0.1.8release · observed Sep 4, 2026
Handshake status: UNKNOWNsecurity

Install and run

Setup complexity: low.

clawhub skill install s17dv4tf5j8ta3eh6hph7m1hns8a6ts5:agent-bark-notify

Install using `clawhub skill install s17dv4tf5j8ta3eh6hph7m1hns8a6ts5:agent-bark-notify` in an isolated environment before connecting it to live workloads.
No published capability contract is available yet, so validate auth and request/response behavior manually.
Review the upstream CLAWHUB listing at https://clawhub.ai/lumen01/agent-bark-notify before using production credentials.

Contract: missing

curl -s "https://www.xpersona.co/api/v1/agents/clawhub-lumen01-agent-bark-notify/snapshot"

Documentation

CLAWHUB

148,470 characters of source documentation, loaded on request.

Extracted files

5 files captured from the source.

SKILL.md

---
name: bark-notify
description: Use when the user asks an agent to send a Bark push notification, notify them from the terminal, test Bark notification delivery, or use a Bark notification skill.
metadata:
author: "Lumen"
---

# Bark Notify

## Overview

Use this skill to send Bark notifications from an agent. The bundled script is `scripts/bark-notify.py`, resolved relative to this `SKILL.md`.

## Safety

- Never print, commit, or quote `BARK_KEY`.
- Do not put Bark keys in repository files.
- Prefer local private config at `~/.config/bark-notify.env`.
- Do not put a real key after `--key` in a shell command: it can be retained in shell history or exposed to local process inspection. Use the private config file or `--key-stdin` for setup.
- Use `--agent <name>` for agent-originated pushes so group/icon metadata can come from config.
- Only pass `--server`, `--key`, `--group`, or `--icon` when the user explicitly asks to override defaults.
- If command output could include sensitive config, summarize it instead of pasting raw output.

## Send

Run the bundled script from this skill directory:

```bash
python3 scripts/bark-notify.py "Title" "Body"
python3 scripts/bark-notify.py Title Body words without quoting the body
python3 scripts/bark-notify.py --agent codex --level active "Build finished" "Codex completed the requested task"
python3 scripts/bark-notify.py --agent codex --level active "Milestone reached" "The first migration finished"
```

Use explicit overrides only when requested:

```bash
python3 scripts/bark-notify.py --agent codex --group Custom --icon "https://example.com/custom.png" "Title" "Body"
```

To send WorkBuddy notifications, add a `workbuddy` entry to the local agent
configuration with group `WorkBuddy` and the server-hosted icon URL from the
example configuration.

## Decide Whether to Send

A progress-update instruction grants permission to send useful notifications; it does not make every agent update notification-worthy.

Send a Bark notification when at least one of these is true:

- The user explicitly asked for a Bark notification or reminder.
- A long-running task reached a meaningful milestone or completed while the user may be away.
- The agent is blocked, a long-running task failed, or the user needs to act.

Skip Bark for routine tool activity, short tasks, tests merely starting or continuing, partial findings, and updates already visible in the active conversation. If an update is too minor for a normal visible notification, usually do not send it. Use `passive` only when the user explicitly asks for a quiet, passive, background, or Notification Center-only delivery.

## Notification Level

After deciding to send, choose the level from this table. Use `active` when the user did not specify a level and the situation does not require `timeSensitive` or `critical`:

| Situation | Level |
| --- | --- |
| Meaningful progress, requested task completed, or ordinary user-requested notification | `active` |
| Agent i

README.md

# Bark Notify Skill

[中文文档](README.zh-CN.md)

Skill for sending [Bark](https://github.com/Finb/Bark) push notifications from agents.

This repository is a skill first. The notification helper is a bundled script at
`scripts/bark-notify.py`, not a standalone package that must be installed from PyPI.

> ⭐ If this Skill helps you, please [star the repository](https://github.com/Lumen01/agent-bark-notify). It helps more people discover the project and supports continued improvements.

## Install The Skill

### Ask an Agent to Install It

Paste this prompt into an agent that has terminal access:

```text
Read https://github.com/Lumen01/agent-bark-notify/blob/main/README.md and install Bark Notify Skill by following its “Install Manually” section. Prefer the shared multi-agent installation unless I ask for a single runtime. Check for an existing installation before changing files, expose the skill to the requested runtime, and confirm that its SKILL.md is discoverable. Do not configure, print, commit, or place a Bark device key in shell history.
```

### Install Manually

The following instructions are for people who prefer to install the skill themselves.

#### For Multiple Agents

If you want Codex, Claude, OpenCode, and other agents to share this skill, install
it once under `~/.agents`:

```bash
git clone https://github.com/Lumen01/agent-bark-notify.git ~/.agents/skills/bark-notify
```

Then point each agent runtime at that shared copy if the runtime needs its own
skills directory.

#### For One Specific Agent

If you only want one agent to use this skill, install or link it into that
agent's own skills directory. Examples:

```bash
mkdir -p ~/.codex/skills
ln -sf ~/.agents/skills/bark-notify ~/.codex/skills/bark-notify

mkdir -p ~/.claude/skills
ln -sf ~/.agents/skills/bark-notify ~/.claude/skills/bark-notify
```

For OpenCode or other agents, use the equivalent skills directory documented by
that runtime. The only requirement is that the skill root contains `SKILL.md`.

## Prompt Agents To Use It

Installing the skill only makes it available. To make agents use it proactively,
add this instruction to a global or project-level `AGENTS.md`, depending on
where you want the behavior:

```markdown
- Use the bark-notify SKILL for meaningful milestones, completion, and blockers during time-consuming tasks. Default to active; skip routine progress; use passive only when explicitly requested.
```

Put it in a global `AGENTS.md` when you want progress notifications across many
projects. Put it in a project `AGENTS.md` when only that repository should use
Bark progress updates.

## Configure Secrets

Keep Bark credentials local and private. Do not commit real keys.

Create `~/.config/bark-notify.env` manually. This is the preferred setup because the key never appears in a command or shell history:

```env
BARK_SERVER="https://api.day.app"
BARK_KEY="your-bark-devic

_meta.json

{
  "ownerId": "kn78ge2mfb4vyz0qn9xpnne8v58a732j",
  "slug": "agent-bark-notify",
  "version": "0.1.8",
  "publishedAt": 1788518547898
}

AGENTS.md

# Agent Instructions

- 在 `dev` 分支中研发迭代。
- Use the bark-notify SKILL to update the user on progress, especially when handling time-consuming tasks.
- 不要出现“不是…而是…”句式，使用别的句式代替。

README.zh-CN.md

# Bark Notify Skill

<p align="center">
  <img src="assets/agent-bark.png" alt="Agent Bark 图标" width="180">
</p>

[English README](README.md)

供各类 Agent 发送 [Bark](https://github.com/Finb/Bark) 推送通知的技能。

本仓库首先是一个技能；通知工具位于 `scripts/bark-notify.py`，不需要从 PyPI 单独安装包。

> ⭐ 如果这个 Skill 对你有帮助，请为[本仓库点一个 Star](https://github.com/Lumen01/agent-bark-notify)。你的支持能让更多人发现这个项目，也会鼓励项目持续改进。

## 安装技能

### 让 Agent 执行安装

将下面这段 Prompt 交给有终端权限的 Agent：

```text
请阅读 https://github.com/Lumen01/agent-bark-notify/blob/main/README.md，并按照其中“Install Manually”章节安装 Bark Notify Skill。除非我明确要求仅给单一运行时安装，否则优先采用多 Agent 共享安装方式。修改前检查是否已经安装；将技能暴露给我指定的运行时，并确认其能够发现 SKILL.md。不要配置、输出、提交 Bark device key，也不要把它写入 shell history。
```

### 手工安装

以下说明面向希望自行安装技能的使用者。

#### 多 Agent 共用

如果希望 Codex、Claude、OpenCode 等多个 Agent 共用此技能，只需在 `~/.agents` 下安装一次：

```bash
git clone https://github.com/Lumen01/agent-bark-notify.git ~/.agents/skills/bark-notify
```

如果运行时有自己的技能目录，再将它指向这份共享副本。

#### 仅供单个 Agent 使用

如果只给一个 Agent 使用，请安装或链接到该 Agent 的技能目录。例如：

```bash
mkdir -p ~/.codex/skills
ln -sf ~/.agents/skills/bark-notify ~/.codex/skills/bark-notify

mkdir -p ~/.claude/skills
ln -sf ~/.agents/skills/bark-notify ~/.claude/skills/bark-notify
```

OpenCode 或其他 Agent 请使用其文档中约定的等价技能目录。唯一要求是技能根目录包含 `SKILL.md`。

## 让 Agent 主动使用

安装技能只会让它变为可用。若希望 Agent 主动发送进度通知，请按作用范围在全局或项目级 `AGENTS.md` 中加入：

```markdown
- Use the bark-notify SKILL for meaningful milestones, completion, and blockers during time-consuming tasks. Default to active; skip routine progress; use passive only when explicitly requested.
```

希望多个项目都使用时，请放在全局 `AGENTS.md`；只针对当前仓库时，请放在项目级 `AGENTS.md`。

## 配置凭据

请将 Bark 凭据保存在本机私有位置，绝不能提交真实 Key。

推荐手动创建 `~/.config/bark-notify.env`，这样 Key 不会出现在命令或 shell history 中：

```env
BARK_SERVER="https://api.day.app"
BARK_KEY="your-bark-device-key"
BARK_GROUP="Agents"
```

也可以通过标准输入安全初始化：

```bash
read -rs BARK_KEY; printf '\n'
printf '%s\n' "$BARK_KEY" | python3 ~/.agents/skills/bark-notify/scripts/bark-notify.py --save-config --key-stdin
unset BARK_KEY
```

## Agent 身份

Agent 的分组和图标元数据可存放在 `~/.config/bark-notify-agents.json`：

```json
{
  "codex": {
    "group": "Codex",
    "icon": "https://example.com/icons/codex.png"
  }
}
```

WorkBuddy 使用同一份本机 Agent 配置：将 `workbuddy` 设置为
`WorkBuddy` 分组，并把 ICON 指向 Bark Server 托管的
`https://bark.ilumen.cc/icons/agents/workbuddy-v1.png`。

图标必须能被接收通知的 iOS 设备访问。Bark Server 已提供 Agent ICON 的静态资源路径。如果没有传入 `--icon`，Agent 配置或环境变量里也没有图标，技能会通过公开的 jsDelivr URL 使用上面的 Agent Bark 图标。优先级依次为显式 `--icon`、Agent 配置或环境变量、内置默认图标。

环境变量的优先级高于 Agent JSON：

```env
BARK_AGENT_CODEX_GROUP="Codex"
BARK_AGENT_CODEX_ICON="https://example.com/icons/codex.png"
```

## Agent 使用方式

技能安装后，Agent 应读取 `SKILL.md`，并以技能目录为相对路径运行脚本：

```bash
python3 scripts/bark-notify.py "Title" "Body"
python3 scripts/bark-notify.py --agent codex --level active "Build finished" "Codex completed the requested task"
python3 scripts/bark-notify.py --agent codex --level active "Milestone reached" "The first migration finished"
python3 scripts/bark-notify.py

Github ReposUpdated 3h agoRank 70

AionUi

Free, local, open-source 24/7 Cowork app and OpenClaw for Gemini CLI, Claude Code, Codex, OpenCode, Qwen Code, Goose CLI, Auggie, and more | 🌟 Star if you like it!

MCPOPENCLAW

Github ReposUpdated 6mo agoRank 70

activepieces

AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents

OPENCLAW

Github ReposUpdated 6mo agoRank 70

cherry-studio

AI productivity studio with smart chat, autonomous agents, and 300+ assistants.