CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

whatsapp-message-management

Use when user wants to capture tasks, send briefings, or manage life via WhatsApp - leverages existing WhatsApp MCP for mobile-first workflow

Quality

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

tessl review fix ./skills/whatsapp-message-management/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

48%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 delivers a clear five-phase workflow with useful tool references and command patterns, but it is severely bloated by triple-duplicated briefing templates and overlapping example sections, and much of its code is non-executable pseudocode. Content that belongs in reference files is monolithically inlined.

Suggestions

Deduplicate the briefing content: keep the message formats and generateMorningBriefing/generateEveningBriefing implementations in one place instead of repeating them across Phase 3, the Integration section, and Technical Implementation Notes.

Replace the pseudocode orchestration JavaScript with either executable code or plain procedural instructions (e.g., 'call mcp__whatsapp__list_messages, match text against these regexes, then add to inbox via the processing-inbox skill'), removing undefined helpers like transcribeVoiceNote and addToInbox.

Move the message format templates, Use Cases/Examples, and the Life OS Command Reference into reference files (e.g., references/message-formats.md, references/examples.md, references/commands.md) and keep SKILL.md as a concise overview with clearly signaled one-level-deep links.

DimensionReasoningScore

Conciseness

The ~1050-line body is noticeably verbose: morning/evening briefing formats appear nearly verbatim three times (Phase 3, Integration, Technical Implementation), and the five Use Cases duplicate the three Examples' interactions, creating several padded, redundant sections.

2 / 5

Actionability

Concrete MCP tool signatures, parsing regexes, and a user command reference exist, but the orchestration JavaScript is pseudocode built on undefined functions (transcribeVoiceNote, addToInbox, getDailyPlan, isInDNDHours) with MCP tools invoked as JS functions — incomplete rather than executable guidance.

3 / 5

Workflow Clarity

Five phases are clearly sequenced with a copyable progress checklist, Phase 1 verifies the MCP connection, cron sends respect DND hours, and the Warning Signs section provides corrective feedback loops; only minor validation gaps remain (e.g., no post-capture verification step).

4 / 5

Progressive Disclosure

Section headers and a Quick Reference table give real structure, but no bundle files exist and roughly 600 lines of message templates, use cases, and implementation code that belong in separate reference files are inlined in SKILL.md.

3 / 5

Total

12

/

20

Passed

Description

70%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.

A solid description with an explicit 'Use when' trigger, third-person voice, and a clear WhatsApp/mobile niche. It falls short of top marks due to a vague 'manage life' clause, missing trigger synonyms, and omission of habit-tracking and query capabilities that dominate the skill body.

DimensionReasoningScore

Specificity

"capture tasks" and "send briefings" are concrete actions, but "manage life" is generic and core capabilities from the body (habit check-ins, reminders, contextual queries) are omitted, so coverage gaps exceed anchor 4's 'minor gaps' threshold.

3 / 5

Completeness

An explicit "Use when user wants to..." clause answers 'when' and embeds the 'what' (capture tasks, send briefings, manage life via WhatsApp), but the when-triggers could be more specific — no mention of habit reminders or queries that make up half the skill.

4 / 5

Trigger Term Quality

Natural terms like "WhatsApp", "capture tasks", and "send briefings" are present and would be said by users, but common variants such as "remind me", "message me", or "daily summary" are missing.

4 / 5

Distinctiveness Conflict Risk

"leverages existing WhatsApp MCP" carves a clear niche, but "capture tasks" and "manage life" overlap with the closely related Life OS skills (processing-inbox, daily-planning) the skill itself integrates with.

4 / 5

Total

15

/

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

skill_md_line_count

SKILL.md is long (1051 lines); consider splitting into references/ and linking

Warning

Total

15

/

16

Passed

Repository

kmondlane/ExoMind

Path

skills/whatsapp-message-management/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.