home / skills / openclaw / skills / wa-styler

wa-styler skill

safe

This skill enforces WhatsApp formatting rules to deliver clean, readable messages by avoiding markdown bloat and applying platform-specific styling.

npx playbooks add skill openclaw/skills --skill wa-styler

Review the files below or copy the command above to add this skill to your agents.

Files (2)

SKILL.md

1.2 KB

---
name: whatsapp-styler
description: Skill to ensure all messages sent to WhatsApp follow the platform's specific formatting syntax. It prevents markdown bloat and ensures a clean, mobile-first reading experience.
---

# WhatsApp Styler

This skill defines the strict formatting rules for WhatsApp to ensure the user sees clean, styled text without raw markdown symbols.

## Core Syntax Rules

1. *Bold*: Use single asterisks around text: `*texto*`. NEVER use double asterisks `**`.
2. _Italic_: Use single underscores around text: `_texto_`.
3. ~Strikethrough~: Use tildes around text: `~texto~`.
4. `Monospace`: Use triple backticks: ``` texto ``` (good for code or technical IDs).
5. *Bullet Lists*: Use a single asterisk followed by a space: `* Item`.
6. *Numbered Lists*: Use standard numbers: `1. Item`.
7. *Quotes*: Use the angle bracket: `> texto`.

## Prohibited Patterns (Do NOT use)

- No headers (`#`, `##`, `###`). Use *BOLD CAPS* instead.
- No markdown tables. Use bullet lists for structured data.
- No horizontal rules (`---`). Use a line of underscores if needed `__________`.
- No nested bold/italic symbols if it risks showing raw characters.

## Goal
The goal is a "Human-to-Human" look. Technical but clean.

Overview

This skill enforces WhatsApp-specific message formatting so sent content appears clean and mobile-friendly. It replaces or blocks non-supported markdown patterns and ensures text uses WhatsApp-native styling tokens. The result is human-readable messages that avoid raw markdown artifacts and display consistently across devices.

How this skill works

The skill scans outgoing message text for prohibited markdown patterns and transforms allowed elements to WhatsApp syntax. It enforces single-asterisk bold, single-underscore italics, tildes for strikethrough, triple backticks for monospace blocks, and standard list/quote tokens. When it detects disallowed patterns it either rewrites them into allowed forms or flags them for manual review.

When to use it

Sending automated notifications to WhatsApp users where consistent styling matters.
Converting rich-text content from other platforms into WhatsApp-safe formatting.
Preparing customer-facing messages that must render cleanly on mobile screens.
Sanitizing user-generated content before relaying it via WhatsApp.
Batch-processing archived messages to a WhatsApp-friendly format.

Best practices

Always prefer single asterisks for bold and single underscores for italics to avoid raw symbols.
Use triple backticks only for technical IDs, code snippets, or monospaced blocks.
Avoid headers and markdown tables; use BOLD CAPS for headings and bullet lists for structured data.
Keep lines short and mobile-first; break long paragraphs into bullets or short sentences.
Validate transformed output on a device preview to ensure no raw characters remain.

Example use cases

Transforming marketing copy exported from a CMS into WhatsApp-safe messages.
Sanitizing customer support transcripts before sending summaries to customers on WhatsApp.
Automated alerts from monitoring systems formatted with monospace IDs and clear bullets.
Archiving content that originated in markdown so it reads cleanly on mobile.
Preparing onboarding tips that require bold emphasis and short quoted notes.

FAQ

Will the skill change content semantics when rewriting formatting?

No—rewrites aim to preserve meaning while swapping prohibited tokens for WhatsApp-safe equivalents; manual review is recommended for complex cases.

Can it handle nested styling like bold+italic?

Nested bold/italic is discouraged because it can produce raw characters; the skill will avoid nesting and suggest a flat styling alternative.