synthesis-content-distribution
Strategically promote and distribute content across social media platforms to build thought leadership, spark discussion, and create professional connections. Provides platform-specific guidelines, engagement strategies, cross-platform coordination, and quick-start templates for blog promotion and event/topic posts. Use when asked to: promote content, content distribution, social media strategy, share article, social media post, write tweet, LinkedIn post, Instagram post, promote blog, blog promotion, post about event, content marketing, distribute post, promote article, social media promotion.
Rajiv Pant · 已有静态检查记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add synthesisengineering/synthesis-skills --skill synthesis-content-distribution技能说明
name: synthesis-content-distribution description: > Strategically promote and distribute content across social media platforms to build thought leadership, spark discussion, and create professional connections. Provides platform-specific guidelines, engagement strategies, cross-platform coordination, and quick-start templates for blog promotion and event/topic posts. Use when asked to: promote content, content distribution, social media strategy, share article, social media post, write tweet, LinkedIn post, Instagram post, promote blog, blog promotion, post about event, content marketing, distribute post, promote article, social media promotion. license: "CC0-1.0" depends_on: [] metadata: author: "Rajiv Pant" version: "1.2.0" source_repo: "github.com/synthesisengineering/synthesis-skills" source_type: "public"
Content Distribution
Strategically promote content across social media platforms to build genuine thought leadership, spark meaningful discussion, and create valuable professional connections.
Initial Analysis Phase
When given a content URL, produce a strategic brief before writing any posts:
Content Analysis
- Core insight or argument
- Primary value proposition for different audiences
- Natural discussion hooks and controversy points
- Connection to current industry conversations
- Unique angles or perspectives presented
Audience Mapping
- Who benefits most from this content
- What specific problems it solves or questions it answers
- Which professional communities find it most relevant
- Potential objections or counterarguments to anticipate
Platform Strategy Recommendation
- Which platforms are optimal for this content (and why)
- Suggested posting sequence and timing
- Platform-specific angles to emphasize
- Communities or groups to target
- Risks or sensitivities to navigate
Voice and Positioning
- How this content advances thought leadership
- What authority or expertise it demonstrates (implicitly)
- Connections to other work or ongoing themes
- How to frame without sounding promotional
Present this analysis and get feedback before writing posts.
Content Information Template
Gather this information:
- Content URL
- Content Type: Blog post, published article, research/analysis, opinion piece, tutorial/guide, case study, or other
- Primary Goal: Establish expertise, generate discussion, drive qualified traffic, create speaking/advising opportunities, test ideas with peers, build relationships, or other
- Timing Considerations: Current events ties, relevant industry discussions, upcoming events, time-sensitive elements
- Constraints or Sensitivities: Topics to avoid, relationships to navigate, competitive sensitivities
Strategic Context and Voice
Voice and tone for posts come from the user's active voice profile, not from this skill. Apply whatever voice profile is loaded in the current environment — typically a private skill (e.g., <workspace>-private-writing-voice), a CLAUDE.md / AGENTS.md instruction block, or both. This skill is methodology-agnostic about voice; it does not embed sample voice traits, sample forbidden language, or persona text.
Areas the active voice profile should cover for content distribution to work well:
- Professional positioning — domain expertise, current role, what distinguishes the writer's perspective.
- Authentic voice characteristics — direct vs academic, formal vs conversational, contrarian vs consensus-leaning, etc.
- Forbidden language — words and patterns the writer never uses.
- Strategic subtlety — how expertise should surface (through analysis quality, storytelling, evidence) rather than be claimed directly.
If no voice profile is active, ask the user to load one (or to describe their voice in conversation) before generating posts. Defaults applied without user input produce generic posts that read as machine-generated.
Social register vs article register
Articles and social posts have different reader expectations. The same writer's voice should sound different in the two modes — same person, different register.
| Dimension | Article | Social post |
|---|---|---|
| Time investment | Hours to days | One sitting |
| Editing passes | Multiple | One or two |
| Reader expectation | Reference, deep dive | Update, share, react |
| Polish level | High | Medium-low (intentional) |
| Voice register | Considered, can be more formal | Conversational, casual-professional |
| Engagement goal | Click-through, share | Comment, react, repost |
| AI-detectability tolerance | Lower | Much lower |
The expectation gap. Readers expect articles to be edited; they expect social posts to be conversational. Over-polished social posts read as AI-generated and get skipped, even when a human wrote them. A few rough edges (a fragment, a casual word, a slight digression) signal authenticity.
Common AI-cadence failures specific to social posts
These patterns are tolerable in articles and flag immediately in social:
- Article structure imported wholesale. Topic sentences, transitions, "the principle" / "the takeaway" / "first / second / finally" labels read as essay scaffolding in social register.
- Imported spec language uppercase. Formal severity labels (CRITICAL, HIGH, MEDIUM) lifted from technical specs read as press-release register in a conversational post. Translate to conversational equivalents.
- Third-person narration of first-person experience. Using "the site", "the audit", "the fix" instead of "my site", "my audit", "my fix" reads as third-party reporting. First-person throughout for personal-experience posts.
- Long sentences (>25 words) without compression. Essay register. Break them.
- Over-smoothed prose with no rhythmic variation. When every sentence is grammatically tidy and every paragraph the same shape, the post reads as machine-edited.
- Closing the loop instead of inviting response. C