How do I install the Notify On Completion skill?

Run npx skillmds@latest add tomevault-io/notify-on-completion in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Notify On Completion safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Notify On Completion?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Notify On Completion free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Notify On Completion?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Notify On Completion by tomevault-io

Name: Notify On Completion
Author: tomevault-io

Notify On Completion

Send local completion notifications to the agent-notifier service via POST http://127.0.0.1:60766/agent/notify after finishing a task; include title, content, and agent details so the desktop app shows a system notification. Use when this capability is needed.

tomevault-io 972cba8 2 files · 3.0 KB Updated Sep 17, 2026

File contents

Notify on Completion

Endpoint

POST http://127.0.0.1:60766/agent/notify
Header: Content-Type: application/json
Scope: Loopback only; requires the agent-notifier app to be running and listening.

Payload properties

title (string, required): Concise heading for the notification title (e.g., "Build succeeded", "Tests failed").
content (string, required): One to two sentences summarizing the outcome. Include key facts such as what finished, duration, artifact paths, or a brief error summary. Keep under ~950 characters because the server truncates the displayed body to 1000 characters after prefixing the agent.
agent (string, required): Short identifier for the calling agent or workflow (e.g., "codex", "ci-run"). Avoid blanks and trailing spaces.

The server renders the notification body as <agent>: <content>.

Construction rules

Trim all fields; do not send empty strings.
Make success/failure explicit in title and content.
Include the most useful signal in content (duration, counts, artifact hints, or top error line).
Stay within the soft 950-character limit to avoid truncation.
Build JSON safely (use jq -n or printf); escape quotes to avoid invalid payloads.

cURL template

agent_name="codex"
title="Feature implemented"
content="The feature was implemented in ${elapsed}s; bundle at dist/."

curl --fail --silent --show-error \
  -X POST http://127.0.0.1:60766/agent/notify \
  -H "Content-Type: application/json" \
  -d "$(jq -n --arg title "$title" --arg content "$content" --arg agent "$agent_name" '{title:$title, content:$content, agent:$agent}')"

When to send

After long-running builds, tests, deploys, or data jobs finish.
Before ending a session when the user may be away from the terminal.
When a task fails; set a failure-focused title and summarize the error in content.

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: notify-on-completiondescription: Send local completion notifications to the agent-notifier service via POST http://127.0.0.1:60766/agent/notify after finishing a task; include title, content, and agent details so the desktop app shows a system notification. Use when this capability is needed.---# Notify on Completion## Endpoint- POST `http://127.0.0.1:60766/agent/notify`- Header: `Content-Type: application/json`- Scope: Loopback only; requires the agent-notifier app to be running and listening.## Payload properties- `title` (string, required): Concise heading for the notification title (e.g., "Build succeeded", "Tests failed").- `content` (string, required): One to two sentences summarizing the outcome. Include key facts such as what finished, duration, artifact paths, or a brief error summary. Keep under ~950 characters because the server truncates the displayed body to 1000 characters after prefixing the agent.- `agent` (string, required): Short identifier for the calling agent or workflow (e.g., "codex", "ci-run"). Avoid blanks and trailing spaces.The server renders the notification body as `<agent>: <content>`.## Construction rules1. Trim all fields; do not send empty strings.2. Make success/failure explicit in `title` and `content`.3. Include the most useful signal in `content` (duration, counts, artifact hints, or top error line).4. Stay within the soft 950-character limit to avoid truncation.5. Build JSON safely (use `jq -n` or `printf`); escape quotes to avoid invalid payloads.## cURL template```bashagent_name="codex"title="Feature implemented"content="The feature was implemented in ${elapsed}s; bundle at dist/."curl --fail --silent --show-error \ -X POST http://127.0.0.1:60766/agent/notify \ -H "Content-Type: application/json" \ -d "$(jq -n --arg title "$title" --arg content "$content" --arg agent "$agent_name" '{title:$title, content:$content, agent:$agent}')"```## When to send- After long-running builds, tests, deploys, or data jobs finish.- Before ending a session when the user may be away from the terminal.- When a task fails; set a failure-focused `title` and summarize the error in `content`.---> Converted and distributed by [TomeVault](https://tomevault.io/claim/davidkelley) — claim your Tome and manage your conversions.

Frequently asked questions