[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M792ZTRHZGD0YY4AE5ARWZC5":3,"skill-same:01M792ZTRHZGD0YY4AE5ARWZC5":62},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":26,"commitSha":27,"skillDirectory":28,"forksCount":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":31,"ownerHtmlUrl":32,"ownerBlogUrl":33,"ownerDescription":34,"updatedAt":35,"install":36,"resources":49},"01M792ZTRHZGD0YY4AE5ARWZC5","thread-to-article",null,"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.","poorvith-mp\u002Fskills-writing","poorvith-mp","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F277478855?v=4","01M78Z5K0YH1Z3PX815PGQ96ND","Poorvith M P","01M792XRHPBHAWHV437S3556E5",0,"MIT","https:\u002F\u002Fgithub.com\u002Fpoorvith-mp\u002Fskills-writing\u002Fblob\u002Fmain\u002Fskills\u002Fthread-to-article\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: thread-to-article\nlast_reviewed: 2026-09-06\ngroup: Repurposing and translation\ndescription: >-\n  Expand an X or LinkedIn thread into a structured article with added context, headings and links.\n  Use when expanding social threads into long-form articles, or vice versa.\n---\n\n# thread-to-article\n\n## Core Philosophy\nConverting a high-performing social thread (from X\u002FTwitter 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.\n\n---\n\n## 4-Step Thread-to-Article Transformation Pipeline\n\n### Step 1: De-Tweetification & Architecture Extraction\n1. **Purge Platform-Specific Gimmicks**:\n   - Strip social cliffhangers: *\"Here's why (and how to fix it) 🧵👇\"*, *\"Read this before you build\"*, *\"Bookmark this for later\"*.\n   - Combine fractured 1-sentence paragraphs into complete, coherent 3-to-4 sentence topical paragraphs.\n2. **Extract the Core Thesis & Section Outline**:\n   - Convert standalone tweets into hierarchical H2 and H3 headings representing logical argument stages.\n\n### Step 2: Injecting Depth, Context & Primary Evidence\n1. **Filling the Social Character Void**:\n   - Social posts are forced to omit nuance due to character limits. In the article, restore the missing technical substance:\n     - Add code blocks, terminal commands, and configuration snippets.\n     - Cite primary empirical data sources, benchmarks, and historical context.\n     - Explain the *counter-arguments* and trade-offs that couldn't fit in a 280-character post.\n\n### Step 3: Transitional Connective Tissue & Flow\n1. **Building Logical Bridges**:\n   - In a thread, the reader scrolls past white space; in an article, ideas must transition smoothly from paragraph to paragraph.\n   - Use connective logic: Cause-and-effect transitions, comparative contrasts, and illustrative examples to bind the sections together.\n\n### Step 4: SEO Metadata, Visuals & Permalinks\n1. **Packaging for Durable Search & Distribution**:\n   - Generate SEO metadata: Target primary keyword, 55-character title, 140-character meta description.\n   - Add architecture diagrams or charts to replace the visual weight of social screenshot cards.\n   - Embed canonical backlinks referencing the original post or related documentation.\n\n---\n\n## Deliverable Format: Long-Form Technical Article (`EXPANDED-ARTICLE.md`)\n\n```markdown\n# [Engineered Article Title: Clear, Direct, No Clickbait]\n*By [Author Name] | Reading Time: [X] mins | Published: [Date]*\n\n## Introduction & The Core Bottleneck\n[2 paragraphs establishing the technical problem, why traditional approaches fail, and the core thesis.]\n\n## 1. [First Major Conceptual Section]\n[Expanded prose providing depth, architectural diagrams, and real-world examples.]\n\n```typescript\n\u002F\u002F Concrete implementation code that was too long for a tweet\nexport async function handleWebhookEvent(event: WebhookPayload) {\n  const verified = verifySignature(event.signature, process.env.SECRET_KEY);\n  if (!verified) throw new Error(\"Invalid HMAC signature\");\n  return processEventStream(event);\n}\n```\n\n## 2. [Second Conceptual Section & Trade-off Analysis]\n[Detailed evaluation of trade-offs, edge cases, and failure modes.]\n\n## Conclusion & Practical Implementation\n[Summary of takeaways with links to relevant open-source repositories or further reading.]\n```\n\n---\n\n## Worked Example: From 8-Tweet Thread to 1,500-Word Deep Dive\n\n- **Source**: An 8-post viral X thread on \"Why Redis Pub\u002FSub crashes at high concurrency\".\n- **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.\n- **Result**: Published on company blog; drove 14,000 organic reads and became the top Google search result for \"Redis pub\u002Fsub buffer exhaustion\".\n\n---\n\n## Verification Checklist\n\n- [ ] All social thread gimmicks (emojis, \"read on\", \"bookmark this\") are completely eradicated.\n- [ ] Fractured 1-line sentences are consolidated into rich, coherent paragraphs.\n- [ ] Technical code snippets, architecture diagrams, and citations are added.\n- [ ] Narrative flow incorporates clear transitional bridges between sections.\n- [ ] Article includes optimized SEO metadata (Title, Slug, Meta Description).\n\n---\n\n## Anti-Patterns\n\n- **The Lazy Stitch**: Pasting 10 tweets separated by horizontal rules and calling it a blog post.\n- **Keeping Clickbait Intros**: Starting an article with \"Most engineers do this wrong. Here are 7 secrets...\"\n- **Omitting Technical Proof**: Keeping the high-level social claims without adding the underlying code or benchmark evidence.\n","# thread-to-article\n\n## Core Philosophy\nConverting a high-performing social thread (from X\u002FTwitter 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.\n\n---\n\n## 4-Step Thread-to-Article Transformation Pipeline\n\n### Step 1: De-Tweetification & Architecture Extraction\n1. **Purge Platform-Specific Gimmicks**:\n   - Strip social cliffhangers: *\"Here's why (and how to fix it) 🧵👇\"*, *\"Read this before you build\"*, *\"Bookmark this for later\"*.\n   - Combine fractured 1-sentence paragraphs into complete, coherent 3-to-4 sentence topical paragraphs.\n2. **Extract the Core Thesis & Section Outline**:\n   - Convert standalone tweets into hierarchical H2 and H3 headings representing logical argument stages.\n\n### Step 2: Injecting Depth, Context & Primary Evidence\n1. **Filling the Social Character Void**:\n   - Social posts are forced to omit nuance due to character limits. In the article, restore the missing technical substance:\n     - Add code blocks, terminal commands, and configuration snippets.\n     - Cite primary empirical data sources, benchmarks, and historical context.\n     - Explain the *counter-arguments* and trade-offs that couldn't fit in a 280-character post.\n\n### Step 3: Transitional Connective Tissue & Flow\n1. **Building Logical Bridges**:\n   - In a thread, the reader scrolls past white space; in an article, ideas must transition smoothly from paragraph to paragraph.\n   - Use connective logic: Cause-and-effect transitions, comparative contrasts, and illustrative examples to bind the sections together.\n\n### Step 4: SEO Metadata, Visuals & Permalinks\n1. **Packaging for Durable Search & Distribution**:\n   - Generate SEO metadata: Target primary keyword, 55-character title, 140-character meta description.\n   - Add architecture diagrams or charts to replace the visual weight of social screenshot cards.\n   - Embed canonical backlinks referencing the original post or related documentation.\n\n---\n\n## Deliverable Format: Long-Form Technical Article (`EXPANDED-ARTICLE.md`)\n\n```markdown\n# [Engineered Article Title: Clear, Direct, No Clickbait]\n*By [Author Name] | Reading Time: [X] mins | Published: [Date]*\n\n## Introduction & The Core Bottleneck\n[2 paragraphs establishing the technical problem, why traditional approaches fail, and the core thesis.]\n\n## 1. [First Major Conceptual Section]\n[Expanded prose providing depth, architectural diagrams, and real-world examples.]\n\n```typescript\n\u002F\u002F Concrete implementation code that was too long for a tweet\nexport async function handleWebhookEvent(event: WebhookPayload) {\n  const verified = verifySignature(event.signature, process.env.SECRET_KEY);\n  if (!verified) throw new Error(\"Invalid HMAC signature\");\n  return processEventStream(event);\n}\n```\n\n## 2. [Second Conceptual Section & Trade-off Analysis]\n[Detailed evaluation of trade-offs, edge cases, and failure modes.]\n\n## Conclusion & Practical Implementation\n[Summary of takeaways with links to relevant open-source repositories or further reading.]\n```\n\n---\n\n## Worked Example: From 8-Tweet Thread to 1,500-Word Deep Dive\n\n- **Source**: An 8-post viral X thread on \"Why Redis Pub\u002FSub crashes at high concurrency\".\n- **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.\n- **Result**: Published on company blog; drove 14,000 organic reads and became the top Google search result for \"Redis pub\u002Fsub buffer exhaustion\".\n\n---\n\n## Verification Checklist\n\n- [ ] All social thread gimmicks (emojis, \"read on\", \"bookmark this\") are completely eradicated.\n- [ ] Fractured 1-line sentences are consolidated into rich, coherent paragraphs.\n- [ ] Technical code snippets, architecture diagrams, and citations are added.\n- [ ] Narrative flow incorporates clear transitional bridges between sections.\n- [ ] Article includes optimized SEO metadata (Title, Slug, Meta Description).\n\n---\n\n## Anti-Patterns\n\n- **The Lazy Stitch**: Pasting 10 tweets separated by horizontal rules and calling it a blog post.\n- **Keeping Clickbait Intros**: Starting an article with \"Most engineers do this wrong. Here are 7 secrets...\"\n- **Omitting Technical Proof**: Keeping the high-level social claims without adding the underlying code or benchmark evidence.\n",{"name":5,"group":24,"description":7,"last_reviewed":25},"Repurposing and translation",1788652800000,"main","036f70c9d6ddd7a7e8b6691aa3ae0279b0649433","skills\u002Fthread-to-article",2,"https:\u002F\u002Fgithub.com\u002Fpoorvith-mp\u002Fskills-writing","https:\u002F\u002Fgithub.com\u002Fpoorvith-mp\u002Fskillary","https:\u002F\u002Fgithub.com\u002Fpoorvith-mp","poorvithmp.com","Shipping tools for problems people notice too late.","2026-10-02 21:32:55",{"source":8,"skillName":5,"commands":37,"prompt":47,"zipAvailable":48},[38,41,44],{"tool":39,"command":40},"npx","npx skills add poorvith-mp\u002Fskills-writing --skill thread-to-article",{"tool":42,"command":43},"bunx","bunx skills add poorvith-mp\u002Fskills-writing --skill thread-to-article",{"tool":45,"command":46},"pnpm","pnpm dlx skills add poorvith-mp\u002Fskills-writing --skill thread-to-article","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fpoorvith-mp\u002Fskills-writing\u002Fblob\u002Fmain\u002Fskills\u002Fthread-to-article\u002FSKILL.md",true,[50,56],{"path":51,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":54,"sourceHtmlUrl":55},"evals\u002Frouting.yaml","REFERENCE","参考文档",1005,"https:\u002F\u002Fgithub.com\u002Fpoorvith-mp\u002Fskills-writing\u002Fblob\u002Fmain\u002Fskills\u002Fthread-to-article\u002Fevals\u002Frouting.yaml",{"path":57,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":60,"sourceHtmlUrl":61},"thread-to-article.skill","OTHER","其他",3344,"https:\u002F\u002Fgithub.com\u002Fpoorvith-mp\u002Fskills-writing\u002Fblob\u002Fmain\u002Fskills\u002Fthread-to-article\u002Fthread-to-article.skill",[63,69,76,83,90,97],{"skillNo":64,"name":65,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M79309BVEDZ4AB80FM7N45XV","writing-taste","https:\u002F\u002Fgithub.com\u002Fpoorvith-mp\u002Fskills-writing\u002Fblob\u002Fmain\u002Fskills\u002Fwriting-taste\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M79303W7E8AD1M3EC1T9TXEE","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.","https:\u002F\u002Fgithub.com\u002Fpoorvith-mp\u002Fskills-writing\u002Fblob\u002Fmain\u002Fskills\u002Ftranslation\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M79300EK34V2MZRPVMV3PP41","thread-to-blog-converter","Moved to modernized catalog in skillary. Removed in v4.1.","https:\u002F\u002Fgithub.com\u002Fpoorvith-mp\u002Fskills-writing\u002Fblob\u002Fmain\u002Fskills\u002Fthread-to-blog-converter\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M792ZRYX1PPQ737CGQB28T1E","technical-writer","Moved to technical-docs in skills-writing. Removed in v4.1.","https:\u002F\u002Fgithub.com\u002Fpoorvith-mp\u002Fskills-writing\u002Fblob\u002Fmain\u002Fskills\u002Ftechnical-writer\u002FSKILL.md",[],[],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":19},"01M792ZMCF8S5GJMNKJ984ARDF","technical-docs","Write API references, user guides, setup manuals and architecture docs with consistent terminology. Use when writing developer documentation, API guides, or tutorials.","https:\u002F\u002Fgithub.com\u002Fpoorvith-mp\u002Fskills-writing\u002Fblob\u002Fmain\u002Fskills\u002Ftechnical-docs\u002FSKILL.md",[],[],{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":19},"01M792ZG14PGB50E2P8VGQ8RC3","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.","https:\u002F\u002Fgithub.com\u002Fpoorvith-mp\u002Fskills-writing\u002Fblob\u002Fmain\u002Fskills\u002Ftalk-writing\u002FSKILL.md",[],[]]