add-imessage

النجوم١٠

التفرعات٢

آخر تحديث٢٢ مايو ٢٠٢٦ في ١٩:٤١

Add iMessage channel integration via Chat SDK. Local (macOS) or remote (Photon API) mode.

التثبيت

التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.

المصدر

taslim

taslim/nanoclaw-gws-ea

فتح مستودع GitHub عرض مستودعات المنشئ

تنزيل

المهن ذات الصلةSOC

استنادا إلى تصنيف SOC المهني

مطوّرو البرمجياتمهن الحاسوب والرياضيات·SOC 15-1252

مستكشف الملفات

3 ملفات

SKILL.md

readonly

name	add-imessage
description	Add iMessage channel integration via Chat SDK. Local (macOS) or remote (Photon API) mode.

Add iMessage Channel

Adds iMessage support via the Chat SDK bridge. Two modes: local (macOS with Full Disk Access) or remote (Photon API).

Install

NanoClaw doesn't ship channels in trunk. This skill copies the iMessage adapter in from the channels branch.

Pre-flight (idempotent)

Skip to Credentials if all of these are already in place:

src/channels/imessage.ts exists
src/channels/index.ts contains import './imessage.js';
chat-adapter-imessage is listed in package.json dependencies

Otherwise continue. Every step below is safe to re-run.

1. Fetch the channels branch

git fetch origin channels

2. Copy the adapter

git show origin/channels:src/channels/imessage.ts > src/channels/imessage.ts

3. Append the self-registration import

Append to src/channels/index.ts (skip if the line is already present):

import './imessage.js';

4. Install the adapter package (pinned)

pnpm install chat-adapter-imessage@0.1.1

5. Build

pnpm run build

Credentials

Local Mode (macOS)

Requirements: macOS with Full Disk Access granted to the Node.js binary.

The Node binary path is buried deep (e.g. ~/.nvm/versions/node/v22.x.x/bin/node). To make it easy, open the folder in Finder so the user can drag the file into System Settings:

open "$(dirname "$(which node)")"

Then tell the user:

Open System Settings > Privacy & Security > Full Disk Access
Click +, then drag the node file from the Finder window that just opened
Toggle it on

Stop and wait for the user to confirm before continuing.

Remote Mode (Photon API)

Set up a Photon account
Get your server URL and API key

Configure environment

Local mode -- add to .env:

IMESSAGE_ENABLED=true
IMESSAGE_LOCAL=true

Remote mode -- add to .env:

IMESSAGE_LOCAL=false
IMESSAGE_SERVER_URL=https://your-photon-server.com
IMESSAGE_API_KEY=your-api-key

Sync to container: mkdir -p data/env && cp .env data/env/env

Next Steps

If you're in the middle of /setup, return to the setup flow now.

Otherwise, run /manage-channels to wire this channel to an agent group.

Channel Info

type: imessage
terminology: iMessage has "conversations." Each conversation is with a contact identified by phone number or email address. Group chats are also supported.
how-to-find-id: The platform ID is the contact's phone number (e.g. +15551234567) or email address. For group chats, the ID is assigned by iMessage internally.
supports-threads: no
typical-use: Interactive 1:1 chat — personal messaging
default-isolation: Same agent group if you're the only person messaging the bot across iMessage and other channels. Separate agent group if different contacts should have information isolation.

المزيد من هذا المستودع

نفس المستودع

setup-gws-ea

taslim/nanoclaw-gws-ea

Run Nanoclaw GWS-EA setup. Use when the user wants to install, re-run setup, or import v1 data. Triggers on "setup", "setup gws-ea", "install gws-ea", "import v1", or first-time setup requests on this fork.

2026-05-3010

sync-forks

taslim/nanoclaw-gws-ea

Sync your private fork with public fork(s). Push sanitized changes to a public fork, or pull community contributions back. Triggers on "sync forks", "sync fork", "push to fork", "pull from fork".

