Content
90%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The body is an excellent, lean, fully executable reference for the imsg CLI: real commands throughout, sensible safety rules, and a concrete worked example with a user-confirmation checkpoint. Its only weaknesses are the absence of a post-send verification/feedback step in the workflow and slightly redundant service-option coverage, plus a description-level (not body-level) lack of trigger guidance.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean and command-first: every section is either a short directive ("Use `imsg` to read and send iMessage/SMS via macOS Messages.app") or executable code, with no explanation of concepts Claude already knows and no padding. It matches 'Lean and efficient; assumes Claude's competence; every token earns its place' — nothing reads as a 4-style trimmable aside. | 5 / 5 |
Actionability | All guidance is copy-paste-ready: real commands with concrete flags (`imsg send --to "+14155551212" --text "Hello!"`, `--service imessage`, `--attachments`), plus a worked jq example for finding a chat. This matches 'Fully executable; copy-paste ready code or commands; specific examples cover the common cases'. | 5 / 5 |
Workflow Clarity | The Example Workflow sequences find-chat → confirm → send and the Rules section supplies explicit checkpoints ("Always confirm recipient and message content before sending", "Never send to unknown numbers without explicit user approval"). This is a clear sequence with most checkpoints present — a minor gap keeps it below 5: there is no post-send verification step (e.g. re-checking history to confirm delivery) and no guidance on handling a failed send. | 4 / 5 |
Progressive Disclosure | The body has good structure with well-organized sections (Prerequisites, When to Use, When NOT to Use, Quick Reference, Service Options, Rules, Example Workflow) and no external bundle files — all content is appropriately inline for a single-CLI skill. It sits slightly above the 'under 50 lines' simple-skill threshold (~88 lines), and a few long blocks (Service Options vs. the send examples) could be consolidated, so it fits 'Good structure; most content is appropriately placed; minor organization gaps' rather than a clean 5. | 4 / 5 |
Total | 18 / 20 Passed |