Agent skill · Workflow & Productivity

sendblue-notify

Text the user's phone when a long-running task, agent turn, or scheduled job finishes — via @sendblue/cli for outbound, optionally wired to a Claude Code Stop hook for automatic fire.

Nick44,414★ · +328/wk · 1 repos on radarProfile →
claude-codecodexcursorMIT
Install
npx skills add sickn33/agentic-awesome-skills --skill sendblue-notify --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 10 KB
Bundled scripts: none
Declared author: AnthonyFirth
Path: skills/sendblue/sendblue-notify/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 44,414 · +328 this week
Language: Python
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Sendblue Notify ## Overview Outbound, fire-and-forget notifications from a local Claude Code session, script, or scheduled job to the user's phone via Sendblue. This is the "walk away from the terminal" pattern: kick off something long, get an iMessage when it lands. This skill owns **when to notify and what to say**. Actual sending goes through [[sendblue-cli]]. Hook wiring (so notifications fire automatically) goes through [[update-config]]. ## When to Use This Skill - Use when the user says "text me when X is done", "ping my phone", "notify me on completion", "let me know when the build/deploy/migration finishes", or "send me an iMessage when…". - Use when the user asks to wire a hook that texts on agent stop, `/loop` iteration, or `/schedule` completion. - Use when an agent turn is genuinely long-running and the user has gone heads-down on something else. - Do **not** use for short, interactive tasks where the user is watching the terminal — the notify is noise. ## Prerequisites The CLI must be installed and authenticated: ```bash npx @sendblue/cli whoami # confirms creds # or, if first run: npx @sendblue/cli setup ``` The user's phone number must be a verified contact on the

What's inside
Steps it walks through
  1. Overview
  2. When to Use This Skill
  3. Prerequisites
  4. How It Works
  5. Step 1: Decide whether notify is appropriate
  6. Step 2: Pick a delivery pattern
  7. Step 3: Compose the notification copy
  8. Examples
  9. Example 1: One-shot inline send
  10. Example 2: Claude Code Stop hook (opt-in, scoped)
  11. Example 3: End-of-/loop or /schedule ping
  12. Composing with textme
  13. Best Practices
  14. Limitations
Commands it runs
npx @sendblue/cli whoami        # confirms creds
npx @sendblue/cli setup
if long_running_thing; then
npx @sendblue/cli send +15551234567 "✅ done: $(date +%H:%M)"
else
npx @sendblue/cli send +15551234567 "❌ failed: $(date +%H:%M)"
fi
npx @sendblue/cli send +15551234567 "migration done — $RESULT"
npx @sendblue/cli send "$NOTIFY_NUMBER" "turn done in ${CLAUDE_TURN_DURATION_SECONDS}s" || true
More from agentic-awesome-skills
All skills →
About this skill
What does the sendblue-notify skill do?

Text the user's phone when a long-running task, agent turn, or scheduled job finishes — via @sendblue/cli for outbound, optionally wired to a Claude Code Stop hook for automatic fire.

How do I install it?

Run `npx skills add sickn33/agentic-awesome-skills --skill sendblue-notify --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From sickn33/agentic-awesome-skills, a repository with 44,414 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going