CtrlK
BlogDocsLog inGet started
Tessl Logo

add-imessage

Add iMessage channel integration via Chat SDK. Local (macOS) or remote (Photon API) mode.

69

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

High

Do not use without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

100%Weight 40%Scale 1-3

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

The body is a tight, executable, well-sequenced setup workflow with validation checkpoints, explicit mode branching, and a recovery-oriented Troubleshooting section. It assumes Claude's competence and every directive is concrete and copy-paste ready.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence; directive fences and prose each earn their place ('Pinned to an exact version — the supply-chain policy rejects ranges and latest') without explaining concepts Claude already knows.

3 / 3

Actionability

It provides concrete, copy-paste-ready guidance throughout: 'nc:copy from-branch:channels src/channels/imessage.ts', 'bash setup/channels/imessage-configure.sh local', and 'pnpm exec vitest run src/channels/imessage-registration.test.ts'.

3 / 3

Workflow Clarity

Numbered steps 1–4 are clearly sequenced with explicit validation (build guards, registration test 'goes red if the import line is deleted or drifts') and a human checkpoint ('Stop and wait for the user to confirm Full Disk Access is granted'), plus a Troubleshooting feedback loop.

3 / 3

Progressive Disclosure

No bundle files are present (references/, scripts/, assets/ are absent) and the only cited paths are project repo scripts; the single self-contained SKILL.md is well-organized into clear sections with no nested reference chains.

3 / 3

Total

12

/

12

Passed

Description

67%Weight 40%Scale 1-3

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 distinctive but lacks any explicit 'when to use' trigger guidance and leans on technical jargon (Chat SDK, Photon API) over natural user terms. Adding a 'Use when...' clause with plain-language triggers would lift completeness and trigger-term quality.

Suggestions

Add an explicit 'Use when...' clause naming natural triggers (e.g. 'Use when adding iMessage support, setting up Apple Messages / text messaging on macOS, or wiring a Photon iMessage bridge').

Surface natural user terms ('text messaging on Mac', 'Apple Messages', 'blue-bubble chat') alongside the technical ones to improve trigger-term coverage.

Keep the concise what-it-does framing but ensure the 'when' is stated, not merely implied by the domain.

DimensionReasoningScore

Specificity

Names concrete actions ('Add iMessage channel integration', 'via Chat SDK') and enumerates two distinct modes (local macOS, remote Photon API). It is compact but states multiple specific concrete actions rather than vague language.

3 / 3

Completeness

It clearly answers 'what' (add iMessage channel integration) but provides no 'Use when...' or equivalent explicit trigger guidance, which caps completeness at 2 per the rubric.

2 / 3

Trigger Term Quality

'iMessage' is a natural user term, but 'Chat SDK', 'Photon API', and 'channel integration' are technical jargon, and common variations like 'text messaging on Mac' or 'Apple Messages' are missing.

2 / 3

Distinctiveness Conflict Risk

The iMessage channel integration niche is specific and distinct, so it is unlikely to trigger for the wrong skill.

3 / 3

Total

10

/

12

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
nanocoai/nanoclaw
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.