add-signal

Add Signal channel integration via signal-cli device-link. Native adapter — no Chat SDK bridge.

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/add-signal/SKILL.md

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 body is a highly actionable, well-sequenced integration runbook with explicit validation and strong troubleshooting coverage. It is efficient and self-contained, with only minor opportunities to split lengthy reference material into bundled files.

Dimension	Reasoning	Score
Conciseness	Mostly efficient prose that assumes competence on Node/pnpm and reserves explanation for Signal-specific concepts (device-link, Note to Self, GroupV2); a few rationale paragraphs could be trimmed but nothing is severely padded.	4 / 5
Actionability	Fully executable, copy-paste-ready commands throughout (nc:run/append/dep blocks, SQL queries, ncl commands, signal-cli invocations) covering install, link, persist, restart, wire, and troubleshoot.	5 / 5
Workflow Clarity	Clearly sequenced Apply steps 1-5 with explicit validation checkpoints (build guards typed API, registration test verifies the barrel import, signal-cli presence check before linking) plus a thorough troubleshooting section providing error-recovery feedback loops.	5 / 5
Progressive Disclosure	Well-organized into clearly headed sections (Apply, Link, Persist, Restart, Wiring, Channel Info, Alternatives, Troubleshooting) with logical navigation; no bundle files exist so content is deliberately self-contained, though long sections like Alternatives and Troubleshooting could plausibly live in separate reference files.	4 / 5
	Total	18 / 20 Passed

Description

53%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 distinctive about its Signal niche and mechanism, but it omits any explicit 'when to use' trigger guidance, which limits completeness and trigger-term quality. Adding a 'Use when...' clause would meaningfully raise the score.

Suggestions

Append an explicit trigger clause, e.g. 'Use when adding Signal as a messaging channel or when the user mentions linking Signal/Note to Self.'

Broaden natural keyword coverage by including terms users actually say (e.g. 'Signal DMs', 'Signal groups', 'link Signal device').

Optionally enumerate the concrete capabilities (send/receive DMs, group chats, markdown, quoted replies) to lift specificity from one action to several.

Dimension	Reasoning	Score
Specificity	Names the domain ('Signal channel integration') and a concrete mechanism ('signal-cli device-link') plus the native-adapter distinction, but lists only one main action rather than several concrete actions.	3 / 5
Completeness	Clearly answers 'what' (add Signal channel via signal-cli device-link) but provides no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the guidelines.	3 / 5
Trigger Term Quality	Includes relevant terms like 'Signal', 'channel integration', and 'device-link', but misses natural variations or synonyms a user might actually say and lacks explicit trigger phrasing.	3 / 5
Distinctiveness Conflict Risk	The Signal-specific niche and explicit 'no Chat SDK bridge' disambiguation make it mostly distinct with minimal overlap risk, though the absence of a trigger phrase keeps it just short of a clean 5.	4 / 5
	Total	13 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
referenced_paths_exist	Referenced path issues: 2 missing	Warning

	Total	15 / 16 Passed

Repository: nanocoai/nanoclaw
Path: .claude/skills/add-signal/SKILL.md
Commit: ad8837c

Reviewed: 4 days 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.