← ClaudeAtlas

li-carousellisted

Build a LinkedIn document post (carousel): slide-by-slide copy, the cover that earns the swipe, the 2-3 lines of post text above it, and the PDF to upload. Use when the user says "carousel", "document post", "slides for LinkedIn", "turn this into a carousel", or has a list- or step-shaped idea that would die as a text post.
reportedguy/li-stack · ★ 0 · Data & Documents · score 68
Install: claude install-skill reportedguy/li-stack
# li-carousel Document posts are one of the highest-reach formats (about 1.7-2.3x a single image; much higher engagement than text when they're 6-9 tight slides). A swipe counts as engagement; a scroll doesn't. The format rewards one idea in steps. It punishes a text post chopped into pieces. ## When to use it instead of a text post Use a carousel when the idea has **sequence**: steps, a framework with parts, a before/after, a teardown screen by screen, a checklist. Use a text post when the idea is one claim. If the user has one claim, say so and hand them to `/li-post`. Good builder fits: startup teardowns (S3, H16), exact setups (S2, H40), open-source drops (S5, H07), build logs (S1, H08). ## Structure: 7-10 slides Under 6 is a text post. Past about 10, completion drops off. ``` 1 COVER the hook, 6 words or fewer, plus one line of promise 2 STAKE why this matters, one sentence (a number if you have one) 3..N ONE IDEA PER SLIDE: headline of 3-7 words, at most ~25 words under it N+1 RECAP the whole thing as a list, so the screenshot is useful alone LAST CTA one action: follow, save, or "template in the comments" ``` ## Slide rules - **The cover is most of the result.** Six words, big. The rest can't save a cover nobody swipes. - **Number every slide** (3/9). Completion goes up when people can see the end. - **No paragraphs.** If a slide needs more than ~25 words, it's two slides. - **The recap slide is what people screenshot.** Ma