Rewrite Tone

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.

80 stars 13 forksWriting & Content

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add KerberosClaw/kc_ai_skills --skill rewrite-tone
Manual install
git clone --depth 1 https://github.com/KerberosClaw/kc_ai_skills.git /tmp/kc_ai_skills
mkdir -p ~/.claude/skills
cp -r /tmp/kc_ai_skills/rewrite-tone ~/.claude/skills/rewrite-tone

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# 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

## Anti-patterns
Read the full skill on GitHub

Details

Skill name
rewrite-tone
Path
rewrite-tone/SKILL.md
License
MIT
Repo updated
14 November 2026

FAQ

What does the Rewrite Tone skill do?

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.

How do I install the Rewrite Tone skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add KerberosClaw/kc_ai_skills --skill rewrite-tone. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Rewrite Tone popular?

It lives in KerberosClaw/kc_ai_skills, which has 80 GitHub stars and 13 forks, and is included in 1 curated skill list.

Related skills

Adr

80

KerberosClaw/kc_ai_skills

Use when a durable technical decision was just made in conversation and should be recorded, or when user asks to write/record an ADR (開 ADR / 記個決策 / 這要不要 ADR). Runs a three-gate check FIRST and actively talks the user out of writing one when the decision doesn't qualify — then writes a lightweight (title + 1-3 sentences) ADR following the repo's own ADR conventions if any exist. Repo conventions always override this skill's defaults. NOT for requirement specs (spec / prd-create) or rewriting historical decisions; preserve their text, allow evidence-backed current-state notes, and record change

Writing & ContentIn 1 list13

Align

80

KerberosClaw/kc_ai_skills

Reconcile existing repository documentation with the current implementation, especially after verified hotfixes or after QA in an unattended task. A manual run first asks whether to align only the docs a specific change touched (trigger scope) or rescan the whole repo; unattended runs use the scope the dispatch states and default to the whole repo. Follow cross-repo references for evidence; edit only documentation in the authorized repo, annotating conflicting historical records. Not for fixing code, deploying, inventing requirements, or building a new documentation suite.

Writing & ContentIn 1 list13

Character Lora

80

KerberosClaw/kc_ai_skills

Use when the user wants to build a consistent-identity LoRA for an original character — defining the character, generating a face/body-consistent multi-angle dataset (via the gpt-image-gen skill for codex image generation), captioning it, doing base-specific homework, training on a chosen base (Pony / Z-Image / others) on a local GPU, and producing a usable LoRA. This skill ORCHESTRATES the end-to-end pipeline and gates every expensive/irreversible step; it delegates actual image generation to gpt-image-gen and never improvises training settings from memory.

Images, Video & AudioIn 1 list13

Rewrite Tw

80

KerberosClaw/kc_ai_skills

Use when the user wants a Traditional Chinese (Taiwan) language review of Markdown or plain-text files — flagging genuinely comprehension-breaking grammar faults (missing subject, broken predicate, wrong measure word, misused connectives, inconsistent naming) and non-Taiwanese wording (mainland-Chinese terms, translationese) with replacement suggestions. High bar on grammar: only reports what actually misleads the reader; pure style preferences, punctuation nits and unavoidable loanwords are let through. Phase 1 is a read-only report; Phase 2 (applying edits) only runs after the user explicitl

Writing & ContentIn 1 list13

Rendering Untrusted Content

115

wdm0006/python-skills

Renders stored, authored, or imported content into HTML without shipping XSS — auditing every autoescape bypass (|safe, Markup, innerHTML), sanitizing Markdown output with an allowlist, escaping on both the server and the DOM, and writing sanitization tests that assert on the right copy of the string. Use when adding a Markdown or rich-text filter, rendering user/admin-authored content, reviewing a template that marks HTML trusted, building a client that injects values into innerHTML, or fixing an XSS report.

Writing & Content18

Shipping Build Artifacts

115

wdm0006/python-skills

Make the build step a real gate on what you actually distribute — build scripts that warn and exit 0 on a missing input, size checks with only an upper bound, hand-maintained file lists that drift from the entrypoints they must cover, committed bundles that go stale when only the source changes, GNU-only shell in release scripts that aborts on the other OS, and verification that runs against the source tree instead of the artifact. Use when writing or reviewing a build/package script, a `dist/` copy step, a release workflow that uploads a zip or installer, or a committed compiled asset.

Writing & Content18

Browse the most popular Claude skills, all writing & content skills, or write your own with the skills generator.