From ea1d71560fb4d9bd23fc5d3406740ac9601afab7 Mon Sep 17 00:00:00 2001
From: Hoid <hoid@openclaw>
Date: Tue, 17 Feb 2026 22:01:06 +0000
Subject: [PATCH] Enforce line breaks and short paragraphs in support emails

---
 skills/business/SKILL.md | 7 +++++--
 1 file changed, 5 insertions(+), 2 deletions(-)

diff --git a/skills/business/SKILL.md b/skills/business/SKILL.md
index cb0e0a1..8faae00 100644
--- a/skills/business/SKILL.md
+++ b/skills/business/SKILL.md
@@ -133,8 +133,11 @@ The support agent should:
 - NEVER use `**bold**`, `*italic*`, `[links](url)`, or any markdown in replies.
 - Use CAPS for emphasis (e.g., "WHAT HAPPENED" not "**What happened**").
 - Use plain URLs (e.g., "Visit https://docfast.dev" not "[DocFast](https://docfast.dev)").
-- Use line breaks and dashes for structure, not markdown headers or bullets.
-- Keep it clean and readable as raw plain text.
+- USE LINE BREAKS BETWEEN PARAGRAPHS AND SECTIONS. Never send a wall of text.
+- Each section/topic gets its own paragraph with a blank line before it.
+- Use short paragraphs (2-3 sentences max per block).
+- Use dashes or plain text lists for structure, not markdown bullets.
+- Keep it clean and readable as raw plain text — imagine reading it on a phone.
 
 Never let support tickets go unanswered. Response time matters for customer trust.