CtrlK
BlogDocsLog inGet started
Tessl Logo

imessage

Send and receive iMessages/SMS via the imsg CLI on macOS.

68

Quality

83%

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

SKILL.md
Quality
Evals
Security

Quality

Content

100%

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

The content is a strong, executable skill: lean, copy-paste-ready commands, clear workflows with explicit confirm-before-send validation, and clean section organization requiring no external references. It is essentially already at the top of the rubric across all dimensions.

DimensionReasoningScore

Conciseness

The body is lean with no concept explanations Claude already knows; sections like 'Quick Reference' and 'Service Options' each earn their place, matching the score-3 'every token earns its place' anchor.

3 / 3

Actionability

Provides fully executable imsg commands with real flags (e.g. '--to', '--service imessage', '--json', '--file') plus a copy-paste jq example, matching the score-3 'copy-paste ready' anchor.

3 / 3

Workflow Clarity

The numbered Example Workflow includes an explicit validation checkpoint ('Confirm with user: Found Mom... Send... via iMessage?') and the Rules reinforce verification ('Always confirm recipient', 'Verify file paths exist before attaching'), matching the score-3 anchor with explicit validation for an outward-facing send operation.

3 / 3

Progressive Disclosure

No bundle files exist and the skill needs no external references; the body is well-organized into clearly labeled sections (Prerequisites, When to Use, Quick Reference, Rules) with no nested references, so per the scoring notes progressive disclosure scores 3 for a self-contained well-structured skill.

3 / 3

Total

12

/

12

Passed

Description

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 specific and clearly niche with concrete actions and low conflict risk, but it lacks an explicit usage trigger clause and misses common natural terms like 'text message'. Adding a 'Use when...' clause covering texting vocabulary would lift completeness and trigger-term quality.

Suggestions

Append an explicit trigger clause, e.g. 'Use when the user asks to send or read iMessages, SMS, or text messages on macOS.'

Add common natural variations users say ('text message', 'texting', 'texts') alongside 'iMessages/SMS'.

Optionally mention reading conversation history in the description, since 'receive' alone undersells the chat-listing/history capabilities the body documents.

DimensionReasoningScore

Specificity

Quotes concrete actions ('Send and receive iMessages/SMS') naming both the tool ('imsg CLI') and platform ('macOS'); lists specific concrete actions rather than vague language, matching the score-3 anchor.

3 / 3

Completeness

Clearly states what the skill does ('Send and receive iMessages/SMS via the imsg CLI') but lacks an explicit 'Use when...' trigger clause, so per the judging guidelines completeness is capped at 2.

2 / 3

Trigger Term Quality

Includes natural terms 'iMessages/SMS' and 'macOS' but omits common variations like 'text message' or 'texting' that users would actually say, matching the score-2 anchor of 'some relevant keywords but missing common variations'.

2 / 3

Distinctiveness Conflict Risk

The macOS + imsg CLI + iMessage/SMS niche is narrow and platform/tool-specific, making it clearly distinguishable and unlikely to trigger for the wrong skill, matching the score-3 anchor.

3 / 3

Total

10

/

12

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
NousResearch/hermes-agent
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.