SuperAPI AI Directory
Partner with us中文AI newsFavorites
Skillsgr-social-distill

gr-social-distill

General & other

View repository

Updated 10-16 05:48

About this skill

⚠️ Channel adjustments for 2C products

This skill defaults to dev / B2B channels.2C consumer goods / education / apps: the main battlefield for customer acquisition is vertical communities + short videos + vertical KOLs, choose the first platform based on regional public data (e.g., short video in Indonesia/Thailand has already overtaken Facebook). For KOLs, prioritize nano / micro verticals—the more followers, the lower the engagement rate, and micro > mega is more cost-effective. For the complete 2C channel database + public sources see → gingiris-seo-geo/references/2c-adaptation.md。

gr-social-distill — Blog to social media repurposing

Core concept

Repurposing > creating from scratch. If you've published 60 blog posts but only used social media once, the highest-ROI next step isn't writing new articles, it's breaking them into variants (source: Atomic Library 2026Q2_016).

One 2000-3500 word blog post → 4 social media formats → 4x traffic amplification, and you don't need new content inspiration.

When to use

Scenario Action
"Break this blog post into an X thread" X template (see below)
"Make a Xiaohongshu version" Xiaohongshu template (75 title formulas)
"How should I post on LinkedIn" LinkedIn carousel template (B2B content only)
"dev.to / Zenn repost" Technical blog cross-platform template
"Weekly distribution cadence" Full workflow (1 blog post → 4 variants)

Input

  • 1 published blog URL or _posts/ filename
  • Optional: target channel (X / xhs / LinkedIn / dev.to / Zenn / all)

Output

Produce corresponding markdown or draft text by channel, ready to post directly.

4 channel templates

1️⃣ X thread (10-15 tweets)

Structure：

[推 1 — HOOK] 一个反常识 / 数据 / 问题引入（≤ 280 字，是否有吸引力决定全盘）
[推 2 — STAKES] 我 X 个月踩过 Y 个坑，结论是...
[推 3-12 — BODY] 每推一个要点。每推 ≤ 280 字。用短句。
[推 13 — TL;DR] 回到 HOOK 的答案
[推 14 — LINK] 链接到原博客 + 1 句 why it's worth clicking
[推 15 — CTA] @WeiYipei if you want the template

Principles：

  • Each tweet stands on its own; a screenshot of it alone can still be retweeted
  • Use specific numbers instead of adjectives ("within 30 days" vs "soon")
  • Insert 1 screenshot / table every 3-4 tweets
  • Hook sentence patterns for reference:
    • "Here's what 60 blog posts taught me about X:"
    • "I analyzed 27 X tools. 22 of them aren't worth $0."
    • "Stop doing X. I tried it for 90 days. Data:"

For a detailed example library see templates/x-thread.md。

2️⃣ Xiaohongshu note (3-5 images)

Title formulas(75 viral formulas, copied from dbs-xhs-title):

  • Number type: "I tested 27 XX tools, only 4 are actually free and useful"
  • Pitfall type: "Stop using XX, lessons I paid 30,000 yuan to learn"
  • Tutorial type: "Step-by-step guide to get XX done in 5 steps (with tool list)"
  • Contrast type: "Used XX for 3 years, then found out Y is the real gem"
  • Reveal type: "3 things people who do XX won't tell you"

Content structure(each post < 1000 words):

  • First 100 words: hook + pain point resonance
  • Main body 600 words: 3-5 key points, each 100-200 words
  • Last 100 words: TL;DR + engagement question
  • Add 5-8 related tags:#出海创业 #SaaS增长 #独立开发者 ...

Images(3-5 images):

  • Figure 1: Title image (large headline + key numbers)
  • Figures 2-4: 1 point each (use phone screenshot + red box around keywords)
  • Figure 5 (optional): Data table / comparison chart

See detailed template at templates/xhs-note.md。

3️⃣ LinkedIn carousel (B2B / technical posts only)

Trigger conditions: Only post to LinkedIn if the original blog is B2B / enterprise / developer-oriented content; skip ToC content.

