Content Writer

Content Writer

Overview

This skill enables writing high-quality content across different platforms and audiences. It dynamically selects the appropriate writing style based on the task, then applies that style consistently. Available styles include deep technical blog posts, social media content (LinkedIn, X/Twitter), tutorials, and more.

Style Selection

Before writing, determine the appropriate style based on these factors:

Style Decision Tree

Is this for social media?
├─ Yes → LinkedIn or X/Twitter style
│   ├─ Professional/B2B → LinkedIn Style
│   └─ Tech community/casual → X/Twitter Style
│
└─ No → Is this a technical blog post?
    ├─ Yes → What voice/style?
    │   ├─ Karpathy-style (conversational, personal, pragmatic) → Karpathy Style
    │   ├─ Opinion-forward analysis → Deep Technical Style
    │   ├─ Lightweight explainer → Simplified Technical Style
    │   └─ Tutorial/how-to → Tutorial Style
    │
    └─ No → What type?
        ├─ Announcement → Announcement Style
        ├─ Newsletter → Newsletter Style
        └─ Documentation → Documentation Style

Available Styles

1. Karpathy Style (Conversational Technical)

Use when: Writing technical content that feels personal and accessible. Best for blog posts about AI/ML, tutorials, or technical essays where you want the voice of an expert friend explaining things over coffee.

Characteristics:

• First-person, conversational tone ("I've found that...", "Here's what I learned...")
• Starts with personal experience or intriguing premise
• Progressive complexity (simple → detailed)
• Dry wit and occasional humor
• Honest about limitations and failures
• Pragmatic ("It only has to be right more often than not")
• Numbered frameworks and structured approaches
• Memorable, quotable lines

Load: references/karpathy-style.md for comprehensive guidance

Core Philosophy: "Don't be a hero. Start simple. Be patient."

Opening Hooks (choose one):

Example opening:

"I've trained a lot of neural networks over the years and I've come to find that the process isn't nearly as simple as it seems. They are a leaky abstraction. Here's what I've learned."

Tweet/X style (short-form):

• Pithy observations that compress insight
• Strong statements (90% true, ignore counterexample police)
• Unexpected connections between domains
• Personal candor about struggles and discoveries

2. Deep Technical Style (Opinion-Forward Analysis)

Use when: Writing opinion-forward technical analysis about AI, LLMs, agents, or engineering topics. Best for content targeting senior engineers who want bold takes backed by evidence.

Characteristics:

• Contrarian, opinion-forward opening hooks
• "Do the simple thing first" philosophy
• Concrete examples with specific numbers
• Takes clear positions and makes predictions
• Varied sentence length, active voice

Load: references/deep-technical-style.md for comprehensive guidance

Core Philosophy: "Do the simple thing first."

• Embrace the black box: Focus on inputs/outputs, not internal mechanisms
• Domain expertise over technical knowledge
• Simplicity as virtue: Start simple, add complexity only when necessary
• Opinion-forward: Take clear positions and make predictions boldly

Opening Hooks (choose one):

Example opening:

"Most AI architectures are overengineered. A single-threaded loop often outperforms elaborate multi-agent orchestrations."

3. LinkedIn Style

Use when: Writing professional content for LinkedIn—thought leadership, announcements, industry insights.

Characteristics:

• Hook in first line (appears before "see more")
• Short paragraphs (1-2 sentences each)
• Line breaks between paragraphs for mobile readability
• Personal angle or story
• Call-to-action or question at the end
• Strategic use of emojis (sparingly, professionally)
• 1300 characters ideal, 3000 max

Structure:

[Hook line that creates curiosity]

[Personal context or story - 2-3 short paragraphs]

[Key insight or lesson - bulleted if multiple points]

[Call-to-action or engaging question]

#relevanthashtags (3-5 max)

Example:

Most AI features never make it to production.

Not because the models aren't good enough.

Because teams build for demos, not for users.

After shipping 50+ AI features, here's what actually matters:

→ Start with the simplest possible implementation → Measure what users do, not what they say → Treat AI like any other code: test it, monitor it, iterate

What's the biggest lesson you've learned shipping AI?

4. X/Twitter Style

Use when: Writing for X/Twitter—quick insights, hot takes, thread explainers, engagement posts.

Characteristics:

• Punchy, high-signal first tweet
• No filler words
• Threads: numbered, each tweet standalone valuable
• Contrarian takes perform well
• Code snippets or visuals boost engagement
• 280 characters per tweet, threads typically 5-15 tweets

Thread structure:

1/ [Bold claim or hook]

2/ [Context or "here's why"]

3-N/ [Key points, one per tweet]

N+1/ [Takeaway or call-to-action]

[Optional: link to longer content]

Example:

Unpopular opinion: RAG is overengineered for most use cases.

A well-crafted system prompt often outperforms a poorly designed RAG pipeline.

Thread on when to use (and skip) RAG 🧵

5. Simplified Technical Style

Use when: Writing accessible technical content for broader audiences—explainers, introductions, "what is X" posts.

Characteristics:

• Start with the "why it matters" not the "what it is"
• Analogies to familiar concepts
• Avoid jargon or define it immediately
• Progressive complexity (simple → detailed)
• Concrete examples before abstract explanations

Example opening:

Every time you ask ChatGPT a question, something interesting happens behind the scenes. The AI doesn't just "know" the answer—it builds one, word by word, based on patterns it learned from millions of conversations.

6. Tutorial Style

Use when: Writing step-by-step guides, how-tos, implementation walkthroughs.

Characteristics:

• Clear prerequisites upfront
• Numbered steps
• Code blocks with comments
• "What you'll learn" summary
• Troubleshooting section
• Working example at the end

Structure:

## What You'll Build
[One sentence + screenshot/diagram]

## Prerequisites
[Bulleted list]

## Steps
### Step 1: [Action verb]
[Explanation + code]

### Step 2: ...

## Troubleshooting
[Common issues + solutions]

## Next Steps
[Where to go from here]