Token导航 LogoToken导航TokenDH.com
研究检索需要联网github未标认证来源可访问许可证需确认审计提醒

synthesis-content-distribution合成内容分布

Agent Skill

用于辅助文档、README、Markdown、说明文和内容稿件的整理与改写。它适合让 Agent 提炼结构、补齐章节、统一术语、检查链接或把零散材料整理成可读文档。使用时应保留项目已有事实、命令和路径,不要把未确认的信息写成确定结论;涉及对外文案时,还需要控制语气,避免过度营销或夸大能力。

总安装

259

周安装

11

GitHub Stars

3

下载量

91
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:synthesis-content-distribution(合成内容分布)
来源仓库:https://github.com/rajivpant/synthesis-skills
仓库路径:skills/synthesis-content-distribution
安装命令:
npx skills add https://github.com/rajivpant/synthesis-skills --skill synthesis-content-distribution
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/rajivpant/synthesis-skills --skill synthesis-content-distribution

简介

synthesis-content-distribution 用于辅助文档、README 和内容稿件的整理与改写,适合结构化和术语统一。

  • 适用于 Codex、Claude、Cursor、Gemini CLI 中的内容组织与文案优化场景。
  • 通过 npx skills add 命令从指定 GitHub 仓库安装并使用该技能。
  • 使用时应保留项目事实,避免过度营销或夸大能力,尤其对外文案需控制语气。
  • 适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

SKILL.md

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

Apply voice and style preferences from your CLAUDE.md if present. Otherwise, customize the section below.

Professional Positioning Describe your professional background, areas of expertise, and how you want to be perceived. This helps produce posts that carry the right authority.

Areas to cover:

  • Domain expertise and experience level
  • Current focus or role
  • How you are known professionally
  • What distinguishes your perspective

Authentic Voice Characteristics Define communication style. Examples:

  • Direct and substantive without being academic
  • Confident from experience, not self-promotion
  • Intellectually curious and willing to challenge conventional wisdom
  • Values precision in language and thought
  • Demonstrates expertise through insight, not credentials

What Feels Inauthentic Words and patterns to avoid. Common examples:

  • "honored," "humbled," "excited," "thrilled," "privileged"
  • Obvious statements or business platitudes
  • Marketing copy or promotional language
  • Excessive adjectives or superlatives
  • Humble bragging or credential listing

Strategic Subtlety Define how expertise should be demonstrated: through credentials, analysis quality, storytelling, or other means.

Platform-Specific Guidelines

LinkedIn

Purpose: Thought leadership, professional relationships, advisory/board positioning.

Format: 300-600 words with natural paragraph breaks.

Structure:

  • Open with an observation or question that creates immediate relevance
  • Develop one core insight with supporting context
  • Connect to broader industry implications
  • End with an invitation to engage (question, alternative perspective, call to discussion)
  • URL placement should feel natural, not promotional

Do: Connect technical insights to business outcomes. Share lessons from real experience. Provide frameworks or mental models. Challenge conventional wisdom thoughtfully.

Avoid: Resume recitation. Promotional language. Asking for likes/shares. More than two hashtags.

Tagging: Only tag people genuinely relevant to the discussion. Tag at end, not in main text.

Twitter/X

Purpose: Industry conversations, quick insights, peer relationships.

Format: Thread of 2-5 tweets (280 characters each).

Structure:

  • First tweet is the hook
  • Each subsequent tweet develops one idea
  • Final tweet includes URL and optional discussion invitation
  • Each tweet should work standalone (people quote-tweet individual thoughts)

Do: Counterintuitive observations. Specific examples or data points. Questions that spark debate. Timely reactions to industry news.

Avoid: Thread announcements ("Thread: 1/5"). Engagement farming. Excessive emoji. Multiple hashtags. "Like and retweet if you agree."

Hacker News

Purpose: Share technical insights with startup/tech community.

Format: Title and optional comment.

Tone: Technical and substantive. This audience values depth and dislikes promotion.

Do: Use factual, specific titles (not clickbait). Add technical context if commenting on own submission. Be transparent about authorship. Engage substantively with comments.

Avoid: Any promotional language. Business/marketing angles. Defensive responses. Talking about metrics.

Reddit

Purpose: Engage specific communities, get substantive feedback.

Strategy:

  • Identify 1-2 highly relevant subreddits (quality over quantity)
  • Review recent posts to understand community norms
  • Title should match subreddit style
  • Include context explaining relevance to the community
  • Be transparent about authorship
  • Engage meaningfully with comments

Avoid: Cross-posting to many subreddits. Generic promotional language. Ignoring community rules. Arguing with skeptics. Deleting underperforming posts.

BlueSky

Purpose: Build presence with early adopter community.

Format: Similar to Twitter (300 character limit). Slightly more informal.

Strategy: Good for testing ideas before wider distribution. Engage with others' content. Use as complement to Twitter.

Other Platforms

  • Threads: Similar to Twitter/X approach; broader, less technical audience
  • Instagram: Only if content has strong visual component; carousel posts for text-heavy content
  • Facebook: Personal network, use sparingly; share to specific groups if highly relevant

Content Creation Process

Step 1: Strategic Brief

Present analysis: what makes this content valuable, platform recommendations with rationale, suggested emphasis per platform, timing/sequencing, risks or sensitivities. Wait for feedback.

Step 2: Content Creation

