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

91%

Does it follow best practices?

Impact

100%

2.63x

Average score across 3 eval scenarios

Securityby

Low

Low-risk findings worth noting

Quality

Content

83%Weight 40%Scale 1-5

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

The skill body is concise, executable, and well-structured, providing copy-paste-ready commands for every common case. Its main weakness is the lack of an explicit validation/confirmation checkpoint around the destructive `send` operation, which caps workflow clarity.

Suggestions

Add an explicit pre-send validation step to the Send section (e.g., 'Before running `imsg send`, restate the resolved recipient and message text and confirm with the user') so the destructive operation has a concrete checkpoint.

Add a brief post-send verification note tying the 'sent' return value to checking Messages.app for 'Not delivered', giving a feedback loop for send failures.

Consider a short numbered workflow (read -> confirm -> send) so the intended sequencing is an explicit checklist rather than implied by separate sections.

Dimension	Reasoning	Score
Conciseness	The body is lean with no padding and does not explain concepts Claude already knows; every line is a command, a permission note, or safety guidance that earns its place, matching the lean-and-efficient anchor.	5 / 5
Actionability	Each section gives fully executable, copy-paste-ready `imsg` commands with real flags and the common send variants (email, phone, attachment), covering the common cases.	5 / 5
Workflow Clarity	Sections are sequenced and safety guidance exists, but `imsg send` is a destructive/outward-facing operation whose only safeguard is soft advice ('Always confirm recipient and message text') with no explicit validation checkpoint, so the destructive-operation cap of 3 applies.	3 / 5
Progressive Disclosure	Content is well-organized into clearly signaled sections with appropriate single-file structure and easy navigation; no bundle files exist and none are needed, leaving only minor organization gaps versus the ideal overview-with-references form.	4 / 5
	Total	17 / 20 Passed

Description

100%Weight 40%Scale 1-5

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

The description is concise, specific, and fully complete: it states concrete capabilities and provides explicit natural-language triggers. It is a strong, low-conflict skill description.

Dimension	Reasoning	Score
Specificity	Lists four concrete, distinct actions (listing chats, reading message history, watching for new messages, sending messages) covering the tool's full surface, matching the comprehensive-coverage anchor.	5 / 5
Completeness	Explicitly answers both 'what' (the four actions) and 'when' via a 'Triggers on:' clause with concrete trigger phrases, matching the anchor that requires both clearly and explicitly.	5 / 5
Trigger Term Quality	Includes natural phrases users would say ('check messages', 'who texted me', 'send text', 'message history') plus synonyms ('imessage', 'sms') and the CLI name ('imsg'), matching comprehensive synonym coverage.	5 / 5
Distinctiveness Conflict Risk	A clear iMessage/SMS niche with distinct triggers like 'imsg' and 'who texted me' makes conflict with other skills minimal, matching the clear-niche anchor.	5 / 5
	Total	20 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

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

	Total	15 / 16 Passed

Repository: joelhooks/joelclaw
Path: skills/imsg/SKILL.md
Commit: 7094ced

Reviewed: 3 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.