CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

automate-whatsapp

Automate Whatsapp

Quality

33%

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 ./skills/antigravity-automate-whatsapp/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

0%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 SKILL.md body is a bare "404: Not Found" error string — the skill content was never written (or failed to download). It provides zero instructional value on every dimension, and there are no bundle files to offset it. The skill is non-functional as written.

Suggestions

Replace the placeholder body with actual instructions: what tooling or API to use (e.g. WhatsApp Business API, a client library) with a minimal working code example.

Add a short ordered workflow for the core task (e.g. authenticate -> send message -> verify delivery) with an explicit validation step, which is essential for messaging automation where sends are outward-facing.

If detailed material is needed later, keep SKILL.md as a concise overview and move API details into a references/ file with clearly signaled one-level-deep links.

DimensionReasoningScore

Conciseness

The entire body is the placeholder string "404: Not Found" — a failed fetch, not skill content. It occupies context without conveying anything Claude needs, so no token earns its place; this is maximal waste relative to value even though it is not verbose.

1 / 5

Actionability

There is no guidance at all: no code, no commands, no steps — only "404: Not Found". This matches "Entirely vague or abstract; no concrete code or commands" at the floor of the scale.

1 / 5

Workflow Clarity

"404: Not Found" contains no sequence, no steps, and no validation of any kind, matching "Steps missing or incoherent; no sequence; no validation for risky operations".

1 / 5

Progressive Disclosure

The body has no structure and no references, and the bundle contains no references/, scripts/, or assets/ files. Nothing is organized or navigable, matching the floor anchor for structure and navigation.

1 / 5

Total

4

/

20

Passed

Description

36%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 is a two-word domain label rather than a capability description. It names the domain and nothing else: no concrete actions, no usage triggers, and a misspelled product name. It would rarely be selected over more descriptive skills because neither what it does nor when to use it is stated.

Suggestions

State 2-4 concrete capabilities in third person, e.g. "Sends and schedules WhatsApp messages, reads incoming messages, and sets up automated reply bots via the WhatsApp Business API."

Add an explicit trigger clause, e.g. "Use when the user wants to send, schedule, or auto-respond to WhatsApp messages, or mentions WhatsApp bots or the WhatsApp Business API."

Use the correct capitalization "WhatsApp" so the name matches how users actually write it, and include common synonyms/extensions where relevant.

DimensionReasoningScore

Specificity

"Automate Whatsapp" names the domain (WhatsApp) but provides only a single generic verb with no concrete actions, matching "Names the domain but actions are minimal or generic" (cf. "Processes PDF files"). It is not a 3 because no concrete capability like "sends messages" or "creates bots" is stated.

2 / 5

Completeness

It has a vague "what" (automate which aspect of WhatsApp?) and no "when"/"Use when..." clause, a direct match to anchor 2 ("Has a vague 'what' and no 'when'"). Not 1 because a what is present; not 3 because the what is far from clear.

2 / 5

Trigger Term Quality

The keywords "Automate" and "Whatsapp" are domain-relevant, matching "Some relevant keywords but missing common variations or synonyms" (cf. "Works with PDF files"), though the product name is misspelled ("Whatsapp" vs "WhatsApp") and natural user phrases like "send WhatsApp messages" or "WhatsApp bot" are absent. It is above 2 ("Works with files") because the terms are specific to the domain, but below 4 because coverage is thin and the misspelling weakens matching.

3 / 5

Distinctiveness Conflict Risk

WhatsApp automation is a reasonably distinct niche, but with no trigger phrases or stated capabilities the description could overlap with any messaging- or chat-automation skill, matching "Somewhat specific but could still overlap with similar skills". Not 4 because the extreme brevity leaves the skill's boundaries undefined.

3 / 5

Total

10

/

20

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

description_field

'description' is very short (17 chars), consider making it more detailed

Warning

Total

15

/

16

Passed

Repository

boisenoise/skills-collections

Path

skills/antigravity-automate-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.