CtrlK
BlogDocsLog inGet started
Tessl Logo

add-signal

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

58

Quality

67%

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

Fix and improve this skill with Tessl

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

Quality

Content

77%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 highly actionable with a well-sequenced, validated workflow, but it is a long monolithic file with some duplicated troubleshooting content that keeps conciseness and progressive disclosure at the mid level.

Suggestions

Move the detailed Troubleshooting entries and the Alternatives registration path into a separate reference file (e.g. TROUBLESHOOTING.md) referenced one level deep, to reduce SKILL.md length and improve progressive disclosure.

De-duplicate the captcha and 'Invalid verification method' guidance so it lives in one place and cross-references from the other.

DimensionReasoningScore

Conciseness

The body is dense with actionable, non-redundant operational detail and avoids explaining basics Claude already knows, but it is long and duplicates some content (captcha solving and the 'Invalid verification method' note appear in both Alternatives and Troubleshooting).

2 / 3

Actionability

It provides fully executable, copy-paste-ready commands throughout — exact signal-cli flags, SQL queries, `ncl` invocations, and pinned dependency versions — matching the score-3 anchor.

3 / 3

Workflow Clarity

The Apply section is a clearly numbered 1–5 sequence with explicit validation (build guards typed API consumption; the registration test fails if the barrel import drifts) plus a pre-link reachability check, satisfying the checkpoint and feedback-loop criteria.

3 / 3

Progressive Disclosure

It is well-sectioned with clear headings and no nested references, but it is a single monolithic ~330-line file with no external reference files, so content that could be split (Alternatives registration path, Channel Info, Troubleshooting) is inlined.

2 / 3

Total

10

/

12

Passed

Description

57%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 to Signal and clearly distinct, but it stops short of a full capability list and omits any explicit 'when to use' trigger clause, leaving completeness and trigger coverage at the mid level.

Suggestions

Append an explicit trigger clause, e.g. 'Use when adding Signal as a messaging channel or when the user asks to link/add Signal support.'

Broaden natural trigger terms to include variations like 'Signal messaging', 'link Signal', or 'Signal DMs' alongside the existing keywords.

Expand the action list to name more concrete capabilities (e.g. 'send and receive DMs and group messages, render the device-link QR') to raise specificity.

DimensionReasoningScore

Specificity

Names the domain and mechanism ('signal-cli device-link', 'Native adapter — no Chat SDK bridge') but does not enumerate a comprehensive list of concrete actions, matching the score-2 anchor rather than the multi-action score-3 example.

2 / 3

Completeness

It clearly answers 'what' (add Signal channel integration via device-link) but has no 'Use when…' or equivalent explicit trigger guidance, which the guidelines cap at 2.

2 / 3

Trigger Term Quality

'Signal' and 'channel integration' are natural terms, but the set is narrow and leans on jargon ('signal-cli', 'device-link'); common variations a user might say ('Signal messaging', 'link Signal', 'Signal DMs') are missing.

2 / 3

Distinctiveness Conflict Risk

'Add Signal channel integration' names a specific platform niche with a distinctive trigger, making it unlikely to fire for an unrelated skill.

3 / 3

Total

9

/

12

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 2 missing

Warning

Total

15

/

16

Passed

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.