imsg
iMessage/SMS CLI for listing chats, history, and sending messages via Messages.app.
84
83%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Quality
Discovery
67%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 is concise and specific about its capabilities, clearly identifying the domain (iMessage/SMS) and concrete actions (listing chats, viewing history, sending messages). Its main weaknesses are the lack of an explicit 'Use when...' trigger clause and missing common user phrasings like 'text message' or 'send a text' that would improve skill selection accuracy.
Suggestions
Add a 'Use when...' clause, e.g., 'Use when the user wants to send or read text messages, view iMessage conversations, or interact with Messages.app.'
Include additional natural trigger terms like 'text message', 'texting', 'send a text', 'conversation history', 'message thread' to improve matching with common user language.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'listing chats', 'history', and 'sending messages'. Also specifies the tool ('Messages.app') and interface type ('CLI'). | 3 / 3 |
Completeness | Clearly answers 'what does this do' (listing chats, history, sending messages via CLI), but lacks an explicit 'Use when...' clause specifying when Claude should select this skill. | 2 / 3 |
Trigger Term Quality | Includes good terms like 'iMessage', 'SMS', 'chats', 'messages', and 'Messages.app', but misses common user variations like 'text message', 'texting', 'send a text', or 'conversation history'. | 2 / 3 |
Distinctiveness Conflict Risk | Very distinct niche — iMessage/SMS via Messages.app CLI is highly specific and unlikely to conflict with other skills. The combination of messaging platform and CLI interface creates a clear identity. | 3 / 3 |
Total | 10 / 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 a well-crafted skill that is concise, actionable, and well-structured. It provides concrete CLI commands with real arguments, includes appropriate safety guardrails with user confirmation steps, and clearly disambiguates from other messaging channels. The example workflow ties everything together effectively.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient. It doesn't explain what iMessage is or how Messages.app works. The 'When NOT to Use' section adds value by disambiguating from other messaging channels. Every section earns its place. | 3 / 3 |
Actionability | All commands are concrete, copy-paste ready with real flags and arguments. The example workflow shows a complete end-to-end flow with actual CLI commands and jq filtering. Service options are clearly enumerated. | 3 / 3 |
Workflow Clarity | The example workflow clearly sequences steps: find chat → confirm with user → send after confirmation. Safety rules include explicit validation checkpoints (confirm recipient, confirm file exists). The confirmation step before sending is an appropriate feedback loop for a potentially destructive/irreversible operation. | 3 / 3 |
Progressive Disclosure | For a skill under 80 lines covering a single CLI tool, the content is well-organized into logical sections (when to use, commands, safety, workflow) without needing external references. The structure supports quick scanning and discovery. | 3 / 3 |
Total | 12 / 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
- qsimeon/openclaw-engaging
- Commit
4467e04
- 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.