thread-to-article

Files (3)

• SKILL.md
• routing.yaml · evals/
• thread-to-article.skill

SKILL.md (first lines)

# thread-to-article

## Core Philosophy
Converting a high-performing social thread (from X/Twitter or LinkedIn) into a long-form article is not simply copy-pasting the 10 posts together and removing the tweet numbers. Social threads rely on fragmented cliffhangers, artificial suspense, and aggressive line breaks designed to maximize mobile scroll metrics. Transforming a thread into an authoritative article requires de-tweetification: weaving fragmented bullet points into cohesive narrative prose, adding missing technical evidence, building structured section hierarchies, and expanding nuance.

---

## 4-Step Thread-to-Article Transformation Pipeline

### Step 1: De-Tweetification & Architecture Extraction
1. **Purge Platform-Specific Gimmicks**:
   - Strip social cliffhangers: *"Here's why (and how to fix it) 🧵👇"*, *"Read this before you build"*, *"Bookmark this for later"*.
   - Combine fractured 1-sentence paragraphs into complete, coherent 3-to-4 sentence topical paragraphs.
2. **Extract the Core Thesis & Section Outline**:
   - Convert standalone tweets into hierarchical H2 and H3 headings representing logical argument stages.

### Step 2: Injecting Depth, Context & Primary Evidence
1. **Filling the Social Character Void**:
   - Social posts are forced to omit nuance due to character limits. In the article, restore the missing technical substance:
     - Add code blocks, terminal commands, and configuration snippets.
     - Cite primary empirical data sources, benchmarks, and historical context.
     - Explain the *counter-arguments* and trade-offs that couldn't fit in a 280-character post.

### Step 3: Transitional Connective Tissue & Flow
1. **Building Logical Bridges**:
   - In a thread, the reader scrolls past white space; in an article, ideas must transition smoothly from paragraph to paragraph.
   - Use connective logic: Cause-and-effect transitions, comparative contrasts, and illustrative examples to bind the sections together.

### Step 4: SEO Metadata, Visuals & Permalinks
1. **Packaging for Durable Search & Distribution**:
   - Generate SEO metadata: Target primary keyword, 55-character title, 140-character meta description.
   - Add architecture diagrams or charts to replace the visual weight of social screenshot cards.
   - Embed canonical backlinks referencing the original post or related documentation.

---

## Deliverable Format: Long-Form Technical Article (`EXPANDED-ARTICLE.md`)

```markdown
# [Engineered Article Title: Clear, Direct, No Clickbait]
*By [Author Name] | Reading Time: [X] mins | Published: [Date]*

## Introduction & The Core Bottleneck
[2 paragraphs establishing the technical problem, why traditional approaches fail, and the core thesis.]

## 1. [First Major Conceptual Section]
[Expanded prose providing depth, architectural diagrams, and real-world examples.]

```typescript
// Concrete implementation code that was too long for a tweet
export async function handleWebhookEvent(event: WebhookPayload) {
  const verified = verifySignature(event.signature, process.env.SECRET_KEY);
  if (!verified) throw new Error("Invalid HMAC signature");
  return processEventStream(event);
}
```

## 2. [Second Conceptual Section & Trade-off Analysis]
[Detailed evaluation of trade-offs, edge cases, and failure modes.]

## Conclusion & Practical Implementation
[Summary of takeaways with links to relevant open-source repositories or further reading.]
```

---

## Worked Example: From 8-Tweet Thread to 1,500-Word Deep Dive

- **Source**: An 8-post viral X thread on "Why Redis Pub/Sub crashes at high concurrency".
- **Transformation**: Removed all emoji hooks; expanded tweet #4 into a complete explanation of socket backpressure and buffer exhaustion with a Node.js code example; added a comparative benchmark chart.
- **Result**: Published on company blog; drove 14,000 organic reads and became the top Google search result for "Redis pub/sub buffer exhaustion".

---

## Verification Checklist

- [ ] All social thread gimmicks (emojis, "read on", "bookmark this") are completely eradicated.
- [ ] Fractured 1-line sentences are consolidated into rich, coherent paragraphs.
- [ ] Technical code snippets, architecture diagrams, and citations are added.
- [ ] Narrative flow incorporates clear transitional bridges between sections.
- [ ] Article includes optimized SEO metadata (Title, Slug, Meta Description).

---

## Anti-Patterns

- **The Lazy Stitch**: Pasting 10 tweets separated by horizontal rules and calling it a blog post.
- **Keeping Clickbait Intros**: Starting an article with "Most engineers do this wrong. Here are 7 secrets..."
- **Omitting Technical Proof**: Keeping the high-level social claims without adding the underlying code or benchmark evidence.

From poorvith-mp/skills-writing, MIT.

More from poorvith-mp/skills-writing