imsg
iMessage/SMS CLI for listing chats, history, and sending messages via Messages.app.
91
Quality
91%
Does it follow best practices?
Impact
96%
1.81xAverage score across 3 eval scenarios
Passed
No known issues
Quality
Discovery
82%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 description with strong specificity and excellent trigger terms covering both iMessage and SMS terminology. The main weakness is the absence of an explicit 'Use when...' clause, which would help Claude know exactly when to select this skill over others.
Suggestions
Add a 'Use when...' clause with trigger phrases like 'Use when the user wants to send texts, read iMessages, view message history, or interact with Apple Messages.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'listing chats, history, and sending messages'. Also specifies the platform (Messages.app) and interface type (CLI). | 3 / 3 |
Completeness | Clearly answers 'what does this do' with specific actions, but lacks an explicit 'Use when...' clause or equivalent trigger guidance. The when is only implied through the capability description. | 2 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'iMessage', 'SMS', 'chats', 'history', 'sending messages', 'Messages.app'. Good coverage of both Apple-specific and generic messaging terms. | 3 / 3 |
Distinctiveness Conflict Risk | Very distinct niche targeting Apple's iMessage/SMS via Messages.app CLI. Unlikely to conflict with other skills due to specific platform and application references. | 3 / 3 |
Total | 11 / 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 high-quality skill that exemplifies good practices: concise command references, clear when-to-use/when-not-to-use boundaries, explicit safety rules with confirmation requirements, and a practical example workflow. The skill efficiently teaches Claude how to use the imsg CLI without unnecessary explanation.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, providing only necessary information. No explanations of what iMessage is or how messaging works—assumes Claude's competence throughout. | 3 / 3 |
Actionability | Fully executable commands with specific flags and examples. Every command is copy-paste ready with concrete options like `--limit 20 --json` and real phone number formats. | 3 / 3 |
Workflow Clarity | The example workflow shows a clear 3-step sequence with an explicit confirmation checkpoint before sending. Safety rules reinforce validation requirements for destructive operations (sending messages). | 3 / 3 |
Progressive Disclosure | Well-organized with clear sections (When to Use, Requirements, Commands, Safety, Example). For a skill under 100 lines with no need for external references, the structure is appropriate and easy to navigate. | 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
- trpc-group/trpc-agent-go
- Commit
8763418
- 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.