imsg

iMessage/SMS CLI for listing chats, reading message history, watching for new messages, and sending messages. Triggers on: check messages, read imessage, send text, imsg, message history, sms, who texted me.

2.63x

Quality

89%

Does it follow best practices?

Impact

100%

2.63x

Average score across 3 eval scenarios

Securityby

Advisory

Suggest reviewing before use

Quality

Content

79%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a well-crafted, concise skill that provides fully actionable CLI commands with important operational nuances (optimistic send semantics, permission requirements). Its main weakness is the lack of an explicit multi-step workflow with validation checkpoints for the send operation, which is effectively irreversible. The structure is clean but the safety guidance could be formalized into a sequenced pre-send checklist.

Suggestions

Add an explicit sequenced workflow for sending messages, e.g.: 1. Look up recipient via `imsg chats`, 2. Verify chat-id with `imsg history`, 3. Confirm recipient/text, 4. Send, 5. Check for delivery errors.

Consider adding a troubleshooting subsection or reference for common permission errors (Full Disk Access denied, Automation permission missing) with specific error messages and fixes.

Dimension	Reasoning	Score
Conciseness	Every section is lean and purposeful. No unnecessary explanations of what iMessage is or how CLIs work. The delivery notes section adds genuinely non-obvious information (optimistic send semantics, permission nuances). Every token earns its place.	3 / 3
Actionability	All commands are fully executable and copy-paste ready with clear flag usage. Multiple send variants (email, phone, attachment) are shown with concrete examples. The setup section specifies exact permissions needed.	3 / 3
Workflow Clarity	The Safety section mentions 'Read-only by default — use chats and history before sending' and 'Always confirm recipient and message text before imsg send', but there's no explicit sequenced workflow with validation checkpoints. For a send operation that is destructive (messages can't be unsent), a clearer step-by-step workflow with verification (e.g., confirm chat-id via history before sending) would be warranted.	2 / 3
Progressive Disclosure	References to USER.md for contact details are well-signaled, and the ADR-0067 mention provides provenance. However, with no bundle files, the skill is essentially self-contained. The content is well-organized with clear sections but could benefit from separating the setup/permissions details or linking to a troubleshooting guide for permission errors.	2 / 3
	Total	10 / 12 Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is a strong skill description that clearly communicates what the skill does (iMessage/SMS CLI operations) and when to use it (with explicit trigger terms). The trigger terms are natural and cover multiple variations of how users might request messaging functionality. The description is concise, specific, and well-differentiated from other potential skills.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: 'listing chats, reading message history, watching for new messages, and sending messages.' These are clear, actionable capabilities.	3 / 3
Completeness	Clearly answers both 'what' (iMessage/SMS CLI for listing chats, reading history, watching, sending) and 'when' (explicit 'Triggers on:' clause with specific trigger terms).	3 / 3
Trigger Term Quality	Excellent coverage of natural trigger terms users would say: 'check messages', 'read imessage', 'send text', 'imsg', 'message history', 'sms', 'who texted me' — these cover common variations and natural phrasing.	3 / 3
Distinctiveness Conflict Risk	Very distinct niche — iMessage/SMS messaging is a specific domain unlikely to conflict with other skills. The trigger terms like 'imessage', 'sms', 'who texted me' are highly distinctive.	3 / 3
	Total	12 / 12 Passed

Validation

90%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: joelhooks/joelclaw
Commit: 2ca3686

Reviewed: 10 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.