[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M698R80GQ7NAQC84AGFP1391":3,"skill-same:01M698R80GQ7NAQC84AGFP1391":54},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":25,"linkOnly":26,"markdownContent":27,"markdownBody":28,"frontMatter":29,"refName":30,"commitSha":31,"skillDirectory":32,"forksCount":33,"repositoryHtmlUrl":34,"repositoryHomepageUrl":35,"ownerHtmlUrl":36,"ownerBlogUrl":37,"ownerDescription":38,"updatedAt":39,"install":40,"resources":53},"01M698R80GQ7NAQC84AGFP1391","imsg",null,"iMessage\u002FSMS: local history, contacts, live watch, and requested sends.","openclaw\u002Fimsg","openclaw","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F252820863?v=4","01M698P3FSAZ6B4R928ZF19KPT","01M698R4MMJ5ZXB7KVEP27XM3G",1411,"MIT","https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fimsg\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fimsg\u002FSKILL.md",[],[5,18,19,20,21,22,23,24],"imessage","history","local","live","watch","sms","contacts","2026-11-10 10:12:30",false,"---\nname: imsg\ndescription: \"iMessage\u002FSMS: local history, contacts, live watch, and requested sends.\"\n---\n\n# imsg\n\n`imsg` reads `~\u002FLibrary\u002FMessages\u002Fchat.db` directly and sends through Messages.app automation. Reading is local and safe. **Sending, reacting, marking read, typing indicators, and any chat mutation require an explicit user request** — confirm recipient, service, and content in your final summary.\n\n## Ground rules\n\n- Every read command supports `--json` and emits **NDJSON** (one object per line). Pipe to `jq -s` to get an array. Stdout carries only JSON; progress and warnings go to stderr.\n- Two capability tiers:\n  - **Standard** (normal permissions): `chats`, `group`, `history`, `watch`, `search`, `send`, `react`, `nickname --local`, `account --local`, `whois --local`.\n  - **Bridge** (SIP disabled + `imsg launch` dylib injection): `send-rich`, `send-multipart`, `send-attachment`, `send-sticker`, `tapback`, `poll`, `edit`, `unsend`, `delete-message`, `read`, `typing`, `notify-anyways`, `chat-*`, `name-photo`, and default-mode `account`\u002F`whois`\u002F`nickname`.\n- Check availability with `imsg status --json` before using bridge commands. Stickers additionally require `send.sticker` in `rpc_methods` and `selectors.stickerSend`; attaching one requires `selectors.stickerAttach`, and placing it with `--x`\u002F`--y`\u002F`--scale`\u002F`--rotation` requires `selectors.stickerPlacement`. If the bridge is down, use a standard command only when it preserves the requested semantics; otherwise stop and explain. Never turn a reply\u002Feffect\u002Fsubject into a plain send or a GUID-targeted tapback into `react`, and never suggest disabling SIP unprompted.\n- Full command and flag reference: `imsg completions llm`.\n\n## Preconditions\n\n```bash\nimsg status --json                                        # feature availability + setup hints\nsqlite3 ~\u002FLibrary\u002FMessages\u002Fchat.db 'pragma quick_check;'  # fails => terminal lacks Full Disk Access\n```\n\n## Reading\n\nResolve a person visible in the Messages.app UI from `chats`, not `search`. The UI name usually surfaces as `contact_name` (Contacts permission); it does not appear in `imsg search` results, raw `message.text`, or the DB `handle` table. **No search hits is not proof the contact doesn't exist.**\n\n```bash\nimsg chats --limit 200 --json | jq -s '.[] | select((.contact_name \u002F\u002F .display_name \u002F\u002F .name \u002F\u002F .identifier \u002F\u002F \"\" | ascii_downcase) | contains(\"beatrix\"))'\nimsg chats --unread-only --json | jq -s\n```\n\nThen inspect and read the chat by rowid:\n\n```bash\nimsg group --chat-id ID --json                 # identity + participants; check before automating\nimsg history --chat-id ID --limit 50 --json | jq -s\nimsg history --chat-id ID --start 2025-01-01T00:00:00Z --end 2025-02-01T00:00:00Z --json\nimsg stats --chat-id ID --time-zone UTC --media --json  # logical message + media totals\nimsg scheduled list --json                    # future Send Later rows; read-only\nimsg chat-background status --chat-id ID --json  # inspect local background state; read-only\nimsg name-photo status --chat GUID --json          # read-only Share Name & Photo eligibility\n```\n\n- Chat `id` is the `chat.db` rowid: stable on one machine, the preferred `--chat-id` handle. `identifier` and `guid` are portable across machines.\n- `--start` is inclusive, `--end` exclusive; both take ISO8601. Use absolute timestamps for date-scoped questions.\n- `--attachments` adds attachment metadata; `--convert-attachments` converts CAF→M4A \u002F GIF→PNG for model consumption.\n- `imsg search --query \"pizza tonight\" --json` searches message bodies only (`--match contains` default, `exact` available).\n- `imsg stats [--chat-id ID] [--time-zone IANA] [--media] --json` aggregates logical messages by chat, inbound sender, service, and local date; no bridge required.\n- Chat-list JSON includes `unread_count`. Inbound message payloads include `is_read` and, when read, `date_read`; outbound payloads omit both.\n- SIP-free lookups: `imsg whois --address \"+15551234567\" --type phone --local`, `imsg nickname --address \"+15551234567\" --local --json`, `imsg account --local --json`. Note `nickname --local` returns *your* AddressBook label for the handle; the iMessage-shared nickname needs default-mode `nickname` via the bridge.\n- Direct `sqlite3` queries are a last resort; the `handle` table lacks the resolved names `imsg chats` provides.\n\n## Streaming\n\n```bash\nimsg watch --chat-id ID --json                 # filesystem events with polling fallback\nimsg watch --since-rowid N --json              # resume from a message id cursor\n```\n\nMessage `id` doubles as the watch cursor: persist the last-seen id and pass it back via `--since-rowid`. Add `--reactions` for tapback add\u002Fremove events and `--attachments` for attachment metadata.\n\n## Sending (explicit request only)\n\n```bash\nimsg send --to \"+15551234567\" --text \"message\" --service auto\nimsg send --chat-id ID --text \"message\"        # prefer for groups: no address ambiguity\nimsg send --to \"+15551234567\" --file ~\u002FDesktop\u002Fpic.jpg\nimsg name-photo share --chat GUID                  # shares YOUR Name & Photo; explicit request only\nimsg name-photo set --first-name NAME --photo PATH # replaces YOUR Name & Photo; explicit request only\n```\n\n`name-photo set` replaces the account-wide profile. Never run it implicitly during startup,\nstatus, discovery, or to repair a missing profile. Omitting a last name or photo removes it;\nonly invoke the setter with the user's explicit identity-change request.\n\n- `--service auto` prefers iMessage and falls back to SMS for text-only phone sends; `--no-sms-fallback` disables that.\n- `imsg react --chat-id ID --reaction like` (AppleScript) only targets the **most recent incoming message** and needs Accessibility permission. To react to a specific message by GUID, use bridge `tapback`.\n- `name-photo share` is not a vCard send. It discloses the local Messages Name & Photo to every participant in the selected chat; confirm the destination and explicit user intent before invoking it.\n\n## Bridge extras\n\nOnly after `imsg status` confirms the bridge is loaded (`imsg launch` injects it; refuses when SIP is on; macOS 26 entitlement gates can block features even with SIP off):\n\n```bash\nimsg send-rich --chat 'iMessage;-;+15551234567' --text 'hi' --reply-to MSG_GUID   # replies, effects, subjects\nimsg send-sticker --chat GUID --file ~\u002FPictures\u002Fsticker.png --attach-to MSG_GUID --target-part 0\nimsg send-sticker --chat GUID --file ~\u002FPictures\u002Fsticker.png --attach-to MSG_GUID --x 0.9 --y 0.1 --scale 0.5 --rotation 15\nimsg send-rich --chat 'iMessage;-;+15551234567' --url https:\u002F\u002Fimsg.sh\nimsg poll send --chat GUID --question 'Dinner?' --option 'Pizza' --option 'Sushi' --comment 'Vote by 5pm'\nimsg poll unvote --chat GUID --poll POLL_GUID --option-index 1\nimsg edit --chat GUID --message MSG_GUID --new-text 'updated'                     # macOS 13+\nimsg chat-create --addresses '+15551234567,+15559876543' --name 'Crew'\n```\n\n`poll send` echoes `--question` as a best-effort plain caption after the Polls balloon; `--comment` overrides that caption. Do not retry automatically when only the caption fails: the poll may already be delivered. `history` and `watch` backfill a title-less inbound native poll's `poll.question` from its clean caption row.\n\nDestructive bridge commands — `unsend`, `delete-message`, `chat-delete`, `chat-leave`, `chat-remove-member` — need per-action user confirmation.\n\n## Verification\n\nFor repo edits:\n\n```bash\nmake test\nmake build\n.\u002Fbin\u002Fimsg chats --limit 3 --json | jq -s      # live read proof against the local DB\n```\n","# imsg\n\n`imsg` reads `~\u002FLibrary\u002FMessages\u002Fchat.db` directly and sends through Messages.app automation. Reading is local and safe. **Sending, reacting, marking read, typing indicators, and any chat mutation require an explicit user request** — confirm recipient, service, and content in your final summary.\n\n## Ground rules\n\n- Every read command supports `--json` and emits **NDJSON** (one object per line). Pipe to `jq -s` to get an array. Stdout carries only JSON; progress and warnings go to stderr.\n- Two capability tiers:\n  - **Standard** (normal permissions): `chats`, `group`, `history`, `watch`, `search`, `send`, `react`, `nickname --local`, `account --local`, `whois --local`.\n  - **Bridge** (SIP disabled + `imsg launch` dylib injection): `send-rich`, `send-multipart`, `send-attachment`, `send-sticker`, `tapback`, `poll`, `edit`, `unsend`, `delete-message`, `read`, `typing`, `notify-anyways`, `chat-*`, `name-photo`, and default-mode `account`\u002F`whois`\u002F`nickname`.\n- Check availability with `imsg status --json` before using bridge commands. Stickers additionally require `send.sticker` in `rpc_methods` and `selectors.stickerSend`; attaching one requires `selectors.stickerAttach`, and placing it with `--x`\u002F`--y`\u002F`--scale`\u002F`--rotation` requires `selectors.stickerPlacement`. If the bridge is down, use a standard command only when it preserves the requested semantics; otherwise stop and explain. Never turn a reply\u002Feffect\u002Fsubject into a plain send or a GUID-targeted tapback into `react`, and never suggest disabling SIP unprompted.\n- Full command and flag reference: `imsg completions llm`.\n\n## Preconditions\n\n```bash\nimsg status --json                                        # feature availability + setup hints\nsqlite3 ~\u002FLibrary\u002FMessages\u002Fchat.db 'pragma quick_check;'  # fails => terminal lacks Full Disk Access\n```\n\n## Reading\n\nResolve a person visible in the Messages.app UI from `chats`, not `search`. The UI name usually surfaces as `contact_name` (Contacts permission); it does not appear in `imsg search` results, raw `message.text`, or the DB `handle` table. **No search hits is not proof the contact doesn't exist.**\n\n```bash\nimsg chats --limit 200 --json | jq -s '.[] | select((.contact_name \u002F\u002F .display_name \u002F\u002F .name \u002F\u002F .identifier \u002F\u002F \"\" | ascii_downcase) | contains(\"beatrix\"))'\nimsg chats --unread-only --json | jq -s\n```\n\nThen inspect and read the chat by rowid:\n\n```bash\nimsg group --chat-id ID --json                 # identity + participants; check before automating\nimsg history --chat-id ID --limit 50 --json | jq -s\nimsg history --chat-id ID --start 2025-01-01T00:00:00Z --end 2025-02-01T00:00:00Z --json\nimsg stats --chat-id ID --time-zone UTC --media --json  # logical message + media totals\nimsg scheduled list --json                    # future Send Later rows; read-only\nimsg chat-background status --chat-id ID --json  # inspect local background state; read-only\nimsg name-photo status --chat GUID --json          # read-only Share Name & Photo eligibility\n```\n\n- Chat `id` is the `chat.db` rowid: stable on one machine, the preferred `--chat-id` handle. `identifier` and `guid` are portable across machines.\n- `--start` is inclusive, `--end` exclusive; both take ISO8601. Use absolute timestamps for date-scoped questions.\n- `--attachments` adds attachment metadata; `--convert-attachments` converts CAF→M4A \u002F GIF→PNG for model consumption.\n- `imsg search --query \"pizza tonight\" --json` searches message bodies only (`--match contains` default, `exact` available).\n- `imsg stats [--chat-id ID] [--time-zone IANA] [--media] --json` aggregates logical messages by chat, inbound sender, service, and local date; no bridge required.\n- Chat-list JSON includes `unread_count`. Inbound message payloads include `is_read` and, when read, `date_read`; outbound payloads omit both.\n- SIP-free lookups: `imsg whois --address \"+15551234567\" --type phone --local`, `imsg nickname --address \"+15551234567\" --local --json`, `imsg account --local --json`. Note `nickname --local` returns *your* AddressBook label for the handle; the iMessage-shared nickname needs default-mode `nickname` via the bridge.\n- Direct `sqlite3` queries are a last resort; the `handle` table lacks the resolved names `imsg chats` provides.\n\n## Streaming\n\n```bash\nimsg watch --chat-id ID --json                 # filesystem events with polling fallback\nimsg watch --since-rowid N --json              # resume from a message id cursor\n```\n\nMessage `id` doubles as the watch cursor: persist the last-seen id and pass it back via `--since-rowid`. Add `--reactions` for tapback add\u002Fremove events and `--attachments` for attachment metadata.\n\n## Sending (explicit request only)\n\n```bash\nimsg send --to \"+15551234567\" --text \"message\" --service auto\nimsg send --chat-id ID --text \"message\"        # prefer for groups: no address ambiguity\nimsg send --to \"+15551234567\" --file ~\u002FDesktop\u002Fpic.jpg\nimsg name-photo share --chat GUID                  # shares YOUR Name & Photo; explicit request only\nimsg name-photo set --first-name NAME --photo PATH # replaces YOUR Name & Photo; explicit request only\n```\n\n`name-photo set` replaces the account-wide profile. Never run it implicitly during startup,\nstatus, discovery, or to repair a missing profile. Omitting a last name or photo removes it;\nonly invoke the setter with the user's explicit identity-change request.\n\n- `--service auto` prefers iMessage and falls back to SMS for text-only phone sends; `--no-sms-fallback` disables that.\n- `imsg react --chat-id ID --reaction like` (AppleScript) only targets the **most recent incoming message** and needs Accessibility permission. To react to a specific message by GUID, use bridge `tapback`.\n- `name-photo share` is not a vCard send. It discloses the local Messages Name & Photo to every participant in the selected chat; confirm the destination and explicit user intent before invoking it.\n\n## Bridge extras\n\nOnly after `imsg status` confirms the bridge is loaded (`imsg launch` injects it; refuses when SIP is on; macOS 26 entitlement gates can block features even with SIP off):\n\n```bash\nimsg send-rich --chat 'iMessage;-;+15551234567' --text 'hi' --reply-to MSG_GUID   # replies, effects, subjects\nimsg send-sticker --chat GUID --file ~\u002FPictures\u002Fsticker.png --attach-to MSG_GUID --target-part 0\nimsg send-sticker --chat GUID --file ~\u002FPictures\u002Fsticker.png --attach-to MSG_GUID --x 0.9 --y 0.1 --scale 0.5 --rotation 15\nimsg send-rich --chat 'iMessage;-;+15551234567' --url https:\u002F\u002Fimsg.sh\nimsg poll send --chat GUID --question 'Dinner?' --option 'Pizza' --option 'Sushi' --comment 'Vote by 5pm'\nimsg poll unvote --chat GUID --poll POLL_GUID --option-index 1\nimsg edit --chat GUID --message MSG_GUID --new-text 'updated'                     # macOS 13+\nimsg chat-create --addresses '+15551234567,+15559876543' --name 'Crew'\n```\n\n`poll send` echoes `--question` as a best-effort plain caption after the Polls balloon; `--comment` overrides that caption. Do not retry automatically when only the caption fails: the poll may already be delivered. `history` and `watch` backfill a title-less inbound native poll's `poll.question` from its clean caption row.\n\nDestructive bridge commands — `unsend`, `delete-message`, `chat-delete`, `chat-leave`, `chat-remove-member` — need per-action user confirmation.\n\n## Verification\n\nFor repo edits:\n\n```bash\nmake test\nmake build\n.\u002Fbin\u002Fimsg chats --limit 3 --json | jq -s      # live read proof against the local DB\n```\n",{"name":5,"description":7},"main","fdd51c4874d25469127f8d65a2e047bb7df224f5",".agents\u002Fskills\u002Fimsg",199,"https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fimsg","https:\u002F\u002Fimsg.sh","https:\u002F\u002Fgithub.com\u002Fopenclaw","https:\u002F\u002Fopenclaw.ai","Your personal, open source AI assistant.","2026-11-14 16:16:35",{"source":8,"skillName":5,"commands":41,"prompt":51,"zipAvailable":52},[42,45,48],{"tool":43,"command":44},"npx","npx skills add openclaw\u002Fimsg --skill imsg",{"tool":46,"command":47},"bunx","bunx skills add openclaw\u002Fimsg --skill imsg",{"tool":49,"command":50},"pnpm","pnpm dlx skills add openclaw\u002Fimsg --skill imsg","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fimsg\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fimsg\u002FSKILL.md",true,[],[55],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":25},"01M698R6FS1EDAC8FTWK2KZW6F","crabbox","Use the Crabbox wrapper for OpenClaw remote validation across Linux, macOS, Windows, and WSL2, including delegated Blacksmith Testbox proof. Report the actual provider and id.","https:\u002F\u002Fgithub.com\u002Fopenclaw\u002Fimsg\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fcrabbox\u002FSKILL.md",[],[57,62,63,64,65,66,67,68,69,70,71,72,73,74,75,76,9],"Wrapper","for","openclaw remote","remote","blacksmith testbox","proof","id","across","provider","use","validation","report","windows","linux","macos"]