[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M798AVGJSPVVVGZAC1XY61J4":3,"skill-same:01M798AVGJSPVVVGZAC1XY61J4":66},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":46,"commitSha":47,"skillDirectory":48,"forksCount":14,"repositoryHtmlUrl":49,"repositoryHomepageUrl":6,"ownerHtmlUrl":50,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":51,"install":52,"resources":65},"01M798AVGJSPVVVGZAC1XY61J4","sendblue-cli",null,"Send iMessage and SMS from the shell via the @sendblue\u002Fcli npm package — outbound sends, contact management, and account setup with no API client or webhook server required.","Elogic360\u002Fsoftware-factory","Elogic360","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F156535519?v=4","01M74NH3F0RB13PWB7JZDE2V80","elogic360","01M74NH3FPC65082MDZVMFHDM3",0,"MIT","https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fintegrations\u002Fantigravity-skills\u002Fskills\u002Fsendblue\u002Fsendblue-cli\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: sendblue-cli\ndescription: \"Send iMessage and SMS from the shell via the @sendblue\u002Fcli npm package — outbound sends, contact management, and account setup with no API client or webhook server required.\"\ncategory: api-integration\nrisk: critical\nsource: community\nsource_repo: sendblue-api\u002Fsendblue-cli\nsource_type: official\ndate_added: \"2026-05-22\"\nauthor: AnthonyFirth\ntags: [sendblue, imessage, sms, cli, messaging, notifications]\ntools: [claude, cursor, gemini]\nlicense: \"MIT\"\nlicense_source: \"https:\u002F\u002Fgithub.com\u002Fsendblue-api\u002Fsendblue-cli\u002Fblob\u002Fmain\u002FLICENSE\"\nplugin:\n  targets:\n    codex: blocked\n    claude: blocked\n---\n\n# Sendblue CLI\n\n## Overview\n\n`@sendblue\u002Fcli` is a Node CLI that creates a Sendblue account, provisions an iMessage-enabled number, and sends messages. It is the fastest way to text from a shell, script, or Claude Code hook — no API client, no webhook server, no credentials in env vars. Credentials live at `~\u002F.sendblue\u002Fcredentials.json` (mode `600`) and Node.js 18+ is required.\n\n## When to Use This Skill\n\n- Use when the user wants to text a phone number from a script, shell, hook, or agent turn (e.g. \"text me when X finishes\", \"ping my phone\", \"notify on completion\").\n- Use when the user mentions `sendblue` as a CLI\u002Fbinary or asks to set up the `@sendblue\u002Fcli` package.\n- Prefer this skill over [[sendblue-api]] when the work happens in a shell context, one-shot script, cron job, or agent hook.\n- Reach for [[sendblue-api]] instead when writing application code that integrates Sendblue, receiving inbound webhooks, or needing features the CLI does not expose (send styles, reactions, group messages, status callbacks, media uploads).\n\n## How It Works\n\n### Step 1: Install\n\n```bash\nnpm install -g @sendblue\u002Fcli       # global, exposes `sendblue`\n# or one-shot:\nnpx @sendblue\u002Fcli \u003Ccommand>\n```\n\n### Step 2: Set up an account\n\n`sendblue setup` runs interactively by default. For CI\u002Fscripts, run it in two phases — the first call sends an 8-digit verification code by email, the second consumes it.\n\n```bash\nsendblue setup --email you@example.com                                       # sends code\nsendblue setup --email you@example.com --code 12345678 \\\n               --company my-co --contact +15551234567                        # completes setup\n```\n\n| Flag | Notes |\n|---|---|\n| `--email` | Email address |\n| `--code` | 8-digit verification code (from the email) |\n| `--company` | Lowercase, hyphens\u002Funderscores, 3–64 chars |\n| `--contact` | First contact, E.164 |\n\n### Step 3: Send messages\n\n```bash\nsendblue send +15551234567 'Hello from Sendblue!'\nsendblue messages --inbound --limit 20\n```\n\nPhone numbers must be E.164 (`+` + country code + digits, no spaces or dashes).\n\n### Step 4: Manage contacts and plan\n\nOn the free plan, **a contact must text your Sendblue number once before outbound sends to that contact will work**. After `sendblue setup ... --contact +15551234567`, have that contact send any text to the printed Sendblue number, then run `sendblue contacts` to confirm verification.\n\n## Command Reference\n\n| Command | Purpose |\n|---|---|\n| `sendblue setup` | Create account, verify email, set company name, add first contact |\n| `sendblue login` | Log in to an existing account |\n| `sendblue send \u003Cnumber> \u003Cmessage>` | Send an iMessage |\n| `sendblue messages [--inbound\\|--outbound] [-n \u003Cnumber>] [-l \u003Ccount>]` | List recent messages |\n| `sendblue add-contact \u003Cnumber>` | Register a contact |\n| `sendblue contacts` | List contacts and their verification status |\n| `sendblue status` | Account\u002Fplan info |\n| `sendblue whoami` | Show current credentials and verify validity |\n\n## Examples\n\n### Example 1: Notify when a long task finishes\n\n```bash\nlong_running_thing && sendblue send +15551234567 \"✅ done: $(date)\"\n```\n\n### Example 2: Read recent inbound for a specific contact\n\n```bash\nsendblue messages -n +15551234567 --inbound --limit 50\n```\n\n### Example 3: Verify creds are good before a batch send\n\n```bash\nsendblue whoami || sendblue login\n```\n\n### Example 4: Wire to a Claude Code `Stop` hook\n\nTo text yourself at the end of every agent turn, register a `Stop` hook in `settings.json` that shells out to `sendblue send`. Defer the actual hook wiring to [[update-config]] and the trigger logic to [[sendblue-notify]] — this skill only owns the CLI invocation.\n\n## Best Practices\n\n- ✅ **Use E.164 numbers everywhere.** `+15551234567`, never `5551234567` or `(555) 123-4567`.\n- ✅ **Run `sendblue whoami` before unattended batches** to fail fast on stale or missing creds.\n- ✅ **Re-run `setup` as the same OS user** that owns `~\u002F.sendblue\u002Fcredentials.json`.\n- ❌ **Don't `sudo`** — it writes creds to root's home and the next non-sudo run won't see them.\n- ❌ **Don't embed creds in env vars** when the CLI already reads them from the per-user credentials file.\n\n## Limitations\n\n- Outbound-first: there is no built-in webhook server for inbound. Use [[sendblue-api]] webhooks for full inbound handling.\n- The CLI does not expose send styles\u002Feffects, reactions, group messages, status callbacks, media uploads, or the contacts API beyond basic CRUD. Reach for the HTTP API for those.\n- Free-plan accounts require recipient verification before outbound sends succeed.\n\n## Security & Safety Notes\n\n- Credentials are written to `~\u002F.sendblue\u002Fcredentials.json` with mode `600`. Treat that file like an API key — do not commit it, do not copy it across machines without the same posture.\n- Treat every outbound send, contact setup, login, or account setup action as state-changing. Preview the recipient, message body, and account\u002Femail target, then wait for explicit user confirmation before running it.\n- Run the CLI as the OS user that owns the credentials file. `sudo` writes a separate copy under root's home and silently desyncs.\n- Outbound messages to phone numbers are not free of consequence — wire `sendblue send` into hooks or loops only after gating on duration or success conditions to avoid spamming the recipient.\n- Verification codes arrive by email; treat the address you registered with as a recovery factor for the account.\n\n## Common Pitfalls\n\n- **E.164 only.** `5551234567` or `(555) 123-4567` will fail — always `+15551234567`.\n- **Free-plan unverified contacts.** Outbound to a contact that hasn't texted in first returns an error — have them text your Sendblue number once, then confirm with `sendblue contacts`.\n- **Two-step setup in non-interactive mode.** `--email` alone only sends the code; you must run a second invocation with `--code` and the rest of the flags to finish.\n- **Credentials are per-user.** `~\u002F.sendblue\u002Fcredentials.json` is owner-only (`600`). Don't `sudo` and pollute root's home — re-running as the same user that ran `setup` is what works.\n\n## Related Skills\n\n- `@sendblue-api` — HTTP\u002FJSON alternative for application code, webhooks, and features the CLI does not expose.\n- `@sendblue-notify` — Patterns and copy rules for \"text me when X is done\" workflows that sit on top of this CLI.\n- `@update-config` — Wires `sendblue send` into Claude Code hooks (`Stop`, `Notification`) without owning the message logic.\n\n## Links\n\n- README & full flag reference: \u003Chttps:\u002F\u002Fgithub.com\u002Fsendblue-api\u002Fsendblue-cli>\n- Sendblue: \u003Chttps:\u002F\u002Fsendblue.com>\n- API docs (deeper protocol details): \u003Chttps:\u002F\u002Fdocs.sendblue.com>\n","# Sendblue CLI\n\n## Overview\n\n`@sendblue\u002Fcli` is a Node CLI that creates a Sendblue account, provisions an iMessage-enabled number, and sends messages. It is the fastest way to text from a shell, script, or Claude Code hook — no API client, no webhook server, no credentials in env vars. Credentials live at `~\u002F.sendblue\u002Fcredentials.json` (mode `600`) and Node.js 18+ is required.\n\n## When to Use This Skill\n\n- Use when the user wants to text a phone number from a script, shell, hook, or agent turn (e.g. \"text me when X finishes\", \"ping my phone\", \"notify on completion\").\n- Use when the user mentions `sendblue` as a CLI\u002Fbinary or asks to set up the `@sendblue\u002Fcli` package.\n- Prefer this skill over [[sendblue-api]] when the work happens in a shell context, one-shot script, cron job, or agent hook.\n- Reach for [[sendblue-api]] instead when writing application code that integrates Sendblue, receiving inbound webhooks, or needing features the CLI does not expose (send styles, reactions, group messages, status callbacks, media uploads).\n\n## How It Works\n\n### Step 1: Install\n\n```bash\nnpm install -g @sendblue\u002Fcli       # global, exposes `sendblue`\n# or one-shot:\nnpx @sendblue\u002Fcli \u003Ccommand>\n```\n\n### Step 2: Set up an account\n\n`sendblue setup` runs interactively by default. For CI\u002Fscripts, run it in two phases — the first call sends an 8-digit verification code by email, the second consumes it.\n\n```bash\nsendblue setup --email you@example.com                                       # sends code\nsendblue setup --email you@example.com --code 12345678 \\\n               --company my-co --contact +15551234567                        # completes setup\n```\n\n| Flag | Notes |\n|---|---|\n| `--email` | Email address |\n| `--code` | 8-digit verification code (from the email) |\n| `--company` | Lowercase, hyphens\u002Funderscores, 3–64 chars |\n| `--contact` | First contact, E.164 |\n\n### Step 3: Send messages\n\n```bash\nsendblue send +15551234567 'Hello from Sendblue!'\nsendblue messages --inbound --limit 20\n```\n\nPhone numbers must be E.164 (`+` + country code + digits, no spaces or dashes).\n\n### Step 4: Manage contacts and plan\n\nOn the free plan, **a contact must text your Sendblue number once before outbound sends to that contact will work**. After `sendblue setup ... --contact +15551234567`, have that contact send any text to the printed Sendblue number, then run `sendblue contacts` to confirm verification.\n\n## Command Reference\n\n| Command | Purpose |\n|---|---|\n| `sendblue setup` | Create account, verify email, set company name, add first contact |\n| `sendblue login` | Log in to an existing account |\n| `sendblue send \u003Cnumber> \u003Cmessage>` | Send an iMessage |\n| `sendblue messages [--inbound\\|--outbound] [-n \u003Cnumber>] [-l \u003Ccount>]` | List recent messages |\n| `sendblue add-contact \u003Cnumber>` | Register a contact |\n| `sendblue contacts` | List contacts and their verification status |\n| `sendblue status` | Account\u002Fplan info |\n| `sendblue whoami` | Show current credentials and verify validity |\n\n## Examples\n\n### Example 1: Notify when a long task finishes\n\n```bash\nlong_running_thing && sendblue send +15551234567 \"✅ done: $(date)\"\n```\n\n### Example 2: Read recent inbound for a specific contact\n\n```bash\nsendblue messages -n +15551234567 --inbound --limit 50\n```\n\n### Example 3: Verify creds are good before a batch send\n\n```bash\nsendblue whoami || sendblue login\n```\n\n### Example 4: Wire to a Claude Code `Stop` hook\n\nTo text yourself at the end of every agent turn, register a `Stop` hook in `settings.json` that shells out to `sendblue send`. Defer the actual hook wiring to [[update-config]] and the trigger logic to [[sendblue-notify]] — this skill only owns the CLI invocation.\n\n## Best Practices\n\n- ✅ **Use E.164 numbers everywhere.** `+15551234567`, never `5551234567` or `(555) 123-4567`.\n- ✅ **Run `sendblue whoami` before unattended batches** to fail fast on stale or missing creds.\n- ✅ **Re-run `setup` as the same OS user** that owns `~\u002F.sendblue\u002Fcredentials.json`.\n- ❌ **Don't `sudo`** — it writes creds to root's home and the next non-sudo run won't see them.\n- ❌ **Don't embed creds in env vars** when the CLI already reads them from the per-user credentials file.\n\n## Limitations\n\n- Outbound-first: there is no built-in webhook server for inbound. Use [[sendblue-api]] webhooks for full inbound handling.\n- The CLI does not expose send styles\u002Feffects, reactions, group messages, status callbacks, media uploads, or the contacts API beyond basic CRUD. Reach for the HTTP API for those.\n- Free-plan accounts require recipient verification before outbound sends succeed.\n\n## Security & Safety Notes\n\n- Credentials are written to `~\u002F.sendblue\u002Fcredentials.json` with mode `600`. Treat that file like an API key — do not commit it, do not copy it across machines without the same posture.\n- Treat every outbound send, contact setup, login, or account setup action as state-changing. Preview the recipient, message body, and account\u002Femail target, then wait for explicit user confirmation before running it.\n- Run the CLI as the OS user that owns the credentials file. `sudo` writes a separate copy under root's home and silently desyncs.\n- Outbound messages to phone numbers are not free of consequence — wire `sendblue send` into hooks or loops only after gating on duration or success conditions to avoid spamming the recipient.\n- Verification codes arrive by email; treat the address you registered with as a recovery factor for the account.\n\n## Common Pitfalls\n\n- **E.164 only.** `5551234567` or `(555) 123-4567` will fail — always `+15551234567`.\n- **Free-plan unverified contacts.** Outbound to a contact that hasn't texted in first returns an error — have them text your Sendblue number once, then confirm with `sendblue contacts`.\n- **Two-step setup in non-interactive mode.** `--email` alone only sends the code; you must run a second invocation with `--code` and the rest of the flags to finish.\n- **Credentials are per-user.** `~\u002F.sendblue\u002Fcredentials.json` is owner-only (`600`). Don't `sudo` and pollute root's home — re-running as the same user that ran `setup` is what works.\n\n## Related Skills\n\n- `@sendblue-api` — HTTP\u002FJSON alternative for application code, webhooks, and features the CLI does not expose.\n- `@sendblue-notify` — Patterns and copy rules for \"text me when X is done\" workflows that sit on top of this CLI.\n- `@update-config` — Wires `sendblue send` into Claude Code hooks (`Stop`, `Notification`) without owning the message logic.\n\n## Links\n\n- README & full flag reference: \u003Chttps:\u002F\u002Fgithub.com\u002Fsendblue-api\u002Fsendblue-cli>\n- Sendblue: \u003Chttps:\u002F\u002Fsendblue.com>\n- API docs (deeper protocol details): \u003Chttps:\u002F\u002Fdocs.sendblue.com>\n",{"name":5,"risk":24,"tags":25,"tools":32,"author":36,"plugin":37,"source":40,"license":15,"category":41,"date_added":42,"description":7,"source_repo":43,"source_type":44,"license_source":45},"critical",[26,27,28,29,30,31],"sendblue","imessage","sms","cli","messaging","notifications",[33,34,35],"claude","cursor","gemini","AnthonyFirth",{"targets":38},{"codex":39,"claude":39},"blocked","community","api-integration","2026-05-22","sendblue-api\u002Fsendblue-cli","official","https:\u002F\u002Fgithub.com\u002Fsendblue-api\u002Fsendblue-cli\u002Fblob\u002Fmain\u002FLICENSE","main","c475fc64e94e803b50d14a791dfee8853fbb2c5c","integrations\u002Fantigravity-skills\u002Fskills\u002Fsendblue\u002Fsendblue-cli","https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory","https:\u002F\u002Fgithub.com\u002FElogic360","2026-11-08 22:21:22",{"source":8,"skillName":5,"commands":53,"prompt":63,"zipAvailable":64},[54,57,60],{"tool":55,"command":56},"npx","npx skills add Elogic360\u002Fsoftware-factory --skill sendblue-cli",{"tool":58,"command":59},"bunx","bunx skills add Elogic360\u002Fsoftware-factory --skill sendblue-cli",{"tool":61,"command":62},"pnpm","pnpm dlx skills add Elogic360\u002Fsoftware-factory --skill sendblue-cli","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fintegrations\u002Fantigravity-skills\u002Fskills\u002Fsendblue\u002Fsendblue-cli\u002FSKILL.md",true,[],[67,75,82,89,96,103],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":71,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M79G206MT3J6S0GY3C45P2KV","vss-summarize-video","Use to summarize a recorded video via the LVS summarization microservice (HITL-gated) with a VLM fallback. Not for report generation or live RTSP captioning.","Apache-2.0","https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fskills\u002Fnvidia\u002Fvss-summarize-video\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":71,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M79G1WN63PGRE8CKD47WEBQ5","vss-setup-video-analytics-api","Use to deploy the vss-video-analytics-api REST service standalone (config-source, data-log bind, Elasticsearch, optional Kafka). Not for full warehouse deploy.","https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fskills\u002Fnvidia\u002Fvss-setup-video-analytics-api\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":71,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M79G1S9F7VY3EF6H53PRP5AN","vss-setup-behavior-analytics","Use to deploy the vss-behavior-analytics service standalone (entrypoint, config-source, optional calibration). Not for the full warehouse deploy.","https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fskills\u002Fnvidia\u002Fvss-setup-behavior-analytics\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":71,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":19},"01M79G1N1S1Y27PFZPYMNK1MTQ","vss-search-archive","Use this skill to run top-level VSS fusion search on archived video, or to ingest video files \u002F RTSP streams for search. Do NOT use for ad-hoc visual Q&A (use vss-ask-video), live captioning (use vss-deploy-dense-captioning), or video summarization and reports (use vss-summarize-video).","https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fskills\u002Fnvidia\u002Fvss-search-archive\u002FSKILL.md",[],[],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":71,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":19},"01M79G1H6WN0Q6C0VCAXCZX6B7","vss-query-analytics","Use this skill when reading video-analytics metrics, incidents, alerts, and sensor data via the VA-MCP server (port 9901). Not for live VLM or incident-range narrative reports.","https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fskills\u002Fnvidia\u002Fvss-query-analytics\u002FSKILL.md",[],[],{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":71,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":109,"publishedAt":19},"01M79G1DYPNXQS7QHZ0AAF5FX5","vss-manage-video-io-storage","Use to call the VIOS REST API (sensor list, timelines, clip extraction, snapshots, add\u002Fdelete sensors and streams). Not for VLM inference or search.","https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fskills\u002Fnvidia\u002Fvss-manage-video-io-storage\u002FSKILL.md",[],[]]