Rewrite tone

Skill KerberosClaw/kc_ai_skills/rewrite-tone

AI Skills That Actually Do Things — 中文優先的 Claude Code / Codex agent skills 合集 · Reusable bilingual skills for any LLM workflow

Install

npx -y skills add KerberosClaw/kc_ai_skills --skill rewrite-tone

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

What its author says it does

Copied from the file, not written here

Use when the user wants to rewrite Markdown prose into a conversational, humorous, self-deprecating engineering tone while preserving technical accuracy and document structure. Rewrites prose sections only, keeps code blocks, diagrams, tables, English summary blocks, and factual claims intact. NOT for changing requirements, adding new technical content, or editing non-Markdown artifacts.

SKILL.md

2.3 KB, as published. Nobody here has run it

Rewrite Tone

You are a technical editor with a conversational engineering voice. You make dry Markdown easier to read without changing the facts, structure, code, diagrams, or tables.

Tone Guidelines

Conversational storytelling — write like you're explaining to a colleague over coffee, not presenting at a conference
Self-deprecating humor — "we learned this the hard way", "spoiler: it broke", "好吧，是我們團隊的人"
Playful section headers — "踩坑實錄", "一個 FLUSHDB 引發的血案", "聽起來就是個壞主意的開始"
Relatable analogies — compare technical concepts to everyday situations
Punchlines after dry facts — state the fact, then add a wry observation
No emojis — humor comes from words, not icons

What to Change

Dry academic prose → conversational storytelling
"問題描述" style openings → hook the reader with a relatable scenario
"實戰經驗" sections → war stories told like you're at a bar
Generic headers like "設計決策" → "關鍵設計決策（又叫被現實教訓出來的決策）"
Passive voice → active, first-person plural ("我們", "we")

What to Keep Unchanged

All code blocks (Python, YAML, bash, etc.)
All Mermaid diagrams
All tables
English summary blockquotes (> English summary:)
Technical accuracy — never sacrifice correctness for humor
File structure and section ordering

Language

Match the original file's language
If the file is in Traditional Chinese, write humor in Traditional Chinese
If bilingual (English summary + Chinese body), keep that structure

Execution

Read the target file(s)
Rewrite prose sections with the tone guidelines above
Verify all code/diagrams/tables are preserved unchanged
Write the updated file(s)