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.
99
Does it follow best practices?
Validation for skill structure
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 well-crafted skill description that excels across all dimensions. It provides specific capabilities, includes natural trigger terms users would actually say, explicitly states when to use it via the 'Triggers on:' clause, and has a clear, distinct niche in messaging functionality.
| 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 (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 terms users would say: 'check messages', 'read imessage', 'send text', 'imsg', 'message history', 'sms', 'who texted me' - these match real user language patterns. | 3 / 3 |
Distinctiveness Conflict Risk | Very clear niche focused on iMessage/SMS with distinct triggers like 'imessage', 'imsg', 'sms', 'who texted me' - unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an excellent skill file that demonstrates best practices: concise command reference with executable examples, clear safety guidelines, and appropriate external references. The delivery notes section adds valuable context about the gap between 'sent' and 'delivered' status, which is critical operational knowledge.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean and efficient. No unnecessary explanations of what iMessage is or how CLIs work. Every section provides only essential information Claude needs to use the tool. | 3 / 3 |
Actionability | All commands are copy-paste ready with concrete examples including flags, argument formats, and multiple use cases (email vs phone, with/without attachments). No pseudocode or vague instructions. | 3 / 3 |
Workflow Clarity | Clear safety workflow established: read-only by default, use chats/history before sending, confirm recipient and text before send. Delivery notes explain the validation gap (sent ≠ delivered) and how to diagnose failures. | 3 / 3 |
Progressive Disclosure | Well-organized sections with clear headers. Appropriately references external files (USER.md) for user-specific data without deep nesting. Content length is appropriate for a single SKILL.md file. | 3 / 3 |
Total | 12 / 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 | |
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.