CtrlK
BlogDocsLog inGet started
Tessl Logo

imsg

iMessage/SMS CLI for listing chats, history, watch, and sending.

66

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

The canonical home for this skill is imsg in deepgram/dglabs-deepclaw

SKILL.md
Quality
Evals
Security

Quality

Content

92%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 content is an exemplary lean CLI skill: executable commands for every action, clear prerequisite permissions, an explicit input-discovery step, and a confirmation checkpoint before the outward-facing send. The only flaw is minor redundancy in the "Ideas to try" section. No bundle files exist, so all guidance lives appropriately in SKILL.md.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence (no explanation of what iMessage is), but "Ideas to try" repeats the exact `imsg chats --limit 10 --json` command already shown in two places and restates the watch action — minor content that could be trimmed, matching the score-4 anchor rather than the every-token-earns-its-place score-5 anchor.

4 / 5

Actionability

All four actions are given as fully executable, copy-paste-ready bash commands with realistic flags and a concrete example recipient (`imsg send --to "+14155551212" --text "hi"`), and the inputs section explains exactly how to obtain the required chatId, covering the common cases.

5 / 5

Workflow Clarity

For this simple single-purpose skill the workflow is unambiguous: "Inputs to collect" sequences discovery (chatId from `imsg chats --limit 10 --json`) before history/watch, and the risky send action has an explicit validation checkpoint ("Confirm recipient + message before sending"), satisfying the simple-skill exception.

5 / 5

Progressive Disclosure

The body is ~50 lines with no external reference files (references/, scripts/, assets/ are absent) and no need for them; the content is split into well-organized sections (Overview, Requirements, Inputs, Actions, Notes), which per the guidelines earns a 5 for short skills without external references.

5 / 5

Total

19

/

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 concise, specific, and highly distinctive, naming the domain and four concrete actions in third-person voice. Its main weakness is the complete absence of 'when to use this' trigger guidance, which caps completeness, and it misses common natural phrasings like 'text' or 'Messages.app'.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks to read, send, or watch iMessages/SMS texts on macOS."

Include natural synonyms users actually say, such as "text", "texting", and "Messages.app", to improve trigger-term coverage.

Expand the elliptical action nouns ("history, watch") into verb phrases like "fetch chat history" and "watch chats live" for fuller capability coverage.

DimensionReasoningScore

Specificity

"listing chats, history, watch, and sending" lists four concrete actions across a named domain ("iMessage/SMS CLI"), giving several specific capabilities; however the actions are elliptical nouns ("history", "watch") rather than full verb-object phrases, so coverage is strong but not fully comprehensive like the score-5 anchor.

4 / 5

Completeness

The description has a clear 'what' (list chats, history, watch, send) but contains no 'Use when...' clause or any equivalent trigger guidance, which per the judging guidelines caps completeness at 3.

3 / 5

Trigger Term Quality

"iMessage", "SMS", "chats", and "sending" are natural terms users would say, giving good keyword coverage; common variations like "text", "texting", or "Messages.app" are missing, which falls just short of the comprehensive synonym coverage of the score-5 anchor.

4 / 5

Distinctiveness Conflict Risk

"iMessage/SMS" on macOS defines a clear, narrow niche with distinct trigger terms that no generic messaging or file skill would claim, matching the minimal-conflict score-5 anchor; it is clearly above the score-4 anchor because there is no meaningful overlap with closely related skills.

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.

Validation — 13 / 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
Bitterbot-AI/bitterbot-desktop
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.