CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

add-whatsapp-cloud

Add WhatsApp Business Cloud API channel via Chat SDK. Official Meta API.

Quality

81%

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

SKILL.md
Quality
Evals
Security

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.

An exceptionally actionable, well-sequenced skill: every step is executable, validation is built in with explicit feedback loops, and troubleshooting is concrete rather than generic. The only weaknesses are minor design-rationale verbosity and a monolithic single-file layout that could offload Troubleshooting/Channel Info to reference files.

Suggestions

Trim design commentary not needed to execute the task, such as the explanation of how prompt directives could feed `ncl` or the OneCLI vault by swapping the consumer.

Move Troubleshooting and Channel Info into a one-level-deep reference file (e.g. TROUBLESHOOTING.md) and link them from the main flow to improve progressive disclosure.

DimensionReasoningScore

Conciseness

The body is directive-first with no padding of concepts Claude already knows, but there are minor instances of over-explanation that could be trimmed, e.g. the design rationale "prompt only *asks* and binds the answer to a name; a separate directive consumes it — so the same prompts could feed `ncl` or the OneCLI vault instead of `.env` by swapping only the consumer".

4 / 5

Actionability

Fully executable throughout: exact pinned dependency "@chat-adapter/whatsapp@4.41.1", concrete commands ("pnpm run build", "pnpm exec vitest run src/channels/whatsapp-cloud-registration.test.ts"), exact env var names, exact webhook route "/webhook/whatsapp-cloud", and specific navigation paths in the Meta dashboard.

5 / 5

Workflow Clarity

The Apply section gives a clear 4-step sequence with explicit validation steps (build plus the registration test, whose failure modes are enumerated), and Troubleshooting closes the loop with a concrete validate-fix-retry cycle ("Run pnpm exec vitest run ... — red means the barrel import or the @chat-adapter/whatsapp install drifted, so re-run the Apply steps").

5 / 5

Progressive Disclosure

No bundle files exist (references/, scripts/, assets/ are absent), and the ~165-line body is well-sectioned with every inline section task-relevant; however sections like Troubleshooting and Channel Info are reasonable candidates for a one-level-deep reference file to slim the main document — good structure with minor organization gaps rather than an appropriately split overview.

4 / 5

Total

18

/

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 concise, third-person description with a distinct niche and good natural keywords, but it only names a single action and lacks any 'Use when...' trigger guidance. Adding an explicit trigger clause and a fuller action list would lift both completeness and specificity.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user wants to connect WhatsApp, a WhatsApp Business number, or a Meta Cloud API channel to NanoClaw."

Expand the action list to cover the main outcomes, e.g. "...: copies the adapter in, registers it, pins the @chat-adapter/whatsapp dependency, and configures webhook credentials."

Include a synonym or two users actually type, such as "WhatsApp channel" or "WhatsApp Business", to improve trigger-term coverage.

DimensionReasoningScore

Specificity

"Add WhatsApp Business Cloud API channel via Chat SDK" names the domain and one concrete action (adding the channel), matching the '1-2 concrete actions, not comprehensive' anchor; it does not list the several specific actions (register, install, configure webhooks/credentials) needed for a 4.

3 / 5

Completeness

The 'what' is clear (add a WhatsApp Business Cloud API channel via Chat SDK) but the 'when' is entirely absent — no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3.

3 / 5

Trigger Term Quality

Natural terms users would say are present — "WhatsApp", "Business Cloud API", "Chat SDK", "Official Meta API" — giving good keyword coverage, though common variations like "WhatsApp channel", "WhatsApp integration", or "WhatsApp Business number" are missing.

4 / 5

Distinctiveness Conflict Risk

WhatsApp Cloud API channel setup is a clear niche with distinct triggers (WhatsApp, Meta, Chat SDK channel); it is unlikely to fire for any other skill.

5 / 5

Total

15

/

20

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

nanocoai/nanoclaw

Path

.claude/skills/add-whatsapp-cloud/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.