CtrlK
BlogDocsLog inGet started
Tessl Logo

imsg

iMessage/SMS CLI for listing chats, history, and sending messages via Messages.app.

82

1.81x
Quality

76%

Does it follow best practices?

Impact

96%

1.81x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./openclaw/skills/imsg/SKILL.md

The canonical home for this skill is imsg in Hung-Reo/hungreo-openclaw

SKILL.md
Quality
Evals
Security

Quality

Content

82%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable with executable commands and a clear confirmation-gated workflow, organized into clean sections. It is concise and well-structured for a self-contained CLI skill.

DimensionReasoningScore

Conciseness

The body is lean and command-driven with minimal over-explanation, though the "When NOT to Use" channel enumeration adds a little bulk that could be trimmed, fitting the "efficient; minor instances that could be trimmed" anchor.

4 / 5

Actionability

Commands are fully executable and copy-paste ready across the common cases (chats, history, watch, send with attachments, service selection), matching the "fully executable; specific examples cover the common cases" anchor.

5 / 5

Workflow Clarity

The example workflow gives a clear 3-step sequence with an explicit confirmation checkpoint before sending, but it lacks an error-recovery feedback loop, fitting the "clear sequence with most checkpoints present; minor validation gaps" anchor.

4 / 5

Progressive Disclosure

Content is well-organized into clearly signaled sections and is appropriately self-contained for a single CLI tool, though it is over 50 lines with no external reference split, matching the "good structure; minor organization gaps" anchor.

4 / 5

Total

17

/

20

Passed

Description

70%Weight 40%Scale 1-5

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 specific and well-scoped to a clear niche, but it omits any explicit "Use when..." trigger guidance, which limits its completeness. Adding a trigger clause would raise the completeness and overall score.

Suggestions

Append a 'Use when...' clause with concrete triggers, e.g. 'Use when the user asks to send or read iMessage/SMS, or check Messages.app chats.'

Include natural synonyms like 'text' or 'text message' alongside 'iMessage' and 'SMS' to broaden trigger term coverage.

Mention attachments explicitly (e.g. 'send messages with attachments') to close the specificity gap.

DimensionReasoningScore

Specificity

Names the iMessage/SMS domain and lists several concrete actions — "listing chats, history, and sending messages" — with only minor gaps (no mention of attachments or watching), matching the "several specific actions; minor gaps" anchor.

4 / 5

Completeness

It clearly states what the tool does, but there is no "Use when..." clause or equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 3.

3 / 5

Trigger Term Quality

Natural terms like "iMessage", "SMS", "chats", and "messages" are present, but common synonyms such as "text" or "text message" are missing, fitting the "good keyword coverage; a few natural terms missing" anchor.

4 / 5

Distinctiveness Conflict Risk

The iMessage/SMS via Messages.app niche is specific with distinct triggers and minimal overlap risk against other messaging skills, matching the "clear niche with distinct triggers" anchor.

5 / 5

Total

16

/

20

Passed

Validation

81%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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

13

/

16

Passed

Repository
trpc-group/trpc-agent-go
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.