For each approved platform, provide:

  • Platform name
  • Strategic Approach: One paragraph explaining strategy
  • Post Content: Actual text, formatted for the platform
  • Engagement Hook: What will spark discussion
  • Success Indicators: What good engagement looks like
  • Follow-up Strategy: How to engage with responses

Step 3: Cross-Platform Coordination

Posting Sequence: Which platform first and why. Spacing between platforms. Timing considerations.

Cross-Pollination: When to reference discussion from one platform on another. How to synthesize feedback. Opportunities for follow-up content.

Engagement Management

Responding to Comments

Prioritize: Thoughtful questions that advance discussion. Constructive disagreement. Comments from people worth building relationships with. Questions that add context.

Strategy: Add value in every response (not just "thanks"). Use questions to deepen discussion. Acknowledge good points from dissenters. Share additional resources when relevant.

Avoid: Defensive responses. Arguing with trolls. Over-responding. Generic "thanks for reading."

Watch For

  • Emerging themes suggesting follow-up content
  • Connections to people with aligned interests
  • Misconceptions needing clarification in future writing
  • Questions revealing audience needs

Success Metrics

Quantitative: Engagement rate (not just volume). Quality of commenters. Inbound connections or opportunities. Click-through rate. Secondary sharing by influential accounts.

Qualitative: Depth of discussion. New relationships formed. Ideas or opportunities that emerge. Position in relevant conversations.

Red Flags: High engagement with low substance. Negative discussion without understanding. Engagement from outside target audience. Backlash from poor framing.

Failure Modes and Recovery

Low traction: Evaluate timing and framing. Look at who did engage. Mine comments for positioning insights. Do not over-analyze.

Negative discussion: Do not respond defensively. Acknowledge valid criticisms. Clarify misunderstandings once, then move on. Take heated discussion private.

Missed the mark: Acknowledge openly if wrong. Use as learning opportunity. Do not over-apologize. Improve framing next time.

Continuous Improvement

After each campaign: Which platforms drove best engagement? What framing worked? What relationships emerged? What follow-up content does this suggest?

Pattern Recognition: Which topics consistently resonate? Which platforms work for which content types? How is the network evolving? What themes emerge in discussions?

Special Situations

  • Time-Sensitive Content: Prioritize fast-engagement platforms (Twitter, HN). Post at optimal times. Be ready for active engagement in first hours.
  • Controversial Topics: Anticipate objections in framing. Be precise with tone. Consider which platforms handle nuance well.
  • Technical Deep Dives: Prioritize technical audiences (HN, specific subreddits). Expect slower but higher-quality engagement.
  • Strategic/Business Content: LinkedIn becomes primary. Frame in terms of decisions and tradeoffs.

Quick Start: Blog Article Promotion

When asked to promote a blog post or article, follow this condensed workflow:

  1. Read the article at the provided URL. Identify the single most compelling insight.
  2. Note the URL to include in posts.
  3. Write posts for three platforms:

Twitter/X (thread of 2-4 tweets):

  • First tweet: the hook — a counterintuitive observation or specific insight from the article
  • Middle tweets: develop one idea each, each tweet works standalone
  • Final tweet: URL + optional discussion question
  • No thread announcements, no engagement farming, no excessive emoji or hashtags

Instagram (caption for image/carousel post):

  • Lead with a strong opening line that stops the scroll
  • Share the key insight in accessible language
  • End with a call to discussion or reflection
  • 3-5 relevant hashtags maximum

LinkedIn (300-600 words):

  • Open with an observation or question that creates relevance
  • Develop the core insight with supporting context
  • Connect to broader implications
  • End with a discussion invitation
  • Place URL naturally, not promotionally

How to write: Direct, substantive, confident from experience. Demonstrate expertise through insight, not credentials. Challenge conventional wisdom where warranted.

How NOT to write: No "honored/humbled/excited/thrilled." No business platitudes. No promotional language. No humble bragging or credential listing. No "like and retweet."

Quick Start: Event or Topic Post

When asked to write social media posts about an event, experience, location, or topic, follow this workflow:

  1. Gather information (ask if not provided):

- What is the event, experience, or topic? - Where and when? (location, date, context) - What is the key insight, tip, or takeaway to share? - Who is the audience? (professional peers, general public, niche community) - Any photos or visual elements to reference? - Any people or organizations to mention or tag?

  1. Write posts for three platforms:

Twitter/X (1-3 tweets):

  • Lead with the most interesting or useful observation
  • Include specific details (names, places, concrete tips) rather than generalities
  • Tag relevant accounts sparingly and only when genuinely relevant

Instagram (caption):

  • Open with a vivid or specific detail that sets the scene
  • Share what made this notable or what you learned
  • Keep it conversational and authentic
  • 3-5 relevant hashtags

LinkedIn (200-400 words):

  • Frame around a professional insight or lesson drawn from the experience
  • Connect the specific event to a broader theme your audience cares about
  • Include practical takeaway or reflection
  • Tag people or organizations only if genuinely relevant to the post

Tone across all platforms: Authentic, specific, grounded in real experience. Avoid generic "what an amazing event" language. Share what you actually observed, learned, or found useful.

Related

Part of the synthesis writing craft — the writer writes, the AI assists.

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

33.21%
按下载量换算30

Claude

28.23%
按下载量换算26

Cursor

19.85%
按下载量换算18

Gemini CLI

9.03%
按下载量换算8

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

可疑

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在 warning/failed 结果,不能写成本站确认安全。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills