LinkedIn Carousel Builder
Li carousel

Build a LinkedIn document post (carousel) - slide-by-slide copy, the cover that earns the swipe, and the PDF to upload. Use when the user says carousel", "document post", "slides for LinkedIn", "turn this into a carousel", or has a…
--- name: li-carousel description: >- Build a LinkedIn document post (carousel) - slide-by-slide copy, the cover that earns the swipe, 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-shaped idea that would die as a text post. --- # li-carousel Document posts are the highest-dwell format on LinkedIn, because a swipe is counted and a scroll is not. The format rewards one idea broken into steps. It punishes a text post cut into pieces. ## When to use it instead of a text post Use a carousel when the idea has **sequence** - steps, a countdown, a
Overview
Document posts are the highest-dwell format on LinkedIn, because a swipe is counted and a scroll is not. The format rewards one idea broken into steps. It punishes a text post cut into pieces.
Manual install (npx, ZIP)
npx skills add Jakeschincariol/linkedin-agent-skill --skill li-carousel -g -a claude-codenpx degit Jakeschincariol/linkedin-agent-skill/skills/li-carousel#main ~/.claude/skills/li-carouselConnects with Agent Alley MCP · agentalley.io/mcp
Files included
SKILL.md2.8 KB
Read SKILL.md here
Show the full text72 lines
li-carousel
Document posts are the highest-dwell format on LinkedIn, because a swipe is counted and a scroll is not. The format rewards one idea broken into steps. It punishes a text post cut into pieces.
When to use it instead of a text post
Use a carousel when the idea has sequence - steps, a countdown, a
before/after progression, a framework with parts. Use a text post when the
idea is one claim. Splitting one claim across eight slides is the most common
way carousels fail, and if that is what the user has, say so and hand them to
/li-post.
Structure
8-12 slides. Under 8 is a text post. Over 12 and the completion rate falls off a cliff.
1 COVER the hook, 6 words or fewer, plus one line of promise
2 THE STAKE why this matters, in one sentence
3-N ONE IDEA PER SLIDE. A headline of 3-7 words, and at most 25 words
under it. If a slide needs a paragraph, it is two slides.
N+1 RECAP the whole thing as a list, so the screenshot is useful
LAST CTA one action. Follow, comment a keyword, or the link. One.
Slide copy rules
- Slide 1 is 80% of the result. Six words. Big. The rest of the deck cannot save a cover nobody swipes.
- Number every slide (3/10). Completion goes up when people can see the end.
- No slide is a paragraph. If you cannot say it in 25 words, split it.
- The recap slide is the one people screenshot. Make it standalone.
- The user's handle on every slide, small, bottom corner. Screenshots travel without you.
Making the PDF
LinkedIn wants a PDF, 1080x1350 (4:5) for maximum feed real estate, under 100MB, under 300 pages. Build it as HTML and print to PDF:
# one page per slide, 1080x1350, no margins
# then: Chrome headless --print-to-pdf, or any HTML-to-PDF you already use
Write the HTML with one <section> per slide, width:1080px; height:1350px; page-break-after:always, a single accent colour, and type no smaller than
28px - people read these on a phone at thumbnail size. If the user has a brand
skill or design system in this project, use it and do not invent a palette.
Output
The slide-by-slide copy first, as a numbered list the user can read in ten
seconds. Then the accompanying post text - a carousel still needs 2-3
lines above it, which is the actual hook in the feed. Run both through
/li-human. Then build the PDF only if the user approves the copy.
Nothing is uploaded to LinkedIn. The user posts the PDF themselves.
| 1 | |
| 2 | name li-carousel |
| 3 | description >- |
| 4 | Build a LinkedIn document post (carousel) - slide-by-slide copy, the cover |
| 5 | that earns the swipe, and the PDF to upload. Use when the user says |
| 6 | "carousel", "document post", "slides for LinkedIn", "turn this into a |
| 7 | carousel", or has a list-shaped idea that would die as a text post. |
| 8 | |
| 9 | |
| 10 | # li-carousel |
| 11 | |
| 12 | Document posts are the highest-dwell format on LinkedIn, because a swipe is |
| 13 | counted and a scroll is not. The format rewards one idea broken into steps. |
| 14 | It punishes a text post cut into pieces. |
| 15 | |
| 16 | ## When to use it instead of a text post |
| 17 | |
| 18 | Use a carousel when the idea has **sequence** - steps, a countdown, a |
| 19 | before/after progression, a framework with parts. Use a text post when the |
| 20 | idea is one claim. Splitting one claim across eight slides is the most common |
| 21 | way carousels fail, and if that is what the user has, say so and hand them to |
| 22 | `/li-post`. |
| 23 | |
| 24 | ## Structure |
| 25 | |
| 26 | 8-12 slides. Under 8 is a text post. Over 12 and the completion rate falls off |
| 27 | a cliff. |
| 28 | |
| 29 | |
| 30 | 1 COVER the hook, 6 words or fewer, plus one line of promise |
| 31 | 2 THE STAKE why this matters, in one sentence |
| 32 | 3-N ONE IDEA PER SLIDE. A headline of 3-7 words, and at most 25 words |
| 33 | under it. If a slide needs a paragraph, it is two slides. |
| 34 | N+1 RECAP the whole thing as a list, so the screenshot is useful |
| 35 | LAST CTA one action. Follow, comment a keyword, or the link. One. |
| 36 | |
| 37 | |
| 38 | ## Slide copy rules |
| 39 | |
| 40 | **Slide 1 is 80% of the result.** Six words. Big. The rest of the deck |
| 41 | cannot save a cover nobody swipes. |
| 42 | **Number every slide** (3/10). Completion goes up when people can see the |
| 43 | end. |
| 44 | **No slide is a paragraph.** If you cannot say it in 25 words, split it. |
| 45 | **The recap slide is the one people screenshot.** Make it standalone. |
| 46 | **The user's handle on every slide**, small, bottom corner. Screenshots |
| 47 | travel without you. |
| 48 | |
| 49 | ## Making the PDF |
| 50 | |
| 51 | LinkedIn wants a PDF, 1080x1350 (4:5) for maximum feed real estate, under |
| 52 | 100MB, under 300 pages. Build it as HTML and print to PDF: |
| 53 | |
| 54 | |
| 55 | # one page per slide, 1080x1350, no margins |
| 56 | # then: Chrome headless --print-to-pdf, or any HTML-to-PDF you already use |
| 57 | |
| 58 | |
| 59 | Write the HTML with one `<section>` per slide, `width:1080px; height:1350px; |
| 60 | page-break-after:always`, a single accent colour, and type no smaller than |
| 61 | 28px - people read these on a phone at thumbnail size. If the user has a brand |
| 62 | skill or design system in this project, use it and do not invent a palette. |
| 63 | |
| 64 | ## Output |
| 65 | |
| 66 | The slide-by-slide copy first, as a numbered list the user can read in ten |
| 67 | seconds. Then the accompanying **post text** - a carousel still needs 2-3 |
| 68 | lines above it, which is the actual hook in the feed. Run both through |
| 69 | `/li-human`. Then build the PDF only if the user approves the copy. |
| 70 | |
| 71 | Nothing is uploaded to LinkedIn. The user posts the PDF themselves. |
| 72 |
Details
- License
- MIT
- Stars on the repo
- ★ 1,856
- Checked
- Source
- Jakeschincariol/linkedin-agent-skill ↗
- Creator
- Jakeschincariol · 34 listings
Similar skills
See all →
SkillAI LinkedIn Carousel Builder
SkillIG Caption Writer
SkillIG Carousel Planner
SkillSocial Campaign Analyzer
SkillLinkedIn Post Performance Scorer
SkillVideo Caption GeneratorMore from Jakeschincariol
SkillIG Story Writer
SkillLinkedIn Post Audit
SkillLinkedIn Comment Writer
SkillYouTube Channel Auditor
SkillYouTube Chapter Writer
SkillYouTube Comment Responder