imsg

List and manage iMessage/SMS chats and history on macOS.

Updated Feb 8, 2026
One-click install
npx skills add https://github.com/nomad3/openclaw-k8s --skill imsg-nomad3
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: imsg
Source: https://github.com/nomad3/openclaw-k8s/tree/main/package/skills/imsg
Command: npx skills add https://github.com/nomad3/openclaw-k8s --skill imsg-nomad3

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It removes the friction of managing iMessage/SMS chats through a terminal-friendly workflow, so you can list conversations, review history, and send messages without constantly switching apps.

Core Features & Use Cases

  • Chat discovery and listing: Enumerate your Messages chats to find the correct chat or recipient identifiers.
  • History retrieval and attachment support: Pull recent message history for a selected chat, including optional attachment metadata.
  • Live watch and message sending: Stream incoming messages and send new texts or media to a specific recipient.

Quick Start

Send an iMessage or SMS from your Mac by telling the imsg skill: "Send an SMS to +14155551212 saying 'hi' and attach /path/pic.jpg."

Frequently Asked Questions about imsg

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I send an iMessage or SMS from the macOS terminal?

You can send an iMessage or SMS from the macOS terminal by running a command-line instruction that specifies the recipient's phone number, message text, and optional file paths for attachments. This process routes the delivery directly through the Messages app.

Can I list and find iMessage chat IDs using a command-line interface?

Listing iMessage chats via a command-line interface enumerates your active Messages conversations, allowing you to locate the specific chat identifiers or recipient phone numbers needed for message history retrieval and sending texts.

How do I retrieve iMessage chat history and attachment metadata on macOS?

Retrieving iMessage chat history on macOS involves pulling recent conversation context for a selected chat identifier. This process can also extract and display optional attachment metadata associated with the messages in that specific conversation.

Does the iMessage CLI workflow require Messages.app to be signed in on macOS?

Yes, the iMessage CLI workflow requires a macOS environment with the Messages application actively signed in. Terminal access is also necessary to control the Messages app for executing chat discovery, live updates, and delivery actions.

Can I watch and stream incoming iMessage texts live in the terminal?

Watching incoming iMessage texts live in the terminal streams new messages from a high-signal chat directly to your command-line interface. This allows continuous monitoring of conversations without needing to switch back to the Messages app.

What are the limitations of automating messaging through a macOS CLI?

Automating messaging through a macOS CLI is limited by its dependency on the local macOS environment and an actively signed-in Messages app. It cannot execute delivery actions or access chat histories if the native Messages application is disconnected or offline.