thread-to-article
Expand an X or LinkedIn thread into a structured article with added context, headings and links. Use when expanding social threads into long-form articles, or vice versa.
- License 许可
- MIT
- 最近更新
- 2026-10-02
- Stars
- ★ 0
- Forks
- 2
01 前言 Front Matter
- name
- thread-to-article
- group
- Repurposing and translation
- description
- Expand an X or LinkedIn thread into a structured article with added context, headings and links. Use when expanding social threads into long-form articles, or vice versa.
- last_reviewed
- 1788652800000
02 资源文件 2
- 参考文档evals/routing.yaml1005 B
- 其他thread-to-article.skill3.3 KB
03 SKILL.md 正文
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
- 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.
- 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
- 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.
- Social posts are forced to omit nuance due to character limits. In the article, restore the missing technical substance:
Step 3: Transitional Connective Tissue & Flow
- 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
- 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)
# [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.
04 同仓库更多 Skills
writing-taste
暂无简介
translation
Translate while preserving register, idiom and domain terms, flagging what doesn't carry across. Use when translating text across languages preserving nuance, tone, and idioms.
thread-to-blog-converter
Moved to modernized catalog in skillary. Removed in v4.1.
technical-writer
Moved to technical-docs in skills-writing. Removed in v4.1.
technical-docs
Write API references, user guides, setup manuals and architecture docs with consistent terminology. Use when writing developer documentation, API guides, or tutorials.
talk-writing
Write a conference talk or keynote: through-line, one idea per slide, opening hook and honest timing. Use when scripting keynote talks, conference presentations, or lightning talks.