Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →lingxling/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.
Passed 18 of 21 test cases with the skill, and 11 of 21 without it.
and 9 more in the full report
9 fixed12 passed either way3 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 9 test cases the skill fixed. Same model, same prompt, with and without the skill.
Before running outbound notification commands via Sendblue CLI in a new environment, what CLI command should be executed to verify existing credentials?
| Checked | Without skill | With skill |
|---|---|---|
| Specifies running npx @sendblue/cli whoami. | Missed | Passed |
The instructions your model reads when the skill loads.
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]].
/loop iteration, or /schedule completion.The CLI must be installed and authenticated:
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 account. On the free plan, the contact has to text the Sendblue number once before outbound sends work — confirm with sendblue contacts before relying on notify in an unattended workflow.
Cache the destination number once per project rather than re-asking. A NOTIFY_NUMBER env var or a one-line .notify-number file is fine; defer storage strategy to whatever the surrounding project already does.
Notify is for long, unattended work — not chatter. Good triggers:
/loop and /schedule jobs that produce a discrete result.Bad triggers (do not silently wire these):
test cases passed, vs 11 / 21 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.