imsg

List and send iMessage/SMS messages via a macOS command-line interface.

52|3|Updated Apr 3, 2026
One-click install
npx skills add https://github.com/Zhow01/SkillAttack --skill imsg-zhow01
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: imsg
Source: https://github.com/Zhow01/SkillAttack/tree/main/data/hot100skills/036_steipete_imsg
Command: npx skills add https://github.com/Zhow01/SkillAttack --skill imsg-zhow01

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

CLI access to iMessage/SMS on macOS to list chats, view history, watch for updates, and send messages without switching apps.

Core Features & Use Cases

  • List chats and read message history across conversations
  • Watch chats for new messages and automate replies
  • Send messages to contacts from scripts or automation tools

Quick Start

Install imsg and run a sample command to list your chats.

Frequently Asked Questions about imsg

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

FAQPage Schema
How do I send iMessage or SMS texts from a command-line interface on macOS?

You can send iMessage or SMS texts via a command-line interface on macOS to automate daily messaging workflows. This requires macOS Messages.app access, automation permissions, and a signed environment with the imsg binary installed via Homebrew.

Can I automate iMessage replies when new messages arrive on my Mac?

Yes, you can automate iMessage replies by watching chats for new messages via the CLI. This allows you to script automated responses and integrate chat actions directly into your macOS automation tools without switching apps.

How do I read and audit iMessage chat history using the terminal?

To read and audit iMessage chat history using the terminal, you can use a macOS CLI tool to list chats and view message history across conversations. This enables efficient auditing directly from your command line.

What permissions do I need to manage iMessage conversations via a CLI script?

Managing iMessage conversations via a CLI script requires macOS Messages.app access and explicit automation permissions. You also need a signed environment with the imsg binary installed via Homebrew or an equivalent package manager.

Are there limitations to automating iMessage workflows from the command line?

Automating iMessage workflows from the command line is limited to macOS environments with Messages.app access. It requires proper automation permissions and a signed environment, restricting use on non-macOS systems or unsigned scripts.