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.
95
93%
Does it follow best practices?
Impact
100%
2.63xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Quality
Discovery
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 |
Implementation
87%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, well-structured skill that efficiently documents a CLI tool with concrete, executable examples. Its main weakness is the lack of an explicit send workflow with verification steps — given that sending messages is a consequential action, a numbered sequence (lookup recipient → confirm → send → verify) would improve safety. Otherwise, the content is lean, actionable, and well-organized.
Suggestions
Add an explicit numbered workflow for sending messages: 1. Look up recipient in USER.md, 2. Confirm recipient/text, 3. Send, 4. Check for delivery issues — this would strengthen the safety posture for a destructive-adjacent operation.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every section is lean and purposeful. No unnecessary explanations of what iMessage is or how AppleScript works. The delivery notes section efficiently conveys non-obvious gotchas without padding. | 3 / 3 |
Actionability | All commands are copy-paste ready with concrete flags and examples. Multiple send variants (email, phone, attachment) are shown with real command syntax. Setup requirements are specific and actionable. | 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 workflow sequence with validation checkpoints for the send operation. Given that sending messages is a potentially impactful action, a clearer step-by-step with verification would strengthen this. | 2 / 3 |
Progressive Disclosure | Content is well-organized into logical sections (Setup, Commands, Delivery Notes, Safety, Install). References to USER.md for credentials are clear and one-level deep. The skill is appropriately sized for a single file with no need for further splitting. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
90%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
ce9ca8e
- Reviewed
Table of Contents
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.