菜单
Sync your iMessage history — builds the dataset on first run, updates incrementally after that. Use this to make sure your data is current before analysing.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use the imessage-analysis MCP server to answer questions about the user's iMessage history.
Compare your messaging activity between two time periods — volume, contacts, and trends side by side.
Analyse your group chat activity — most active groups, top talkers per group, and activity over time.
Check whether imessage-analysis is installed and the MCP server is registered, and fix anything that's missing.
Show the current status of the iMessage analysis dataset — last sync time, total messages, and whether it's up to date.
Summarise your most recent message exchanges — who you've been talking to, what topics came up, and the overall tone of recent activity.
| name | sync |
| description | Sync your iMessage history — builds the dataset on first run, updates incrementally after that. Use this to make sure your data is current before analysing. |
Build or update your message dataset so it's ready to query.
status shows stale or missing datastatus()
Report what you find:
sync()
This is safe to call at any time — it does nothing if already current, and only processes new messages if stale.
Call status() again and report the result:
The MCP server doesn't have access to ~/Library/Messages/chat.db. This requires Full Disk Access for the app running the MCP server (Claude Desktop, Claude Code, or your terminal).
Guide the user:
To fix this, grant Full Disk Access to the app you're using: System Settings → Privacy & Security → Full Disk Access Add Claude Desktop, Claude Code, or your terminal application, then try again.
Alternatively, the user can run imessage-analysis sync once from a terminal that already has Full Disk Access — after that, the dataset exists and queries will work without special permissions.