CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

add-whatsapp

Add WhatsApp channel via native Baileys adapter. Direct connection — no Chat SDK bridge. Uses QR code or pairing code for authentication.

Quality

75%

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

Fix and improve this skill with Tessl

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

Quality

Content

77%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.

An exceptionally actionable, well-sequenced operational skill: every step is executable, validation and feedback loops are built in, and edge cases (expired codes, stale-adapter skew, spam-era wirings) are handled explicitly. The main costs are duplicated troubleshooting content and a monolithic 500+ line body that should offload reference material to separate files.

Suggestions

Merge 'QR code or pairing code expired' and 'Pairing code not working' into a single troubleshooting entry — they repeat the same expiry, retry, and server-side-rejection guidance almost verbatim.

Move the migration audit, Channel Info, and long-form troubleshooting sections into a references/ file (e.g. references/troubleshooting.md) with clearly signaled links, keeping SKILL.md as a lean core workflow.

Cut the 'Optional configuration' section or reduce it to a pointer, since ASSISTANT_HAS_OWN_NUMBER is already fully specified in 'Dedicated vs personal number'.

DimensionReasoningScore

Conciseness

The body is dense with project-specific operational knowledge (nc: directive fences, exact sed/grep .env rewrites, SQL queries, mode inference rules) that Claude cannot know, so little is wasted — but 'QR code or pairing code expired' and 'Pairing code not working' are near-verbatim duplicates, and 'Optional configuration' re-explains ASSISTANT_HAS_OWN_NUMBER already covered in 'Dedicated vs personal number'. Fits 'mostly efficient but could be tightened'; below 4 because of the duplicated sections.

3 / 5

Actionability

Every step is copy-paste executable: pinned exact versions ('@whatsappsockets/baileys@7.0.0-rc14', 'qrcode@1.5.4'), literal one-line barrel append, complete .env rewrite commands, per-method auth commands, validated prompts with regexes, and exact ncl/SQL commands. Fully executable and covers the common cases including failure modes.

5 / 5

Workflow Clarity

Explicit, well-ordered sequence (safety check → Apply → Authenticate → mode flag → restart → resolve DM) with real validation checkpoints: build + registration integration test, '[ -n "{{bot_phone}}" ]', '[ "{{chat_phone}}" != "{{bot_phone}}" ]', restart gated on .env writes, plus feedback loops (clear store/auth/ and re-run on expired codes; migration audit that cross-references before offering destructive flips). Matches the top anchor.

5 / 5

Progressive Disclosure

The single bundle script (scripts/wa-qr-browser.ts) is correctly referenced from the Alternatives and Troubleshooting sections, and section headers make navigation easy — but ~200 lines of troubleshooting, migration-audit, and channel-info content that would fit a one-level-deep reference file are inlined in a 500+ line body, and no references/ files exist. Fits 'some structure, content that should be separate is inline'; not 4 because the split is overdue.

3 / 5

Total

16

/

20

Passed

Description

65%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.

A clear, concrete, distinct description that says what the skill does and how it authenticates, but it lacks any 'Use when...' trigger guidance and understates the skill's scope. Adding an explicit trigger clause would lift completeness and specificity.

Suggestions

Append a trigger clause, e.g. 'Use when the user wants to add, connect, or link WhatsApp to NanoClaw, or mentions Baileys, WhatsApp channel setup, or WhatsApp QR/pairing-code linking.'

Broaden coverage of the skill's actions slightly (e.g. mention wiring the chat and shared vs. dedicated number setup) so the description reflects the workflow's actual scope.

Include one or two natural synonyms such as 'link WhatsApp' or 'WhatsApp bot' to widen trigger-term coverage.

DimensionReasoningScore

Specificity

Names the domain ('WhatsApp channel', 'native Baileys adapter') and two concrete actions — add the channel and authenticate via 'QR code or pairing code' — but omits much of what the skill does (registering the adapter, mode configuration, wiring, troubleshooting). Fits the 'names domain and 1-2 concrete actions, but not comprehensive' anchor; below 4 because coverage of the skill's actual operations is thin.

3 / 5

Completeness

The 'what' is clear and concrete, but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. Not 2 because the 'what' is far from vague.

3 / 5

Trigger Term Quality

'WhatsApp', 'QR code', and 'pairing code' are natural phrases users would say when needing this skill, and 'Baileys' is a genuine technical search term. Below 5 because common variants like 'connect WhatsApp', 'link device', or 'WhatsApp bot' are absent.

4 / 5

Distinctiveness Conflict Risk

'WhatsApp', 'Baileys', and the explicit 'no Chat SDK bridge' contrast carve a clear niche with minimal conflict risk against other channel-setup skills; a user asking for this would unambiguously match it.

5 / 5

Total

15

/

20

Passed

Validation

87%

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

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (525 lines); consider splitting into references/ and linking

Warning

referenced_paths_exist

Referenced path issues: 5 missing

Warning

Total

14

/

16

Passed

Repository

nanocoai/nanoclaw

Path

.claude/skills/add-whatsapp/SKILL.md

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.