bark-notify
ListedSend Bark (day.app) push notifications after Codex completes a task. Use when one Codex or Claude run is finished, or when you need to notify on task completion with device name, project name, status,
Install on your platform
Showing OpenClaw.
- 1
Run this in your terminal
terminal$
What we know about this skill
Publisher
caopulan
Taken from the source listing. We haven't verified who controls this account.
Install target
Live repository
Not pinned. Installing fetches whatever the repository holds at the time you run the command.
Automated safety checks
This skill failed 1 of 6 checks. A failure is not proof of bad intent; it means something in the code needs a human to look at it before you run it.
No undeclared network calls: failed
Contacts 1 host that is neither well-known infrastructure nor declared in the skill's frontmatter: api.day.app.
Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.
Hosts contacted
api.day.appundeclaredWhat it found
- bark-notify/scripts/send_bark_notification.py:88contacts api.day.app
base_url = os.environ.get("CODEX_BARK_BASE_URL", "https://api.day.app")
Declares what it does: passed
SKILL.md parses and declares a name and a description.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
No credential access: passed
Reads no keys, tokens, keychains or credential files.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
No pipe-to-shell installers: passed
No pipe-to-shell or download-and-run installers.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
Pinned to a commit: passed
Scanned caopulan/notification-skill at f2616ef2fc.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- f2616ef2fc
- Manifest
- bark-notify/SKILL.md
- Scanned
- 2 files, 198 lines
About this skill
What it does
The bark-notify skill sends push notifications via the Bark app (day.app) upon completion of tasks executed by Codex or Claude. These notifications include details such as the device name, project name, and the task's final status. This allows for real-time awareness of task progress without constantly monitoring logs or dashboards.
When to use it
- Automated workflows: Receive immediate alerts when a complex automated workflow finishes processing data.
- Long-running tasks: Get notified as soon as lengthy Codex/Claude jobs are complete, especially useful for batch processes.
- Project status updates: Track the progress of projects by receiving notifications on task completion within those projects.
- Monitoring critical operations: Ensure timely awareness of successful or failed executions of essential operational scripts.
Key capabilities
- Sends push notifications to Bark (day.app).
- Includes device name in notification.
- Includes project name in notification.
- Includes task status in notification.
- Compatible with Codex and Claude workflows.
Example prompts
- "Notify me on my iPhone when the data processing job finishes."
- "Send a Bark notification to my iPad when the 'Report Generation' project completes."
- "Alert me via Bark if the 'Model Training' task fails."
Tips & gotchas
- You must have the Bark app installed and configured on your device(s) for notifications to be received.
- Ensure that your Codex/Claude workflow is properly set up to trigger the
bark-notifyskill at the desired completion point.