agentleFS
Sign inStart free
moses607moses607/socialforge/skills/cross-platform-adapter/SKILL.md

cross-platform-adapter

Skill3 starsChanged 4 months agoMITView on GitHub

Adapts ONE core idea into each platform's native format instead of cross-posting the same clip everywhere. It maps length, aspect ratio, tone, hook style, caption and hashtag norms, and what actually converts per platform, then outputs a per-platform adaptation table. Use when the user says "repurpose this," "cross-post," "adapt this for LinkedIn/TikTok," or plans a multi-platform push. Works with any capable model.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Write 3 hook angles: contrarian, result-first, and question.

    line 13
  2. Distinctive:

    Never post the same caption and hashtags across two platforms.

    line 48
  3. Distinctive:

    If an idea has no native fit for a platform, skip that platform — do not force it.

    line 53

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Cross-Platform Adapter

Identical cross-posting loses on every platform because each ranks and rewards different behavior. The winning move is "same idea, native execution": lock ONE core insight (the thing worth saying) and re-package everything around it — length, framing, tone, hook, and caption — to the norms of each surface. Keep the insight and the proof; change the container. A repurpose is a translation, not a copy-paste.

1. Extract the transferable core

  1. State the ONE insight in a single sentence a stranger could repeat.
  2. Identify the proof (demo, number, before/after, story beat) — this travels unchanged.
  3. Write 3 hook angles: contrarian, result-first, and question. You will assign different angles to different platforms.

2. Adapt by platform norms

  1. YouTube long: 6-12 min, teach-then-payoff, 16:9. Hook in first 15s naming the payoff; retention lives on chapters and open loops. Convert via watch-time + a clear CTA card.
  2. YouTube Shorts / TikTok: 15-45s, 9:16, fast verbal hook (0-2s), on-screen captions always. TikTok rewards native/lo-fi + trending audio; add a loop or "wait for it." Convert via completion + shares.
  3. Instagram Reels: 7-30s, 9:16, high-polish, strong first frame + cover text. Carousels (1080x1350) win for how-to; slide 1 is the hook, last slide is the CTA. Convert via saves + shares.
  4. X: text-first, 1-3 sentences, punchy claim; thread only if the proof needs steps. Native video 1:1 or 9:16, no external links in the main post. Convert via replies + reposts.
  5. LinkedIn: 150-300 word text post, line breaks every 1-2 sentences, professional but personal; lead with a result or lesson. Convert via comments; ask one question at the end.
  6. Threads: conversational, lowercase-casual, 1-2 sentences, reply-bait. Convert via replies; no hashtag stuffing.

3. Tune hashtags, captions, and CTA

  1. Hashtags: TikTok 3-5 niche, IG 3-8 mixed reach, LinkedIn 3 topical, X 0-2, YouTube in description not title, Threads 1.
  2. Caption first line is a second hook — never waste it on "check out my new video."
  3. One CTA per post, matched to the platform's convert metric (save/share/comment/watch).

Output template

CORE IDEA: <one sentence>
PROOF: <demo/number/story>

| Platform        | Length/Format | Aspect | Hook angle        | Caption first line        | Hashtags        | Convert lever   |
|-----------------|---------------|--------|-------------------|---------------------------|-----------------|-----------------|
| YouTube long    | 6-12 min      | 16:9   | Result-first      | <line>                    | in description  | Watch-time + CTA|
| Shorts/TikTok   | 15-45s        | 9:16   | Contrarian        | <line>                    | 3-5 niche       | Completion+share|
| IG Reel         | 7-30s         | 9:16   | Question          | <line>                    | 3-8 mixed       | Saves + shares  |
| IG Carousel     | 6-10 slides   | 4:5    | Result-first      | slide 1 text              | 3-8 mixed       | Saves           |
| X               | 1-3 sentences | 1:1    | Contrarian        | <claim>                   | 0-2             | Replies+reposts |
| LinkedIn        | 150-300 words | 4:5    | Lesson/story      | <line>                    | 3 topical       | Comments        |
| Threads         | 1-2 sentences | 9:16   | Question          | <line>                    | 1               | Replies         |

Platform variants

Vertical-native (TikTok/Reels/Shorts/Threads) share 9:16 assets but differ in polish: TikTok lo-fi, Reels polished, Shorts payoff-driven. Horizontal (YouTube long) needs its own edit, never a stretched vertical. Text-native (X/LinkedIn) may not need video at all — the insight as words can outperform.

Rules

  • Never post the same caption and hashtags across two platforms.
  • Reshoot or re-crop the hook per platform; the first 2 seconds are platform-specific.
  • One idea per repurpose batch — do not merge three insights to "save effort."
  • Match aspect ratio natively; letterboxed or watermarked (TikTok logo on Reels) reposts get suppressed.
  • Pick each platform's convert metric first, then write to it.
  • If an idea has no native fit for a platform, skip that platform — do not force it.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free