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/`:

| Platform | Reference | Key Characteristics |
|----------|-----------|-------------------|
| LinkedIn | `references/linkedin.md` | Professional tone, include an image or link, concise |
| X (Twitter) | `references/x.md` | 280-char limit (free users), conversational, punchy |
| Reddit | `references/reddit.md` | Casual and human-like, community-aware, anti-marketing |
| English Blog | `references/blog-en.md` | Slightly professional, structured, SEO-friendly |
| WeChat (公众号) | `references/wechat.md` | Storytelling, emotional hooks, twists and engagement |

## 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 paragrap