openclawd/config
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Enforce line breaks and short paragraphs in support emails

Browse source
This commit is contained in:
Hoid 2026-02-17 22:01:06 +00:00
parent 78cd552ce2
commit ea1d71560f
1 changed files with 5 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

7
skills/business/SKILL.md
View file

@ -133,8 +133,11 @@ The support agent should:
- NEVER use `**bold**`, `*italic*`, `[links](url)`, or any markdown in replies. - NEVER use `**bold**`, `*italic*`, `[links](url)`, or any markdown in replies.
- Use CAPS for emphasis (e.g., "WHAT HAPPENED" not "**What happened**"). - 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 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. - USE LINE BREAKS BETWEEN PARAGRAPHS AND SECTIONS. Never send a wall of text.
- Keep it clean and readable as raw plain 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. Never let support tickets go unanswered. Response time matters for customer trust.