martinhjartmyr/skills · Archived

notifery

Send notifications via Notifery API using curl.

First seen Mar 14, 2026

Installation

$ npx skills add martinhjartmyr/skills --skill notifery

View on skills.sh ↗ GitHub repository ↗

Summary

Send notifications via Notifery API using curl.
Use when the user wants to be notified about task completions, errors, or progress.
Also use proactively after long-running tasks, failed operations, or when the user has asked to be kept informed.
Triggers include "notify me", "send notification", "let me know when done", "alert me", "ping me", "notifery", or when a long task completes and the user previously asked for notifications.
Requires NOTIFERY_API_KEY environment variable.

Stronger alternatives

This repository is archived — consider an actively maintained alternative.

umami Same source · more installs

martinhjartmyr/skills

Fetch analytics from Umami. Use when the user asks about umami, analytics, website traffic, dai…

39 installs

overvy Same source

martinhjartmyr/skills

Interact with the Overvy kanban board via curl. Use when the user wants to list issues, list AI…

4 installs

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

frontend-design Same topic

anthropics/skills

Guidance for distinctive, intentional visual design when building new UI or reshaping an existi…

866.4K installs

agent-browser Same topic

vercel-labs/agent-browser

Browser automation CLI for AI agents. Use when the user needs to interact with websites, includ…

810.4K installs

vercel-react-best-practices Same topic

vercel-labs/agent-skills 697.8K installs

web-design-guidelines Same topic

vercel-labs/agent-skills

Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "chec…

617.3K installs

microsoft-foundry Same topic

microsoft/azure-skills

Build, deploy, evaluate, optimize, fine-tune, and manage Microsoft Foundry agents, models, and …

576.5K installs

azure-diagnostics Same topic

microsoft/azure-skills

Debug Azure production issues on Azure using AppLens, Azure Monitor, resource health, and safe …

568.9K installs

Also in this package

Other skills from martinhjartmyr/skills.

npx skills add martinhjartmyr/skills

umami 39 overvy 4

Browse all from martinhjartmyr/skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared

Cursor Not declared

Codex Not declared

GitHub Copilot Not declared

Windsurf Not declared

Gemini CLI Not declared

Cline Not declared

OpenCode Not declared

Repository health

Default branch main

Open issues 0

Status Archived

Package contents

Files included with this skill beyond the listing page.

skill md SKILL.md 3,648 B
docs SUMMARY.md 499 B

History

Mar 14, 2026 First seen on skills.sh
Sep 9, 2026 First recorded snapshot · 4 installs

SKILL.md

Notifery

Send notifications to the user via the Notifery API.

API Configuration

Base URL: https://api.notifery.com (override with NOTIFERYAPIURL env var)
Auth: x-api-key: $NOTIFERYAPIKEY

At the start of any workflow, verify the API key is set:

test -n "$NOTIFERY_API_KEY" || echo "ERROR: NOTIFERY_API_KEY is not set"

If NOTIFERYAPIKEY is not set, stop and tell the user to set it.

Key Details

title is the only required field.
If NOTIFERYDEFAULTGROUP is set and no group is provided, use it as the default group.

API Operations

Send Notification

curl -s -f -X POST "${NOTIFERY_API_URL:-https://api.notifery.com}/event" \
  -H "x-api-key: $NOTIFERY_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "title": "TITLE",
    "message": "MESSAGE",
    "group": "GROUP"
  }'

Only include fields that have values. Omit fields that are not needed.

Parameters:

Parameter	Type	Required	Description
title	string	Yes	Notification title (1-255 chars)
message	string	No	Body text (max 2048 chars)
group	string	No	Group alias (falls back to `NOTIFERYDEFAULTGROUP`)
code	number	No	Status code: 0 = success, >0 = error
duration	number	No	Duration in milliseconds
ttl	number	No	Auto-expiry in seconds (60-31536000)
icon	string	No	Icon name
iconColor	string	No	Hex color for icon (e.g. "ff0000")

Response: { "ok": true } on success.

Error Handling

All curl commands use -f to fail on HTTP errors.
If a command fails, check the HTTP status by running without -f and adding -w "\n%{http_code}".
Common errors: 401 (bad API key), 422 (invalid parameters).

Proactive Usage

Send notifications proactively in these situations:

After a long-running task completes (build, deploy, migration).
When a task fails with an error.
When the user explicitly asked to be notified ("let me know when done").

When sending proactively, use code: 0 for success and code: 1 for errors.

Example: Task Completion

curl -s -f -X POST "${NOTIFERY_API_URL:-https://api.notifery.com}/event" \
  -H "x-api-key: $NOTIFERY_API_KEY" \
  -H "Content-Type: application/json" \
  -d "{
    \"title\": \"Build complete\",
    \"message\": \"Project built successfully in 42s\",
    \"code\": 0,
    \"duration\": 42000
  }"

Example: Task Failure

curl -s -f -X POST "${NOTIFERY_API_URL:-https://api.notifery.com}/event" \
  -H "x-api-key: $NOTIFERY_API_KEY" \
  -H "Content-Type: application/json" \
  -d "{
    \"title\": \"Deploy failed\",
    \"message\": \"Error: container health check timed out\",
    \"code\": 1
  }"

npx skills add martinhjartmyr/skills --skill notifery