whatsapp-formatting
The whatsapp-formatting skill enables proper message formatting and user mentions in WhatsApp conversations. Use it when responding in a WhatsApp chat identified by a JID ending in @s.whatsapp.net or @g.us. It ensures mentions render as clickable, bold tags that notify recipients by using @<phonenumber> syntax, while also supporting WhatsApp's text styling conventions including bold, italic, strikethrough, and monospace formatting.
git clone --depth 1 https://github.com/nanocoai/nanoclaw /tmp/whatsapp-formatting && cp -r /tmp/whatsapp-formatting/container/skills/whatsapp-formatting ~/.claude/skills/whatsapp-formattingSKILL.md
# WhatsApp Message Formatting WhatsApp uses its own lightweight markup and a phone-number-based mention syntax. The host's WhatsApp adapter (Baileys) handles markdown conversion automatically, but **mentions are only protocol-level mentions if you use the right syntax** — otherwise they render as plain text and don't notify the recipient. ## How to detect WhatsApp context You're in a WhatsApp conversation when any of these are true: - The chat JID / platform id ends with `@s.whatsapp.net` (1-on-1 DM) - The chat JID / platform id ends with `@g.us` (group) - Your inbound message metadata has `chatJid` matching the above ## Mentions — the important part To tag a user so their name appears **bold and clickable** in WhatsApp and they get a push notification, write the `@` followed by their phone number digits (no `+`, no spaces, no display name): ``` @15551234567 can you confirm? ``` The adapter scans your outgoing text for `@<digits>` (5–15 digits, optional leading `+` is stripped) and tells WhatsApp to render them as real mention tags. **The sender's phone JID is always in your inbound message metadata.** When a user writes to you, inbound `content.sender` looks like `15551234567@s.whatsapp.net`. The part before the `@` is exactly what you put after `@` when tagging them back. ### Wrong vs right | You write | What recipients see | |-----------|---------------------| | `@Adam can you...` | Plain text `@Adam`. No tag, no notification. | | `@15551234567 can you...` | Bold/blue **@Adam** (or whatever name they're saved as), notification fires. | | `@+15551234567 ...` | Same as above — adapter strips the `+`. | ### Picking who to tag - In a DM, there's no real need to tag the recipient (they already see every message), but tagging still works if you want emphasis. - In a group, look at the `participants` / inbound `content.sender` to find the JID of the person you mean. Don't guess from display names — pushNames can collide and are not reliable. - If you don't know the JID, just refer to the person by name in plain prose. Don't write `@<name>` — it won't tag and it will look like a tag that failed. ## Text styles WhatsApp uses single-character delimiters, *not* doubled like standard Markdown. | Style | Syntax | Renders as | |-------|--------|------------| | Bold | `*bold*` | **bold** | | Italic | `_italic_` | *italic* | | Strikethrough | `~strike~` | ~strike~ | | Monospace | `` `code` `` | `code` | | Block monospace | ```` ```block``` ```` | preformatted block | The adapter converts standard Markdown (`**bold**`, `[link](url)`, `# heading`) to the WhatsApp-native form automatically, so you don't have to think about it — but be aware that single asterisks become italics, not bold. ## What not to do - Don't write `<@U123>` (that's Slack), `<@!123>` (Discord), or any other channel's mention syntax. - Don't paste a full JID like `@15551234567@s.whatsapp.net` in the text — only the digits before the JID's `@` go after your `@`. - Don't try to tag display names. WhatsApp has no display-name-based mention API.
Add local office-document-to-Markdown conversion to NanoClaw agent containers with the pinned Firecrawl AnyDoc CLI. Use when agents need to read attached Word, PowerPoint, Excel, OpenDocument, RTF, EPUB, CSV, or text-based PDF files without uploading them to a hosted parser.
Add Atomic Chat MCP server so the container agent can call local models served by the Atomic Chat desktop app via its OpenAI-compatible API.
Add clidash — a zero-dependency, read-only web dashboard that derives its tabs and tables at runtime from any CLI that lists resources as JSON. Ships pre-wired for NanoClaw's ncl CLI (agent groups, sessions, channels, users, roles), plus message-activity charts, a log tail, and a read-only file viewer for group skills/CLAUDE.md/profiles.
Use Codex (OpenAI's codex app-server) as a full agent provider — planning, tool orchestration, MCP tools, server-side history, session resume — alongside or instead of Claude. ChatGPT subscription or OpenAI API key, vault-only via OneCLI. Per-group via `ncl groups config update --provider codex`. Distinct from using OpenAI as an MCP tool (where Claude remains the planner).
Add a monitoring dashboard to NanoClaw. Installs @nanoco/nanoclaw-dashboard and a pusher that sends periodic JSON snapshots.
Add DeltaChat channel integration via @deltachat/stdio-rpc-server. Native adapter — no Chat SDK bridge. Email-based messaging with end-to-end encryption.
Add Dial channel integration — a real phone number for SMS and AI voice calls via the Dial platform (getdial.ai). Native adapter — no Chat SDK bridge.
Add another phone number to an existing Dial channel — a second (or third) public line for the agent, so one NanoClaw install answers SMS and AI voice calls on multiple numbers. Use when Dial is already installed and the operator wants an additional number (e.g. a personal line plus a support line). Requires the Dial channel to already be installed (see /add-dial).