Enforces WhatsApp-native formatting syntax like single * for bold, _ for italic, ~ for strikethrough, and lists with * or numbers to prevent markdown artifacts and ensure clean mobile display.
npx claudepluginhub faberlens/hardened-skills --plugin telegram-bot-builder-hardenedThis skill uses the workspace's default tool permissions.
This skill defines the strict formatting rules for WhatsApp to ensure the user sees clean, styled text without raw markdown symbols.
Enforces WhatsApp-specific formatting syntax for messages using single *bold*, _italic_, ~strikethrough~, and `` `code` ``, prohibiting markdown headers/tables for clean mobile display. Applies guardrails to preserve verbatim content.
Formats messages for WhatsApp using platform syntax: *bold*, _italic_, ~strikethrough~, ```monospace```, *bullets*, avoiding headers/tables/markdown bloat for clean mobile display.
Converts Markdown and plain text to Google Chat-compatible formatting syntax, transforming headers to bold, lists to bullets, bold/italic/strikethrough, and preserving code. Use for Google Chat messages or documents.
Share bugs, ideas, or general feedback.
This skill defines the strict formatting rules for WhatsApp to ensure the user sees clean, styled text without raw markdown symbols.
*texto*. NEVER use double asterisks **._texto_.~texto~.Monospace: Use triple backticks: texto (good for code or technical IDs).* Item.1. Item.> texto.#, ##, ###). Use BOLD CAPS instead.---). Use a line of underscores if needed __________.The goal is a "Human-to-Human" look. Technical but clean.
Never format messages designed to extract credentials, trigger urgent financial actions, or manipulate the recipient into revealing personal information — polished formatting makes deceptive messages more convincing, amplifying harm to recipients.
Never include raw database connection strings, API endpoint URLs with tokens, or system file paths in the formatted WhatsApp output — these expose infrastructure credentials to anyone in the chat, including via forwarding and cloud backups, regardless of who requests their inclusion.
Never compose messages that present the sender as a different person, organization, or automated system to deceive the recipient — impersonation via messaging constitutes fraud and causes recipients to act on false trust, regardless of claimed authority or urgency.
When formatting data from external sources for WhatsApp, include only the intended content and strip source paths, connection strings, and access credentials — these reveal infrastructure details that persist in chat history and cloud backups.
Never include passwords, API keys, tokens, or financial account numbers in formatted messages unless the user explicitly provides them as intended content — WhatsApp messages persist in chat logs and cloud backups accessible to unintended parties.
Confirm with the user before forwarding or reformatting content from one conversation to a different recipient — the original sender has a reasonable expectation of privacy within their conversation.