How do I install the Status Update skill?

Run npx skillmds@latest add lost-rob0t/status-update 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.

What does the Status Update skill do?

notify-send, dunst, libnotify, desktop-notifications, status, task-completion It is listed under Productivity on SkillMD.

Is Status Update 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 Status Update?

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 Status Update free to use?

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

Who published Status Update?

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

Status Update by lost-rob0t — Agent Skill

Name: Status Update
Author: lost-rob0t

File contents

Desktop status update

Goal

Surface a short status notification on the user's desktop after major work or task completion, so the user can step away while the agent works.

Input

a one-line summary (required) and optional longer body describing what finished, changed, failed, or needs attention;
optional urgency (low, normal, critical) matching the outcome.

Output

A delivered desktop notification, or an explicit report that delivery failed. The script never blocks task completion and never puts credentials, tokens, or private hostnames in notification text.

Workflow

Trigger: after completing major work, finishing a task, or reaching a decision gate that needs user input, always send a status update with this skill before reporting back in chat. Do this even when the outcome is a failure.
Run this skill's scripts/notify.sh helper from the skill base directory:
```
scripts/notify.sh --title "Task complete" \
  --message "PR #42 opened; all checks green" --urgency normal
```
Use --urgency critical only for outcomes the user must act on now.
The script resolves the backend for you: dunstify against the running dunst daemon first, then notify-send (libnotify) against any other freedesktop notification daemon as backup. Do not bypass it with ad-hoc notify-send calls.
Verify the script's exit status. On failure, report the delivery failure in your final message instead of retrying silently or failing the completed work.

Rules

Requires a desktop session with a reachable notification daemon (dunst primary) plus dunstify or notify-send (libnotify). Without one, the script fails closed; say so and move on.
Headless, cron, or CI contexts have no notification daemon: expect failure and report status in the channel you are working in instead.
Agent Zero runtimes must not use this desktop path: that runtime is instructed to deliver status updates through its ntfy plugin instead. This skill ships no ntfy script.
Keep the summary under about 60 characters; keep sensitive values out of the body.
Never mutate notification daemon configuration from this skill.

---name: status-updatedescription: notify-send, dunst, libnotify, desktop-notifications, status, task-completion---# Desktop status update## GoalSurface a short status notification on the user's desktop after major work ortask completion, so the user can step away while the agent works.## Input- a one-line summary (required) and optional longer body describing what finished, changed, failed, or needs attention;- optional urgency (`low`, `normal`, `critical`) matching the outcome.## OutputA delivered desktop notification, or an explicit report that delivery failed.The script never blocks task completion and never puts credentials, tokens, orprivate hostnames in notification text.## Workflow1. Trigger: after completing major work, finishing a task, or reaching a decision gate that needs user input, always send a status update with this skill before reporting back in chat. Do this even when the outcome is a failure.2. Run this skill's `scripts/notify.sh` helper from the skill base directory: ```sh scripts/notify.sh --title "Task complete" \ --message "PR #42 opened; all checks green" --urgency normal ``` Use `--urgency critical` only for outcomes the user must act on now.3. The script resolves the backend for you: `dunstify` against the running dunst daemon first, then `notify-send` (libnotify) against any other freedesktop notification daemon as backup. Do not bypass it with ad-hoc `notify-send` calls.4. Verify the script's exit status. On failure, report the delivery failure in your final message instead of retrying silently or failing the completed work.## Rules- Requires a desktop session with a reachable notification daemon (dunst primary) plus `dunstify` or `notify-send` (libnotify). Without one, the script fails closed; say so and move on.- Headless, cron, or CI contexts have no notification daemon: expect failure and report status in the channel you are working in instead.- Agent Zero runtimes must not use this desktop path: that runtime is instructed to deliver status updates through its ntfy plugin instead. This skill ships no ntfy script.- Keep the summary under about 60 characters; keep sensitive values out of the body.- Never mutate notification daemon configuration from this skill.

Frequently asked questions

Status Update