Multi-Channel Campaign Adapter

Cross platform distribution

by Ootto-AI · MIT license · ★ 139 on GitHub

Cross platform distribution cover

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…

---
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

Overview

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

Manual install (npx, ZIP)
Claude Codenpx skills add Ootto-AI/claude-content-skills --skill cross-platform-distribution -g -a claude-code
Claude Code (degit)npx degit Ootto-AI/claude-content-skills/skills/cross-platform-distribution#main ~/.claude/skills/cross-platform-distribution
Claude.ai / desktopZip the folder and upload it under Settings → Capabilities → Skills.
Codex, Cursor, other agentsPoint them at SKILL.md. The other files are plain text.

Connects with Agent Alley MCP · agentalley.io/mcp

Files included

  • SKILL.md3.2 KB
Read SKILL.md here
Ootto-AI/main1 file shown
SKILL.md
Show the full text46 lines

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.

1---
2name: cross-platform-distribution
3description: 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.
4---
5 
6# Cross-Platform Distribution
7 
8Give one approved message different jobs across channels so distribution increases useful reach without turning into noisy duplication.
9 
10## 1. Start with a locked source
11 
12Ask 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.
13 
14## 2. Assign channel roles
15 
16For 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.
17 
18## 3. Adapt the mechanism, not the truth
19 
20Translate 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.
21 
22## 4. Sequence and measure
23 
24Order 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.
25 
26## Hard rules
27 
28- Never paste the same post across platforms without adapting the format and context.
29- Do not add channels merely because they are popular or have a large theoretical audience.
30- Preserve every approved claim boundary and disclosure requirement.
31- Do not use UTM links where the destination or tracking convention has not been approved; use utm-campaign-plan first.
32- Keep paid, owned, creator, and community activity labelled separately.
33 
34## Failure modes
35 
36| Failure | Do this instead |
37| --- | --- |
38| One asset becomes five duplicate posts | Give each channel a distinct audience job and angle. |
39| Format is chosen before audience context | Start with the role, then choose the smallest suitable format. |
40| A weak post is endlessly republished | Set a review point and change the message or stop based on evidence. |
41| Links cannot be attributed | Create an approved UTM plan before publishing trackable links. |
42 
43## Where it sits
44 
45Use 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.
46 
View all files on GitHub →

Details

License
MIT
Stars on the repo
★ 139
Checked
Source
Ootto-AI/claude-content-skills ↗
Creator
Ootto-AI · 36 listings
View creator

Similar skills

See all →
SkillLinkedIn Post Adaptersergebulaev/linkedin-skills · by sergebulaevRepurpose existing content into a native LinkedIn post. Take a tweet, thread, YouTube video, blog, or newsletter and rebuild it for LinkedIn: re-hook before the fold, expand to the 900 to 1300 char sweet spot, add whitespace and a CTA, move links to the first comment, run the humanizer, publish via Publora on approval. Not for writing from scratch (use linkedin-post-writer), not for auditing a draft (use linkedin-humanizer --mode audit).★ 3.1k GitHub starsSkillSocial Content RepurposerScrapeCreators/social-media-research-skills · by ScrapeCreatorsUse when the user wants to turn public social videos, transcripts, posts, or creator research into reusable content assets such as LinkedIn posts, X threads, short-form scripts, newsletters, blog outlines, carousels, or content calendars.★ 2.6k GitHub starsSkillMulti-Platform RepurposerOpenClaudia/openclaudia-skills · by OpenClaudiaRepurpose and atomize content across platforms and formats. Use when the user says "repurpose this", "turn this into", "convert blog to", "make a thread from", "content atomization", "repurpose content", "turn this article into social posts", or asks about adapting content from one format to another.★ 705 GitHub starsSkillVideo Clip Generatorpawbytes/skill-suites · by pawbytesVideo repurposing pipeline for multi-platform clip extraction. Use when the user requests to 'extract clips', 'repurpose video', 'create clips from video', or 'clip video for social'.★ 114 GitHub starsSkillMulti-Channel DistributorLeadMagic/gtm-skills · by LeadMagicDistribute content across channels for maximum reach — multi-platform repurposing, syndication, paid amplification, email distribution, and partner promotion. Use when getting content in front of an audience, repurposing content, or building a distribution engine. Triggers on: "content distribution", "promote content", "repurpose content", "syndication", "amplify content", "get more eyes on", or any content amplification request.★ 62 GitHub starsSkillFacebook Content Repurposersergebulaev/facebook-skills · by sergebulaevRepurpose existing content into a native Facebook Page post. Take a LinkedIn post, X thread, blog, or newsletter and rewrite it for a Page: warm the tone, lead with a standalone claim before the "See more" fold, move links to the first comment, strip off-platform artifacts (hashtag walls, "link in bio", @-handles), then humanize and publish via Publora on approval. Not for writing from scratch (use fb-post-writer), auditing a draft (use fb-humanizer), or comment replies (use fb-engagement-drafter).★ 49 GitHub stars

