Content Rewrite

Content Rewrite

Adapt a piece of source content (article, blog post, announcement, etc.) into platform-specific versions for distribution across social media and content platforms.

When to Use

Use this skill when the user provides source content and wants it rewritten or adapted for one or more target platforms.

Confirm Before Writing

Before starting, always ask the user:

1. Perspective / voice — Should the content use first person ("I", telling a personal story) or third person (stating facts objectively)? This significantly affects tone and credibility on every platform. 2. Target platforms — Which platforms to write for? (LinkedIn, X, Reddit, English blog, WeChat, or all)

Platform References

Each platform has a dedicated style guide under references/:

General Guidelines

• No AI smell — All platforms require natural, human-sounding writing. Avoid robotic patterns, excessive structure, and formulaic transitions. See the remove-ai-style skill for detailed rules.
• Conversational tone — Even on professional platforms like LinkedIn, keep the writing approachable. Nobody likes reading corporate speak.
• Platform-native — Each version should feel like it was written by someone who actually uses that platform, not cross-posted from a press release.
• Adapt, don't translate — Rewriting for a platform means rethinking the content for that audience, not just reformatting the same text.

English Blog Style Guide

Tone

• Slightly professional but still readable — think "well-written tech blog", not "academic paper".
• Authoritative without being stiff. You know your stuff and you explain it clearly.

Format

• Title: Clear, specific, and SEO-friendly. Include the key topic. 60–70 characters ideal.
• Introduction: Start with the problem or context. Why should the reader care? Keep it to 2–3 sentences.
• Body: Use headers (H2, H3) to break up sections. Each section should have one clear point.
• Length: 800–1500 words for standard posts. Can go longer for deep technical content.
• Code examples: Include runnable code snippets when applicable. Keep them short and focused.
• Conclusion: Summarize the key takeaway. Include a CTA (try the tool, read the docs, etc.) without being pushy.

Do

• Use concrete examples and real numbers (benchmarks, comparisons).
• Link to relevant resources, docs, or related posts.
• Include diagrams or screenshots to illustrate complex concepts.
• Write scannable content — someone skimming headers should get the gist.

Don't

• Don't pad with fluff. Every paragraph should earn its place.
• Don't over-explain basics if the target audience is technical.
• Don't write a wall of text without visual breaks.
• Don't stuff keywords unnaturally for SEO — write for humans first.

LinkedIn Style Guide

Tone

• Professional but approachable — think "smart colleague sharing an insight", not "corporate press release".
• Okay to show personality and share opinions, but keep it grounded.

Format

• Keep it concise: 150–300 words is the sweet spot. People scroll fast on LinkedIn.
• Open with a hook — the first 2 lines show before "see more", so make them count.
• Use short paragraphs (1–3 sentences each). Wall of text = scroll past.
• Include an image, diagram, or link when possible — posts with visuals get significantly more engagement.
• End with a question or call-to-action to encourage comments.

Do

• Share a specific takeaway or lesson, not just an announcement.
• Tag relevant people or companies if appropriate.
• Use 2–3 relevant hashtags at the end (not inline).

Don't

• Don't write like a press release or advertisement.
• Don't use buzzwords like "synergy", "leverage", "game-changer" unless ironically.
• Don't dump a full article — link to it and give people a reason to click.

Reddit Style Guide

Tone

• Casual, genuine, and human. Reddit users have a finely tuned radar for marketing speak — anything that smells like an ad gets downvoted hard.
• Write like you're a regular community member sharing something useful, not a brand promoting a product.
• Self-deprecating humor and honest admissions ("this took me way too long to figure out") build trust.

Format

• Post title: Clear and specific. Avoid clickbait. Good: "How I cut vector search latency by 40% with this indexing trick". Bad: "You won't believe this amazing new tool!"
• Post body: Conversational paragraphs. Tell the story of the problem, what you tried, what worked. Include code snippets or screenshots when relevant.
• Comments/replies: Keep them short and direct. Match the energy of the thread — don't write a formal essay in a casual discussion.

Do

• Provide value first — share knowledge, a tutorial, benchmarks, or a real experience.
• Mention your own tool/project only if it's genuinely relevant to the discussion.
• Engage with replies. Reddit rewards conversation, not broadcast.
• Use subreddit-appropriate language and norms. r/MachineLearning has different expectations than r/Python.

Don't

• Don't write like a press release or product announcement.
• Don't use phrases like "we're thrilled to announce", "revolutionary solution", or "cutting-edge technology".
• Don't drop links without context — explain why someone should care.
• Don't astroturf (fake grassroots enthusiasm). Be upfront if you're affiliated with a project.
• Don't over-format with headers and bullet points for short posts — it looks unnatural on Reddit.

微信公众号 Style Guide

语气

• 故事性强，有代入感。读者是在手机上刷文章，你需要像讲故事一样把他们拉进来。
• 可以带一些情绪 —— 困惑、惊喜、恍然大悟。让读者跟着你的情绪走。
• 不要端着，不要写得像新闻稿或者产品说明书。

结构

• 标题：要有吸引力，可以用疑问句、数字、或制造好奇心。比如「我花了三天踩的坑，你五分钟就能避开」比「XX工具使用指南」好得多。
• 开头：用一个场景、问题、或者小故事开头。不要上来就介绍产品或技术概念。
• 中间：叙事为主，穿插技术内容。关键是让读者感觉在听你讲经历，而不是在读文档。适当制造反转 —— 「我以为这样就搞定了，结果……」
• 结尾：给一个清晰的总结或感悟。可以带一句引导关注/点赞的话，但不要太生硬。
• 长度：1500–3000 字比较合适。太短撑不起故事，太长读者会划走。

要做的

• 用口语化的表达，像在和朋友聊天。
• 适当用一些「我」的视角来讲故事（如果确认用第一人称）。
• 段落要短，3–5 行一段。手机屏幕上长段落非常难读。
• 关键信息可以加粗，但不要整篇都在加粗。
• 可以穿插一些图片、截图、代码片段来打破纯文字的沉闷。

不要做的

• 不要写成产品广告或者新闻通稿。
• 不要堆砌术语 —— 如果必须用，简单解释一下。
• 不要一开头就「随着XX技术的发展……」，这是最典型的 AI 味开头。
• 不要全篇都是平铺直叙，要有节奏变化 —— 有紧有松，有疑问有解答。

X (Twitter) Style Guide

Character Limits

• Free users: 280 characters per tweet.
• Premium users: up to 25,000 characters (but long posts show a truncated 280-char preview with "Show more").
• Default to 280 characters unless the user specifies they have Premium.

Tone

• Punchy, conversational, opinionated.
• Write like you're texting a smart friend, not writing a report.
• Hot takes and strong opinions perform well — lukewarm statements get ignored.

Format

• For 280-char tweets: one clear idea per tweet. No filler words.
• For longer content: consider a thread (multiple connected tweets). Number them (1/5, 2/5...) or use a hook tweet + replies.
• Thread structure: hook tweet first (the one people see in feed), then supporting points.
• Emojis are fine in moderation — don't overdo it.

Do

• Start with a hook or surprising statement.
• Use plain language. Remove every word that doesn't earn its place.
• Quote-tweet or reply to relevant conversations when the content fits.
• Include a link in the last tweet of a thread, not the first (algorithm penalty).

Don't

• Don't write like a LinkedIn post (too formal, too long).
• Don't use hashtags excessively — 0–1 is fine, 5+ looks spammy.
• Don't start with "I'm excited to announce..." — nobody cares, get to the point.
• Don't thread things that can be said in one tweet.