add-imessage

Add iMessage to NanoClaw — one channel, two backends. Local (this Mac's chat.db via the Chat SDK bridge; macOS + Full Disk Access) or Hosted iMessage (via photon.codes — native spectrum-ts with a device-login wizard; any OS, no Mac relay). Triggers on "add imessage", "connect imessage", "add photon", "imessage via photon", "native imessage".

Quality

94%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

88%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 highly actionable with a well-sequenced, validated workflow and dense project-specific guidance. The main weakness is reference hygiene: the repeated docs link points to an inconsistent path and the referenced file is absent from the bundle.

Suggestions

Fix the docs reference so the link text and href agree (e.g. [docs/imessage.md](docs/imessage.md)) and either include docs/imessage.md in the bundle or note it is external.

Tighten the intro and a few troubleshooting paragraphs to drop explanatory framing Claude does not need, pushing conciseness toward a 5.

Consider moving the full Hosted features env-var list and the Channel Info block into the referenced docs file to keep SKILL.md as an overview.

Dimension	Reasoning	Score
Conciseness	The body is dense and mostly lean — project-specific facts (NanoClaw's supply-chain gate, the photon device-login flow, Full Disk Access mechanics) earn their tokens because Claude would not know them. A few explanatory prose passages (e.g., the intro paragraphs and some troubleshooting framing) could be trimmed, which keeps it just below a 5.	4 / 5
Actionability	Every step ships copy-paste-ready, fully-specified commands inside `nc:` directive fences — exact version pins (`spectrum-ts@11.0.0`), exact paths (`src/channels/imessage.ts`), and concrete invocations (`pnpm exec tsx scripts/photon-setup.ts setup --phone {{owner_handle}} --embedded`).	5 / 5
Workflow Clarity	The Apply section is a numbered 1–5 sequence with explicit validation checkpoints (`effect:check` for macOS, `effect:build`, `effect:test` with "Both must be clean"), a stop-and-wait for Full Disk Access, and troubleshooting feedback loops that re-run drifted steps — fully matching the anchor with explicit validation and error recovery.	5 / 5
Progressive Disclosure	Structure is strong with clear section headers and one-level-deep "Full reference" pointers to docs/imessage.md. It is not a 5 because the link display text ("docs/imessage.md") disagrees with its href ("docs.md") and no docs file is present in the bundle, a minor but real navigation gap.	4 / 5
	Total	18 / 20 Passed

Description

100%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 exemplary: it states a concrete capability, distinguishes the two backends with specific mechanisms, and provides an explicit trigger list. It uses third person and avoids fluff. No changes needed.

Dimension	Reasoning	Score
Specificity	Names the domain ("Add iMessage to NanoClaw") and enumerates concrete setup paths for both backends — Local "via the Chat SDK bridge" reading chat.db, Hosted "via photon.codes — native spectrum-ts with a device-login wizard" — giving comprehensive, specific coverage rather than vague language.	5 / 5
Completeness	It explicitly answers both "what" (one channel, two backends with named mechanisms) and "when" (a concrete "Triggers on" list), matching the anchor that requires explicit concrete trigger phrases.	5 / 5
Trigger Term Quality	An explicit "Triggers on" clause lists five natural phrases a user would actually say ("add imessage", "connect imessage", "add photon", "imessage via photon", "native imessage"), including synonyms and backend-specific terms.	5 / 5
Distinctiveness Conflict Risk	The niche is narrow and product-specific (iMessage for NanoClaw via two named backends) with distinct trigger phrases, leaving minimal overlap risk with other skills.	5 / 5
	Total	20 / 20 Passed

Validation

87%

Warnings & errors only

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

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 4 missing	Warning
referenced_paths_exist	Referenced path issues: 3 missing	Warning

	Total	14 / 16 Passed

Repository: nanocoai/nanoclaw
Path: .claude/skills/add-imessage/SKILL.md
Commit: 7902716

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.