More from Ootto-AI

SkillHook Variant A/B GeneratorOotto-AI/claude-content-skills · by Ootto-AIGenerates two genuinely distinct hook variants for the same reel so you can post-test which opening actually wins. Use when the user says "give me two hooks to test", "A/B this hook", "which opening should I use", "hook variants".★ 139 GitHub starsSkillInternet Research RouterOotto-AI/claude-content-skills · by Ootto-AIMUST USE when user wants to 调研/research/搜索/search/查/找/look up anything on the internet — e.g. 全网调研 X / 帮我调研一下 X / 查一下 X / 搜搜 X / 看看大家怎么评价 X / X 上有什么讨论 / research this topic。 Also MUST USE when user mentions any platform or shares any URL/链接: 小红书/xiaohongshu/xhs, Twitter/推特/X, B站/bilibili, Reddit, V2EX, LinkedIn/领英/招聘/求职/jobs, YouTube, GitHub code search, 小宇宙播客, 雪球/股票行情, RSS feeds, or any web URL. 13 platforms, multi-backend routing (OpenCLI / per-platform CLIs / APIs). Zero config for 6 channels. Run `agent-reach doctor --json` to see which backend serves each platform right now. NOT for: 写报告/数据分析/翻译等内容加工(本 skill 只负责从互联网获取内容); 发帖/评论/点赞等写操作;已有专门 skill 的平台(先用专门 skill)。 【路由方式】SKILL.md 包含路由表和常用命令,复杂场景需按需阅读对应分类的 references/*.md。 分类:search / social (小红书/推特/B站/V2EX/Reddit) / career(LinkedIn) / dev(github) / web(网页/文章/RSS) / video(YouTube/B站/播客)。★ 139 GitHub starsSkillObsidian Long-Term MemoryOotto-AI/claude-content-skills · by Ootto-AIGive Claude a permanent, searchable long-term memory using an Obsidian vault as the store. At the end of a session, summarize what mattered and save it as a Markdown note in your "AI Brain" vault; at the start of a session (or on demand), read back only the relevant past notes. Local markdown you own — connected via the Filesystem MCP. Trigger with "wrap up", "save this session", or "remember this".★ 139 GitHub starsSkillAnalytics Readout TranslatorOotto-AI/claude-content-skills · by Ootto-AIReads your reel insights and explains in plain English what to make more of and what to stop — no jargon. Use when the user says "explain my analytics", "what do my numbers mean", "read my insights", "how did this reel do".★ 139 GitHub starsSkillSocial Audience PersonasOotto-AI/claude-content-skills · by Ootto-AIBuild evidence-led social audience personas from customer interviews, comments, reviews, or CRM notes.★ 139 GitHub starsSkillSocial Profile ConverterOotto-AI/claude-content-skills · by Ootto-AIRewrites your bio, name field and pinned-reel order to convert profile visits into follows and clicks. Use when the user says "rewrite my bio", "optimize my profile", "what should my bio say", "which reels should I pin".★ 139 GitHub stars