Automate Whatsapp
28
Quality
11%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/antigravity-automate-whatsapp/SKILL.mdQuality
Discovery
22%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description is severely underdeveloped with only two words that provide minimal guidance for skill selection. It lacks specific capabilities, use-case triggers, and actionable detail. The only redeeming quality is the mention of 'Whatsapp' which provides some domain specificity.
Suggestions
Add specific concrete actions like 'Send messages, read conversations, manage group chats, schedule messages' to clarify what automation means.
Include a 'Use when...' clause with explicit triggers such as 'Use when the user wants to automate WhatsApp messaging, send bulk messages, or integrate WhatsApp with other workflows.'
Add natural keyword variations users might say: 'WhatsApp messages', 'chat automation', 'messaging bot', 'WhatsApp API'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever - just 'Automate' which is extremely vague. It doesn't specify what automation means (sending messages, reading chats, managing groups, etc.). | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the vague 'automate' and completely lacks any 'when to use' guidance or explicit triggers. | 1 / 3 |
Trigger Term Quality | 'Whatsapp' is a natural keyword users would say, but there are no other trigger terms covering variations like 'messaging', 'chat automation', 'send messages', or specific WhatsApp features. | 2 / 3 |
Distinctiveness Conflict Risk | 'Whatsapp' provides some distinctiveness from other messaging or automation skills, but 'Automate' is so generic it could conflict with any automation-related skill. | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill content is completely empty/broken, containing only a '404: Not Found' error message instead of actual skill instructions. There is no usable content to evaluate - the skill file appears to have failed to load or was never properly created.
Suggestions
Create actual skill content that explains how to automate WhatsApp, including specific libraries or APIs to use (e.g., whatsapp-web.js, Twilio WhatsApp API)
Add executable code examples showing how to send messages, handle incoming messages, or perform common automation tasks
Include safety considerations and rate limiting guidance since WhatsApp automation can lead to account bans
Document the setup process including authentication requirements and any necessary configuration steps
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is just an error message '404: Not Found' with no actual skill content, providing zero useful information. | 1 / 3 |
Actionability | No concrete guidance, code, commands, or instructions are provided - the content is completely non-actionable. | 1 / 3 |
Workflow Clarity | No workflow, steps, or processes are defined - the content is an error message with no instructional value. | 1 / 3 |
Progressive Disclosure | No structure, organization, or references exist - the content is a single error line with no meaningful content to organize. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_field | 'description' is very short (17 chars), consider making it more detailed | Warning |
Total | 10 / 11 Passed | |
5c5ae21
Table of Contents
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.