Configure

anthropics/claude-plugins-official/external_plugins/imessage/skills/configure

by anthropics315c4e48967d9541c29c3c656441dded353ca7aaNo license47K starsListed Nov 20, 2026Updated Nov 20, 2026Repository updated today

Check iMessage channel setup and review access policy. Use when the user asks to configure iMessage, asks "how do I set this up" or "who can reach me," or wants to know why texts aren't reaching the assistant.

FeaturedIncludes scriptsProductivity & Workflow
AI-generated overview

Checks iMessage channel setup — Full Disk Access, access policy and allowlist — and guides the user on who can reach the assistant.

What it does
Reads the local iMessage state and reports it: it tests whether chat.db is readable (Full Disk Access), reads the channel's access.json for DM policy, allowed senders and pending pairings, and ends with a concrete next step. It also walks the user through building an allowlist of phone numbers or emails, and flags or pushes back on the pairing policy because it auto-replies to every contact. It only shows status and guidance; it does not save tokens or change configuration itself.
When to use it
Use when the user asks how to set up iMessage, who can reach them through the assistant, or why incoming texts are not reaching it. Also useful when reviewing or adjusting the channel's access policy.
Requirements
Runs on macOS with access to ~/Library/Messages/chat.db, which requires Full Disk Access for the terminal or IDE. Reads ~/.claude/channels/imessage/access.json. Uses Read and ls via Bash; no token or .env file is needed.

/imessage:configure — iMessage Channel Setup

There's no token to save — iMessage reads ~/Library/Messages/chat.db directly. This skill checks whether that works and orients the user on access policy.

Arguments passed: $ARGUMENTS (unused — this skill only shows status)


Status and guidance

Read state and give the user a complete picture:

  1. Full Disk Access — run ls ~/Library/Messages/chat.db. If it fails with "Operation not permitted", FDA isn't granted. Say: "Grant Full Disk Access to your terminal (or IDE if that's where Claude Code runs): System Settings → Privacy & Security → Full Disk Access. The server can't read chat.db without it."

  2. Access — read ~/.claude/channels/imessage/access.json (missing file = defaults: dmPolicy: "allowlist", empty allowlist). Show:

    • DM policy and what it means in one line
    • Allowed senders: count, and list the handles
    • Pending pairings: count, with codes if any (only if policy is pairing)
  3. What next — end with a concrete next step based on state:

    • FDA not granted → the FDA instructions above
    • FDA granted, policy is allowlist → "Text yourself from any device signed into your Apple ID — self-chat always bypasses the gate. To let someone else through: /imessage:access allow +15551234567."
    • FDA granted, someone allowed → "Ready. Self-chat works; {N} other sender(s) allowed."

Build the allowlist — don't pair

iMessage reads your personal chat.db. You already know the phone numbers and emails of people you'd allow — there's no ID-capture problem to solve. Pairing has no upside here and a clear downside: every contact who texts this Mac gets an unsolicited auto-reply.

Drive the conversation this way:

  1. Read the allowlist. Tell the user who's in it (self-chat always works regardless).
  2. Ask: "Besides yourself, who should be able to text you through this?"
  3. "Nobody, just me" → done. The default allowlist with an empty list is correct. Self-chat bypasses the gate.
  4. "My partner / a friend / a couple people" → ask for each handle (phone like +15551234567 or email like [email protected]) and offer to run /imessage:access allow <handle> for each. Stay on allowlist.
  5. Current policy is pairing → flag it immediately: "Your policy is pairing, which auto-replies a code to every contact who texts this Mac. Switch back to allowlist?" and offer /imessage:access policy allowlist. Don't wait to be asked.
  6. User asks for pairing → push back. Explain the auto-reply-to- everyone consequence. If they insist and confirm a dedicated line with few contacts, fine — but treat it as a one-off, not a recommendation.

Handles are +15551234567 or [email protected]. disabled drops everything except self-chat.


Implementation notes

  • No .env file for this channel. No token. The only OS-level setup is FDA plus the one-time Automation prompt when the server first sends (which can't be checked from here).
  • access.json is re-read on every inbound message — policy changes via /imessage:access take effect immediately, no restart.

Source and attribution

Source:anthropics/claude-plugins-officialinexternal_plugins/imessage/skills/configureat commit315c4e4

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Add a badge to your README

Show readers this skill is listed on SourceWeft. The badge links to this page.

Preview of the “Listed on SourceWeft” badge
[![Listed on SourceWeft](https://sourceweft.com/badge/skills/gh-anthropics-claude-plugins-official-configure-external-plugins-imessage-skills-configure-0fbd86a6aa45945f.svg)](https://sourceweft.com/skills/gh-anthropics-claude-plugins-official-configure-external-plugins-imessage-skills-configure-0fbd86a6aa45945f?utm_source=readme&utm_medium=badge)

Report or request removal