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 transfo...
Scanned 9/1/2026
Install to Claude Code
npx -y skills add Ootto-AI/claude-content-skills --skill cross-platform-distribution --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Cross Platform Distribution?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/ootto-ai-cross-platform-distribution)More formats (shields.io, HTML) on the badges page.
---
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.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!