x-linkedin-content-relay
When the user has X (Twitter) content that performed well and wants to relay it to LinkedIn 1-2 weeks later with reframing. Also use when the user mentions "repost to LinkedIn", "LinkedIn version of my tweet", "X to LinkedIn", "delayed repost", "LinkedIn for non-tech audience", or "LinkedIn relay". Also use when the user's ICP is non-tech and X is secondary — LinkedIn is the primary channel and this skill produces the content.
What this skill does
# X → LinkedIn Content Relay Something that goes viral on X takes roughly two weeks to reach the LinkedIn audience. That lag is a feature, not a bug. A well-performing X post can be reframed and relayed to LinkedIn ~14 days later to the same audience that hasn't seen it yet — and LinkedIn's audience prefers a different register of voice than X's. **When invoking**: Ask for the winning X post (or the content the user wants to reuse), the date it was posted, the LinkedIn audience the user is targeting, and whether the target is tech or non-tech. Then produce the LinkedIn version. ## When the relay wins - **Non-tech ICP.** Event marketers, HR, healthcare ops, education, manufacturing, services. These audiences live on LinkedIn. X is a trickle. LinkedIn is where the work gets found. - **Delayed-audience fit.** Your X post went viral with devs, but the real buyers are PMs and ops leaders who live on LinkedIn. Wait two weeks, relay, capture the second wave. - **Authority posts.** Case studies, lessons, numbers. LinkedIn rewards "I learned this" and "here's our number" more than X. ## When NOT to relay - Pure X-native formats: shitposts, memes, crypto-style banter, contrarian one-liners, cold screenshots with no setup. - Posts whose viral value was the reply chain, not the post itself. - Posts under 48 hours old — let X do its full cycle first. ## The reframing rules X and LinkedIn are different rooms. Don't copy-paste. | Axis | X | LinkedIn | |---|---|---| | **Voice** | Punchy, lowercase, ironic OK | Declarative, first-letter caps, earnest | | **Length** | 80-200 chars for engagement | 1,200-2,000 chars for feed dwell | | **Framing** | "Here's a thing" | "Here's what I learned" | | **Proof** | Screenshots, GitHub links | Numbers, outcomes, named companies | | **Opener** | Claim or contrarian hook | Story hook, first-person setup | | **Closer** | Open question or zero close | "What's your take?" or concrete CTA | | **Media** | Video / screenshot native | Native image / carousel PDF | | **External links** | Penalized, put in reply | Same penalty; first comment instead | ## The relay protocol 1. **Find the X winners.** Last 30 days, posts with >5x the account's baseline engagement. 2. **Filter.** Remove pure X-native posts (memes, one-liners). 3. **Extract the underlying insight.** What did the X post actually say, stripped of X-speak? 4. **Rebuild for LinkedIn.** - Lead with a first-person story hook (2-3 lines). - Deliver the insight in prose, not fragments. - Cite numbers or named outcomes wherever possible. - Close with a concrete question pointed at the LinkedIn audience. 5. **Swap the asset.** Screenshots → native image or 4-slide PDF carousel. Video → same video but vertical cut with captions. 6. **Time it.** Post 10-14 days after the X original, ideally Tuesday-Thursday 7-9am or 12-1pm local to the buyer. 7. **External link** goes in the first comment, not the post body. ## Output format When asked to produce a LinkedIn relay, produce: 1. **Source X post** — the original, with its date and performance. 2. **Underlying insight** — 1-2 sentences, stripped of platform voice. 3. **LinkedIn post draft** — 1,200-2,000 chars, formatted for the LinkedIn feed. 4. **Asset recommendation** — what image, carousel, or video format to pair it with. 5. **Timing** — suggested post day/time based on the 14-day lag and the audience. 6. **First comment** — external link, CTA, or continuation. 7. **What NOT to carry over** — 1-2 X elements that would hurt on LinkedIn. ## Related skills - `x-account-warmup` — the upstream step that produced the content being relayed - `x-launch-video-structure` — if the source is a launch video, not a post - `social-content-creation` — broader cross-platform repurposing (different use case — that skill covers newsletters/podcasts → social, this covers X → LinkedIn specifically) - `linkedin-posts` (marketing-skills platforms/linkedin) — LinkedIn formatting fundamentals
Related in Writing & Docs
jax-development
IncludedUse this skill when the user is writing, debugging, profiling, refactoring, reviewing, benchmarking, parallelising, exporting, or explaining JAX code, or when they mention JAX, jax.numpy, jit, grad, value_and_grad, vmap, scan, lax, random keys, pytrees, jax.Array, sharding, Mesh, PartitionSpec, NamedSharding, pmap, shard_map, Pallas, XLA, StableHLO, checkify, profiler, or the JAX repo. It helps turn NumPy or PyTorch-style code into pure functional JAX, fix tracer/control-flow/shape/PRNG bugs, remove recompiles and host-device syncs, choose transforms and sharding strategies, inspect jaxpr/lowering/IR, and benchmark compiled code correctly.
nature-article-writer
IncludedDrafts, rewrites, diagnostically critiques, and style-calibrates primary research manuscripts for Nature and Nature Portfolio journals. Use when the user wants a Nature-style title, summary paragraph or abstract, introduction, results, discussion, methods, figure legends, presubmission enquiry, cover letter, reviewer response, or when a scientific draft sounds generic, jargon-heavy, structurally weak, or AI-ish and needs precise, broad-reader-friendly prose without inventing data, analyses, or references. Best for primary research articles and letters rather than reviews or press releases unless explicitly adapting one.
deckrd
IncludedDocument-driven framework that derives requirements, specifications, implementation plans, and executable tasks from goals through structured AI dialogue. Use when user says "write requirements", "create spec", "plan implementation", "derive tasks", "structure this feature", "break down into tasks", or "document this module". Also use for reverse engineering existing code into docs (/deckrd rev). Do NOT use for direct code writing — use /deckrd-coder after tasks are generated. Do NOT use when the user only wants to run or fix existing code without planning.
clinical-decision-support
IncludedGenerate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.
handling-sf-data
IncludedSalesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use querying-soql), Apex test execution (use running-apex-tests), or metadata deployment (use deploying-metadata).
accelint-ac-to-playwright
IncludedConvert and validate acceptance criteria for Playwright test automation. Use when user asks to (1) review/evaluate/check if AC are ready for automation, (2) assess if AC can be converted as-is, (3) validate AC quality for Playwright, (4) turn AC into tests, (5) generate tests from acceptance criteria, (6) convert .md bullets or .feature Gherkin files to Playwright specs, (7) create test automation from requirements. Handles both bullet-style markdown and Gherkin syntax with JSON test plan generation and validation.