Agent skill

add-imessage

Add iMessage to NanoClaw — one channel, two backends. Local (this Mac's chat.db via the Chat SDK bridge; macOS + Full Disk Access) or Hosted iMessage (via photon.codes — native spectrum-ts with a device-login wizard; any OS, no Mac relay). Triggers on "add imessage", "connect imessage", "add photon", "imessage via photon", "native imessage".

NanoCo30,389★ · +78/wk · 1 repos on radarProfile →
claude-codeMIT
Install
npx skills add nanocoai/nanoclaw --skill add-imessage --agent claude-code

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

Facts
Files in the skill folder: 4
SKILL.md size: 13 KB
Bundled scripts: none
Path: .claude/skills/add-imessage/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 30,426 · +37 this week
Language: TypeScript
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

# Add iMessage NanoClaw talks to iMessage through a single **`imessage`** channel with two pluggable backends: - **Local (this Mac)** — the Chat SDK bridge over `chat-adapter-imessage`, reading this Mac's signed-in iMessage account (`chat.db`). macOS only; the Node binary needs Full Disk Access. - **Hosted iMessage (via photon.codes)** — a native adapter over Photon's `spectrum-ts` gRPC stream. The hosted service owns the iMessage line, so there's no Mac relay, webhook, or public URL. Works on any OS, and a device-login flow provisions everything for you. Both register the same `imessage` channel type; only one runs per install. NanoClaw doesn't ship channels in trunk — this skill copies the unified `imessage` adapter in from the `channels` branch. Full reference: [docs/imessage.md](docs.md). The mechanical steps under **Apply** carry `nc:` directive fences: an agent reads the prose and applies them, and a parser can apply them deterministically from the same document. Every directive is idempotent, so the whole skill is safe to re-run; anything a parser can't apply falls back to the prose beside it. ## Apply ### 1. Choose a backend Pick the backend first — it decides which package

What's inside
Steps it walks through
  1. Apply
  2. 1. Choose a backend
  3. 2. Copy the adapter
  4. 3. Register the adapter
  5. 4. Install the chosen backend's package
  6. 5. Build and validate
  7. Local backend: Full Disk Access (macOS)
  8. Hosted backend: device login (via photon.codes)
  9. Restart
  10. Resolve your iMessage handle
  11. Next Steps
  12. Channel Info
  13. Hosted features
  14. Troubleshooting
Ships with 3 files
  • REMOVE.md
  • apply-fixtures.json
  • docs.md
More from nanoclaw
All skills →
About this skill
What does the add-imessage skill do?

Add iMessage to NanoClaw — one channel, two backends. Local (this Mac's chat.db via the Chat SDK bridge; macOS + Full Disk Access) or Hosted iMessage (via photon.codes — native spectrum-ts with a device-login wizard; any OS, no Mac relay). Triggers on "add imessage", "connect imessage", "add photon", "imessage via photon", "native imessage".

How do I install it?

Run `npx skills add nanocoai/nanoclaw --skill add-imessage --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 nanocoai/nanoclaw, a repository with 30,426 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