10-page carousel structure：

  • Page 1: Title ("How we [result] in [time]", with a key visual)
  • Page 2: Problem definition (why the reader should care)
  • Pages 3-8: 6 steps / points, 1 per page
  • Page 9: Data results (before/after comparison)
  • Page 10: CTA (follow + link to the original blog)

Content per page：

  • Large headline (≤ 40 characters)
  • 3-5 bullets (≤ 10 characters each)
  • Images / icons / charts

Body text (caption 500-1000 characters)：

  • First 3 lines grab attention (LinkedIn shows the collapsed view)
  • Body talks about "what I learned" (not "what features the tool has")
  • End with a question to drive comments

See detailed template at templates/linkedin-carousel.md。

4️⃣ dev.to / Zenn cross-post

Applicable: The original blog is technical (SEO / GEO / API / code / tools)

Key rules(learned from the 2026-04-20 dev.to ranking drop incident):

  • ⚠️ canonical_url must point to dev.to itself, not to gingiris.tools
    • Wrong approach:canonical_url: https://gingiris.tools/...
    • Correct approach:canonical_url: https://dev.to/iris1031/... or leave it blank
    • Reason: canonical points to the main site → Google treats the dev.to version as a duplicate → it doesn't participate in independent SERP
  • Publish time gap ≥ 7 days(don't publish on the same day, to avoid Google considering it a copy)
  • Localize the content: Change the opening hook, add 1-2 paragraphs of commentary from a dev.to user's perspective
  • Add at the end "Originally I wrote this for my blog at gingiris.tools"(build a two-way reference, but don't use canonical)

Zenn special case：

  • frontmatter type: tech technical post / type: idea opinion post
  • Prioritize the Japanese version, use Japanese-style sentence patterns in titles such as "〜してみた" / "〜の作り方"
  • Choose cuter emojis for the emoji system (📝 / 🚀 / 💡)

See detailed template at templates/devto-zenn.md。

Weekly workflow (the rhythm of Phase 2 mainline 2)

每周一 10:00
    ↓
从 gr-seo-patrol 输出里挑：
- Organic Search 流量 top 3
- 或：最近 30 天新发且排名 top 30 的
    ↓
选 1 篇"高潜力博客"作为本周分发源
    ↓
产出 4 变体（X / xhs / LinkedIn / dev.to）
    ↓
分散发布：
- 周一：X thread
- 周三：小红书笔记
- 周五：LinkedIn carousel（如 B2B）
- 次周周一：dev.to / Zenn 二发（延迟 7 天）
    ↓
下周一：复盘
- 哪个渠道带回了多少 GA4 referral？
- 哪个变体互动率最高？
- 更新 MEMORY 里的分发 playbook

Track effectiveness

Record UTM for each variant after publishing:

?utm_source=x|xhs|linkedin|devto&utm_medium=social&utm_campaign=distill_{post-slug}

In the GA4 Referral report, group by utm_source to determine the ROI of each channel.

Cascading recommendations

  • 24h after all variants are published → gr-seo-patrol check whether the Organic Social share has increased
  • If a channel's ROI is found to be especially high → double down next week (publish 2 more posts on the same channel)
  • Xiaohongshu viral hit → increase collaboration with UGC creators (linked with gr-aso UGC creator matrix strategy)
  • dev.to ranking rises → confirm the canonical configuration to avoid repeating the mistake

Anti-patterns

  • ❌ Publishing on 4 channels on the same day — your own readers will be annoyed to see the same content repeatedly
  • ❌ Copy-pasting the original text —— X / xhs / LinkedIn each channel has its own context; copying directly results in a 10x difference in engagement rate
  • ❌ dev.to canonical points to the main site —— 2026-04-20 hard-learned lesson, always self-canonical
  • ❌ Posting ToC content on LinkedIn —— severe mismatch with the platform audience
  • ❌ Adding external links on Xiaohongshu(severe platform demotion —— change the URL to "find the link in the bio")
  • ❌ Drafting 10 posts at once, piling up in drafts without publishing —— better 1 fully distributed post > 10 half-finished ones