Name: whatsapp
Rating: 60 (1 reviews)
Author: membranedev

Whatsapp integration. Manage Chats, Users, Groups, Contacts, Statuses. Use when the user wants to interact with Whatsapp data.

Quality

70%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/whatsapp/SKILL.md

Quality

Content

75%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 highly actionable with executable commands and a solid, validation-aware connection workflow. Its weaknesses are an unnecessary explanatory intro paragraph and slightly inconsistent step numbering in the workflow.

Suggestions

Cut the opening 'WhatsApp is a messaging application...' paragraph and the 'so you can focus on the integration logic rather than auth plumbing' aside — Claude already knows what WhatsApp is.

Fix the workflow numbering: label a clear 'Step 1' (connect) and 'Step 2' (search/run actions) so the 'skip to Step 2' and '1b' references resolve unambiguously.

Consider moving the popular-actions table into a references/ file referenced from the body, to keep SKILL.md a lean overview.

Dimension	Reasoning	Score
Conciseness	The opening paragraph explains what WhatsApp is ('WhatsApp is a messaging application that allows users to send text, voice messages...') — concept background Claude already knows — and a few padded asides ('so you can focus on the integration logic rather than auth plumbing'), but the bulk is efficient commands and tables, fitting 'mostly efficient but includes some unnecessary explanation.'	3 / 5
Actionability	It provides copy-paste-ready, fully executable commands throughout (npm install, membrane login, connection ensure, action list/run, request) with concrete flags and a populated popular-actions table keyed by real action ids, covering the common cases.	5 / 5
Workflow Clarity	The connection workflow has a clear sequence with explicit validation checkpoints (poll --wait, branch on READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR, re-poll after user action), but the step numbering is inconsistent ('skip to Step 2' with no labeled Step 2, a '1b' without a '1a'), a minor gap below the fully-checklisted anchor.	4 / 5
Progressive Disclosure	The body is well-organized into clearly headed sections (Overview, Install, Authentication, Connecting, Searching, Popular actions, Running, Proxy, Best practices) with no bundle files present and no nested references; the inline popular-actions table is borderline content that could live in a separate reference, keeping it just short of the ideal one-level-deep split.	4 / 5
	Total	16 / 20 Passed

Description

66%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 successfully states both what the skill does and when to use it, anchored to a distinct WhatsApp-specific niche. Its main weakness is generic action language ('Manage') and a trigger clause that could use more natural user phrasings.

Suggestions

Replace the generic verb 'Manage' with concrete actions, e.g. 'Send and read messages, manage groups and contacts, view statuses.'

Expand the trigger clause with natural phrasings users actually say, e.g. 'Use when the user wants to send or read WhatsApp messages, manage groups/contacts, or check statuses.'

Dimension	Reasoning	Score
Specificity	The description names the domain and enumerates concrete entities ('Manage Chats, Users, Groups, Contacts, Statuses'), but the single verb 'Manage' is generic rather than listing specific actions like send/read/update, matching the anchor for domain plus limited concrete actions.	3 / 5
Completeness	Both 'what' ('Whatsapp integration. Manage Chats, Users, Groups, Contacts, Statuses.') and 'when' ('Use when the user wants to interact with Whatsapp data.') are present, but the 'when' clause is somewhat generic rather than listing concrete trigger phrases, fitting the anchor where both exist yet 'when' could be more specific.	4 / 5
Trigger Term Quality	It surfaces the natural term 'Whatsapp' and entity words (Chats, Contacts), but the trigger phrase 'interact with Whatsapp data' is generic and misses the common phrasings users actually say ('send a WhatsApp message', 'whatsapp someone').	3 / 5
Distinctiveness Conflict Risk	'Whatsapp integration' is a clearly scoped niche tied to a specific application with distinct triggers, giving minimal overlap risk with other skills, matching the clear-niche anchor.	5 / 5
	Total	15 / 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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/whatsapp/SKILL.md
Commit: f484c82

Reviewed: 3 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.