WhatsApp Styler

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.

Security Scan

Instruction-only skill that enforces WhatsApp-style text formatting; its requirements and instructions are consistent with the stated purpose and it requests no credentials or installs.

Purpose & Capability

The name/description (WhatsApp formatting) align with the SKILL.md rules. No binaries, env vars, or installs are requested — consistent with a simple formatting helper.

Instruction Scope

SKILL.md contains only formatting rules (what to convert/avoid). It does not instruct reading files, accessing environment variables, making network calls, or transmitting data elsewhere.

Install Mechanism

No install spec and no code files — lowest-risk model (instruction-only). Nothing will be written to disk or fetched at install time.

Credentials

The skill requests no environment variables, credentials, or config paths, which is appropriate for a local text-formatting guideline.

Persistence & Privilege

always is false and model invocation is allowed (normal). The skill does not request permanent presence or elevated privileges and does not modify other skills/config.

Assessment

This is an instruction-only formatting guide and appears internally consistent and low-risk: it doesn't install code or ask for credentials. Before relying on it, test a few sample messages in the actual WhatsApp clients you target (some formatting behaviors vary by platform/version). If a future version of this skill asks for API keys, install steps, or access to files/configs, treat that as a material change and re-evaluate — those would be unnecessary for a pure formatter and could indicate a higher risk.

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.