2026-05-3010

update-gws-ea

taslim/nanoclaw-gws-ea

Pull community contributions from the nanoclaw-gws-ea public fork back into this private fork, with preview, selective cherry-pick, and low token usage.

2026-05-3010

google-docs

taslim/nanoclaw-gws-ea

Create and edit Google Docs cleanly. Use before any Docs creation or modification — covers the markdown-draft-then-import workflow, structural editing tools, and verification that formatting renders natively (not as literal characters).

2026-05-3010

onecli-gateway

taslim/nanoclaw-gws-ea

OneCLI Gateway: transparent HTTPS proxy that injects stored credentials into outbound calls. You MUST use this skill when the user asks you to read emails, check calendar, access GitHub repos, create issues, check Stripe payments, or interact with ANY external service or API. Do NOT use browser extensions or OAuth CLI tools. Make HTTP requests directly; the gateway injects credentials automatically.

2026-05-3010

relationships

taslim/nanoclaw-gws-ea

Look up and manage who people are and how to engage them. Use before any substantive interaction (scheduling, email, meetings, outreach). Covers Google Contacts as CRM, tier definitions (1–5), and contact-management thresholds.

2026-05-3010

name	add-imessage
description	Add iMessage channel integration via Chat SDK. Local (macOS) or remote (Photon API) mode.

Add iMessage Channel

Adds iMessage support via the Chat SDK bridge. Two modes: local (macOS with Full Disk Access) or remote (Photon API).

Install

NanoClaw doesn't ship channels in trunk. This skill copies the iMessage adapter in from the channels branch.

Pre-flight (idempotent)

Skip to Credentials if all of these are already in place:

src/channels/imessage.ts exists
src/channels/index.ts contains import './imessage.js';
chat-adapter-imessage is listed in package.json dependencies

Otherwise continue. Every step below is safe to re-run.

1. Fetch the channels branch

git fetch origin channels

2. Copy the adapter

git show origin/channels:src/channels/imessage.ts > src/channels/imessage.ts

3. Append the self-registration import

Append to src/channels/index.ts (skip if the line is already present):

import './imessage.js';

4. Install the adapter package (pinned)

pnpm install chat-adapter-imessage@0.1.1

5. Build

pnpm run build

Credentials

Local Mode (macOS)

Requirements: macOS with Full Disk Access granted to the Node.js binary.

The Node binary path is buried deep (e.g. ~/.nvm/versions/node/v22.x.x/bin/node). To make it easy, open the folder in Finder so the user can drag the file into System Settings:

open "$(dirname "$(which node)")"

Then tell the user:

Open System Settings > Privacy & Security > Full Disk Access
Click +, then drag the node file from the Finder window that just opened
Toggle it on

Stop and wait for the user to confirm before continuing.

Remote Mode (Photon API)

Set up a Photon account
Get your server URL and API key

Configure environment

Local mode -- add to .env:

IMESSAGE_ENABLED=true
IMESSAGE_LOCAL=true

Remote mode -- add to .env:

IMESSAGE_LOCAL=false
IMESSAGE_SERVER_URL=https://your-photon-server.com
IMESSAGE_API_KEY=your-api-key

Sync to container: mkdir -p data/env && cp .env data/env/env

Next Steps

If you're in the middle of /setup, return to the setup flow now.

Otherwise, run /manage-channels to wire this channel to an agent group.

Channel Info

type: imessage
terminology: iMessage has "conversations." Each conversation is with a contact identified by phone number or email address. Group chats are also supported.
how-to-find-id: The platform ID is the contact's phone number (e.g. +15551234567) or email address. For group chats, the ID is assigned by iMessage internally.
supports-threads: no
typical-use: Interactive 1:1 chat — personal messaging
default-isolation: Same agent group if you're the only person messaging the bot across iMessage and other channels. Separate agent group if different contacts should have information isolation.