imsg
iMessage/SMS CLI for listing chats, history, watch, and sending.
68
63%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/imsg/SKILL.mdQuality
Discovery
40%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 identifies a clear and distinctive domain (iMessage/SMS CLI) and lists basic actions, but it is too terse and lacks a 'Use when...' clause, making it incomplete for skill selection. Adding natural trigger terms and explicit usage guidance would significantly improve it.
Suggestions
Add a 'Use when...' clause, e.g., 'Use when the user wants to send or read text messages, iMessages, or SMS from the command line.'
Include common user-facing trigger terms like 'text message', 'texting', 'send a text', 'read messages', 'message history' to improve discoverability.
Expand the capability list slightly, e.g., 'Lists conversations, retrieves message history, watches for new messages in real time, and sends iMessage or SMS replies via CLI.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (iMessage/SMS) and lists some actions (listing chats, history, watch, sending), but the terms are somewhat terse and not fully elaborated as concrete capabilities. | 2 / 3 |
Completeness | Describes what the skill does (iMessage/SMS CLI operations) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per rubric, missing 'Use when' caps completeness at 2, and the 'what' is also fairly thin, warranting a 1. | 1 / 3 |
Trigger Term Quality | Includes relevant keywords like 'iMessage', 'SMS', 'chats', 'sending', and 'history', but misses common user variations like 'text message', 'texting', 'messages app', or 'send a text'. | 2 / 3 |
Distinctiveness Conflict Risk | iMessage/SMS CLI is a very specific niche — it's unlikely to conflict with other skills given the distinct domain of messaging via CLI. | 3 / 3 |
Total | 8 / 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 well-crafted, concise skill that provides clear, actionable CLI commands for iMessage/SMS operations. Its main weakness is the lack of an explicit workflow connecting the discovery step (listing chats) to subsequent actions, and missing error handling guidance for the send operation. Overall it's a strong, efficient skill for a straightforward CLI tool.
Suggestions
Add a brief workflow sequence showing the typical flow: list chats → get chat-id → fetch history/watch/send, making the dependency between steps explicit.
Add a verification step after sending (e.g., check delivery status or confirm via history) to strengthen the safety of the destructive send operation.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every section is lean and purposeful. No unnecessary explanations of what iMessage is or how CLI tools work. The skill assumes Claude's competence and provides only what's needed. | 3 / 3 |
Actionability | All four core actions have concrete, copy-paste-ready CLI commands with realistic arguments. The inputs section clearly specifies what needs to be collected. Commands are fully executable. | 3 / 3 |
Workflow Clarity | The skill lists actions clearly but lacks explicit workflow sequencing (e.g., 'first list chats to get chat-id, then use it for history/watch'). The send action involves a destructive operation (sending a message) and while it mentions confirming recipient + message, there's no explicit validation/feedback loop for verifying delivery or handling errors. | 2 / 3 |
Progressive Disclosure | For a simple CLI wrapper skill under 50 lines with no need for external references, the content is well-organized with clear sections (Overview, Inputs, Actions, Notes, Ideas). No bundle files are needed and none are referenced. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
72%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 8 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata.version' is missing | Warning |
metadata_field | 'metadata' should map string keys to string values | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 8 / 11 Passed | |
- Repository
- deepgram/dglabs-deepclaw
- Commit
ec8d4f8
- 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.