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.
96
96%
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 users might say. 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
92%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 skill that is concise, actionable, and clearly structured. It provides executable commands for every operation, includes important non-obvious caveats about delivery semantics and permissions, and establishes a safe workflow pattern. The only minor weakness is the ADR reference without a link and the progressive disclosure could be slightly improved.
| 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 adds genuinely non-obvious information about the optimistic send behavior. | 3 / 3 |
Actionability | All commands are fully executable with concrete flags and arguments. Multiple send examples cover different recipient types and attachment usage. The install command is copy-paste ready. | 3 / 3 |
Workflow Clarity | The safety section establishes a clear workflow: read-only first (chats/history), then confirm before sending. The delivery notes provide explicit validation guidance (check Messages.app for actual delivery status). Permission requirements are clearly mapped to specific command categories. | 3 / 3 |
Progressive Disclosure | References to USER.md for contact details are well-signaled and one level deep. However, the content is all inline in a single file, which is appropriate for this skill's size, but the ADR-0067 reference is mentioned without a link. The structure is good but could benefit from slightly clearer section grouping (e.g., separating setup/permissions from usage). | 2 / 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 | |
825972c
Table of Contents
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.