Name: whatsable
Rating: 56.8 (1 reviews)
Author: membranedev

whatsable

WhatsAble integration. Manage data, records, and automate workflows. Use when the user wants to interact with WhatsAble data.

Quality

65%

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/whatsable/SKILL.md

Quality

Content

67%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 well-structured, actionable guide with executable Membrane CLI commands and a real connection-state feedback loop. Its main weaknesses are an unactionable speculative opening paragraph and a broken 'Step 2' cross-reference.

Suggestions

Delete the speculative opening paragraph ('WhatsAble is an app that likely focuses on accessibility...'); replace with a one-line factual description of what WhatsAble does.

Fix the 'skip to Step 2' reference by labeling the post-connection sections as numbered steps (Step 2: Search for actions, Step 3: Run actions) or rewording to 'skip to Searching for actions'.

Merge or differentiate 'Searching for actions' and 'Popular actions', which both demonstrate action discovery, to remove redundancy.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete commands, but opens with unactionable speculation ('likely focuses on accessibility features... probably used by individuals with disabilities') and includes padding like 'so you can focus on the integration logic rather than auth plumbing'.	3 / 5
Actionability	Provides concrete, copy-paste-ready commands for install, auth, connection, action discovery/run, and proxying with a flags table, but relies on placeholders (CONNECTION_ID, QUERY) and the 'Popular actions' section repeats discovery guidance.	4 / 5
Workflow Clarity	Clear install→auth→connect→search→run sequence with a genuine feedback loop in the connection state machine (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR polling), but the 'skip to Step 2' reference points to a non-existent Step 2.	4 / 5
Progressive Disclosure	No bundle files exist, so all content is inline in well-organized sections with no nested references; at ~145 lines it exceeds the simple-skill threshold, and minor redundancy between 'Searching for actions' and 'Popular actions' keeps it below 5.	4 / 5
	Total	15 / 20 Passed

Description

62%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 answers both 'what' and 'when' with an explicit third-person trigger clause tied to a specific app, but its capability list is generic ('manage data, records, automate workflows') rather than concrete. Trigger keyword coverage is adequate but lacks natural synonyms.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete WhatsAble capabilities such as 'send template messages, manage contacts, run campaigns, and build flows'.

Add natural trigger phrases and synonyms a user would actually say, e.g. 'Use when the user wants to send WhatsApp messages, manage contacts or campaigns, or automate WhatsAble workflows'.

Name the WhatsApp/messaging context explicitly to sharpen distinctiveness from other data-integration skills.

Dimension	Reasoning	Score
Specificity	Names the domain (WhatsAble) and a few actions ('Manage data, records, and automate workflows'), but the actions are generic rather than concrete like 'extract text' or 'fill forms', placing it between anchor 2 and 3.	3 / 5
Completeness	Provides both a 'what' ('Manage data, records, and automate workflows') and an explicit third-person 'when' ('Use when the user wants to interact with WhatsAble data'); the 'what' is generic so it stops short of anchor 5.	4 / 5
Trigger Term Quality	Includes relevant keywords ('WhatsAble', 'data, records, workflows', 'interact with WhatsAble data') but lacks common natural variations or synonyms a user would naturally say, matching anchor 3.	3 / 5
Distinctiveness Conflict Risk	Tied to a named app (WhatsAble) giving it a clear niche with mostly distinct triggers, though 'manage data/records' language carries minor overlap risk with other integration skills.	4 / 5
	Total	14 / 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/whatsable/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.