Automate Whatsapp
Install with Tessl CLI
npx tessl i github:sickn33/antigravity-awesome-skills --skill automate-whatsapp28
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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, consisting of only two words that fail to communicate what the skill actually does or when it should be used. While 'Whatsapp' provides minimal distinctiveness, the complete absence of specific actions, use cases, or trigger guidance makes this description inadequate for skill selection among multiple options.
Suggestions
Add specific concrete actions the skill performs (e.g., 'Send messages, read conversations, manage group chats, schedule messages via WhatsApp').
Include an explicit 'Use when...' clause with trigger terms like 'WhatsApp', 'messaging automation', 'send WhatsApp message', 'chat bot'.
Specify the scope and limitations to distinguish from other messaging or automation skills.
| 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 'WhatsApp bot'. | 2 / 3 |
Distinctiveness Conflict Risk | 'Whatsapp' provides some distinctiveness from other skills, but 'Automate' is so generic it could conflict with any automation-related skill. The lack of specific actions makes it unclear what this skill actually handles. | 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 contains no actual content - only a '404: Not Found' error message. There is nothing to evaluate as the skill body is completely empty of instructions, code, examples, or any guidance for automating WhatsApp.
Suggestions
Add actual content explaining how to automate WhatsApp (e.g., using libraries like whatsapp-web.js, pywhatkit, or the WhatsApp Business API)
Include executable code examples showing how to send messages, handle authentication, and interact with WhatsApp
Define a clear workflow with steps for setup, authentication, message sending, and error handling
Add safety constraints and rate limiting guidance to prevent account bans or misuse
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is just an error message '404: Not Found' with no actual skill content, making it impossible to evaluate token efficiency of real instructions. | 1 / 3 |
Actionability | No actionable guidance whatsoever - the content is an error page, not instructions for automating WhatsApp. | 1 / 3 |
Workflow Clarity | No workflow, steps, or processes are defined - the skill body contains only an error message. | 1 / 3 |
Progressive Disclosure | No structure, organization, or references exist - the content is completely empty of meaningful information. | 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 | |
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.