Skip to content
Content
Skill

/cross-platform-distribution

Use when an approved campaign, launch, research finding, or asset needs a deliberate plan across several social channels. Trigger phrases include "adapt this for LinkedIn and X", "where should this campaign go?", "make a distribution plan", "repurpose this without duplicating

From plugin
claude-content-skills
34154 skills

Claude Code

$ npx -y skills add Ootto-AI/claude-content-skills --skill cross-platform-distribution --agent claude-code

SKILL.md

cross-platform-distribution.SKILL.md
name: cross-platform-distribution
description: Use when an approved campaign, launch, research finding, or asset needs a deliberate plan across several social channels. Trigger phrases include "adapt this for LinkedIn and X", "where should this campaign go?", "make a distribution plan", "repurpose this without duplicating it", and "what is each platform's role?". Do not use this to invent a campaign strategy, bulk-post identical copy, or schedule a calendar; use campaign-brief for the strategic source, content-repurposer for asset transformations, and content-calendar for dates.

Cross-Platform Distribution

Give one approved message different jobs across channels so distribution increases useful reach without turning into noisy duplication.

1. Start with a locked source

Ask for the approved campaign brief or source asset, its audience, claim boundary, action, timing, and available formats. If the message is not approved, stop and route to campaign-brief or positioning-audit. Do not turn an untested idea into a distribution plan.

2. Assign channel roles

For every proposed channel, state the audience context, what that channel should contribute, the format it can support, and the action it should earn. A channel may educate, create discussion, provide proof, reach partners, or send qualified traffic. Exclude channels with no clear role rather than filling a grid.

3. Adapt the mechanism, not the truth

Translate the same approved point into channel-native openings, structure, visual requirements, and conversation prompts. Keep the claim, proof, and action consistent. Note what cannot move across: private examples, unsupported performance claims, or assets with rights limited to another platform.

4. Sequence and measure

Order releases so early posts can inform later ones without waiting for a false certainty. Specify cadence, owner, links or UTMs where applicable, and the measurement that each channel is meant to influence. End with the decision that determines whether to extend, revise, or stop distribution.

Hard rules

  • Never paste the same post across platforms without adapting the format and context.
  • Do not add channels merely because they are popular or have a large theoretical audience.
  • Preserve every approved claim boundary and disclosure requirement.
  • Do not use UTM links where the destination or tracking convention has not been approved; use utm-campaign-plan first.
  • Keep paid, owned, creator, and community activity labelled separately.

Failure modes

| Failure | Do this instead | | --- | --- | | One asset becomes five duplicate posts | Give each channel a distinct audience job and angle. | | Format is chosen before audience context | Start with the role, then choose the smallest suitable format. | | A weak post is endlessly republished | Set a review point and change the message or stop based on evidence. | | Links cannot be attributed | Create an approved UTM plan before publishing trackable links. |

Where it sits

Use campaign-brief before this skill. Use linkedin-thought-leadership and x-thread-strategy for channel-specific execution, content-repurposer for asset changes, and content-calendar for the publishing schedule. Use social-analytics-report and launch-retrospective to assess the plan afterwards.

Read more
@ootto-ai
Ships withclaude-content-skills

Free, copy-paste Claude skills that run your content growth factory — turn ideas (and your Obsidian memory) into scroll-stopping Instagram reels: hooks, scripts, repurposing, captions, and a 2-week posting calendar.

Stars on GitHub

Momentum

stars in total
341
Star history of Ootto-AI/claude-content-skills on GitHub, a chart by star-history.com

Other skills on claude-content-skills.

agent-reach

agent-reach

MUST USE when user wants to 调研/research/搜索/search/查/找/look up anything on the internet — e.g. 全网调研 X / 帮我调研一下 X / 查一下 X / 搜搜 X /…

More skills from other plugins.

prompt-lookup

prompt-lookup

Activates when the user asks about AI prompts, needs prompt templates, wants to search for prompts, or mentions prompts.chat. Use…

@gh-f@gh-fInstall Skill
ppt-master

ppt-master

AI-driven presentation workflow for generating editable PPTX decks and slides, reconstructing page visuals, creating reusable…

@hugohe3@hugohe3Install Skill
morph-ppt

morph-ppt

Use this skill when the user wants a .pptx with smooth cross-slide animation — PowerPoint Morph transitions, Keynote-style…

officecli13d33k
@iofficeai@iofficeaiInstall Skill

Questions about cross-platform-distribution.

Which coding agents can use cross-platform-distribution?
cross-platform-distribution installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.