bark-notify
Send Bark Notifications After AI Tasks
Long-running AI tasks can finish without drawing attention. This skill sends a Bark push with device, project, status, and summary details.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "bark-notify" from https://skillstore.io/skills/caopulan-bark-notify.md and its manifest at https://skillstore.io/api/skills/caopulan-bark-notify/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "bark-notify". Notify me after the documentation update succeeds.
Expected outcome:
Bark notification sent: Documentation Update; device Workstation; project API Docs; status success; summary Documentation examples updated.
Using "bark-notify". Report the test run even when some tests fail.
Expected outcome:
Bark notification sent: Test Run; device Build Host; project Payments; status partial; summary Two integration tests remain failing.
Using "bark-notify". Send a completion alert using the project name from AGENTS.md.
Expected outcome:
Bark notification sent: Dependency Review; device Laptop; project Client Portal; status success; summary Dependencies reviewed and lockfile updated.
Security Audit
Medium RiskMost static findings are false positives caused by Markdown code spans, shell line continuations, standard installation paths, and specific configuration variable reads. Two medium risks remain: dry-run output reveals the Bark key, and a custom endpoint receives that key plus task metadata. No prompt injection or malicious intent was found.
Confirmed security concerns (2)
Risk Factors
๐ Network access (3)
๐ Env variables (3)
โ๏ธ External commands (9)
๐ Filesystem access (7)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/caopulan-bark-notify/audits/9?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/caopulan-bark-notify?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/caopulan-bark-notify?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/caopulan-bark-notify/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/caopulan-bark-notify.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA ยท BibTeX ยท CFF)
APA citation
caopulan. (2026). bark-notify security audit report (audit version 9) [Author version unspecified]. Skillstore. https://skillstore.io/skills/caopulan-bark-notify/audits/9BibTeX citation
@techreport{caopulan-caopulan-bark-notify-2026,
author = {caopulan},
title = {bark-notify security audit report (audit version 9)},
institution = {Skillstore},
year = {2026},
number = {9},
url = {https://skillstore.io/skills/caopulan-bark-notify/audits/9},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "bark-notify security audit report (audit version 9)"
version: "unspecified"
type: report
authors:
- name: "caopulan"
date-released: "2026-07-23"
url: "https://skillstore.io/skills/caopulan-bark-notify/audits/9"
identifiers:
- type: other
value: "skillstore:caopulan-bark-notify:audit:9"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Monitor Long Coding Tasks
Receive a mobile alert when a local Codex or Claude coding task finishes.
Track Automated Maintenance
Send concise completion status after repository checks, migrations, or documentation updates.
Follow Remote Workflows
Receive project and status details while working away from the development machine.
Try These Prompts
Send a Bark notification that this task completed successfully with the summary: updated the documentation.
Notify me through Bark when this refactor finishes, including project name, success status, and a concise summary without secrets.
At the end of this run, send Bark status failed or partial based on results and summarize unresolved test failures.
Complete deployment checks, derive the project name from AGENTS.md, then send a Bark notification with accurate status and sanitized results.
Best Practices
- Keep task summaries concise and remove credentials, customer data, and private source content.
- Use a trusted HTTPS Bark endpoint and protect the key environment variable.
- Keep dry-run output private because the current helper prints the Bark request URL.
Avoid
- Do not place secrets or complete command output in notification summaries.
- Do not send notifications to an endpoint that you do not control or trust.
- Do not treat a notification status as independent proof that a task succeeded.
Frequently Asked Questions
What configuration is required?
How is the project name selected?
Can I use a self-hosted Bark server?
What data leaves my machine?
Can I test without sending a notification?
Which status values are supported?
Developer Details
Author
caopulanLicense
MIT
Skillstore revision
r2
Version notice
The author did not declare a version.
Ref
a39a91716eadede5f4cdefd78178fed4e837a128
Maintenance freshness
7/24/2026
Usage
10 downloads ยท 189 views
File structure