li-carousel
Skill3 starsChanged 30 days agoMITView on GitHub
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.
7 other projects use a version of this, 6 of them edited.
Adopted by
Most recently taken up by
- furkanbilalakyuz/linkedin-agent-skill-tredited, first seen Nov 8, 2026
- HemanthMChakravarthy/linkedin-agent-skillstheir own version, first seen Nov 8, 2026
- mubaid/dsh-linkedin-agentedited, first seen Oct 25, 2026
- robbiehaynes/job-searchedited, first seen Oct 20, 2026
- avi691/linkedin-agent-skilledited, first seen Oct 8, 2026
- nessalazne/linkedin-agent-skilledited, first seen Sep 19, 2026
Other versions7 projects use a version of this.
Word for word · 0
None found.
Edited · 6
- Jakeschincariol/linkedin-agent-skill★ 51498% same
- avi691/linkedin-agent-skill★ 598% same
- nessalazne/linkedin-agent-skill★ 396% same
- furkanbilalakyuz/linkedin-agent-skill-tr★ 079% same
- mubaid/dsh-linkedin-agent★ 098% same
- robbiehaynes/job-search★ 098% same
Wrote their own version · 1
- HemanthMChakravarthy/linkedin-agent-skills★ 2same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository11 other files it gives its agents.
- li-auditSkill
- li-commentSkill
- li-dmSkill
- li-humanSkill
- li-inboxSkill
- li-planSkill
- li-postSkill
- li-profileSkill
- li-publishSkill
- li-replySkill
- li-repurposeSkill
The file
We split this skill into the rules it gives an agent
4 rules. 3 are common, 0 are distinctive, and 1 is very specific to this project.
3
Common
Most of the 7 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Common: line 12
Document posts are the highest-dwell format on LinkedIn, because a swipe is counted and a scroll is not.
- Common: line 18
Use a carousel when the idea has sequence - steps, a countdown, a before/after progression, a framework with parts.
- Common: line 44
No slide is a paragraph: If you cannot say it in 25 words, split it.
- Very specific: line 59
Write the HTML with one <section> per slide, width:1080px.
“Common” is measured: kept by at least 6 in 10 of the 7 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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 useWrite 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.
This skill uploads nothing. Two ways out:
- PostZen connected (the
createPostandcreateMediaPresigntools are in this session): export the PDF and offer/li-publish. It goes up as a document post: the PDF throughcreateMediaPresign, the post text ascontent, and adocumentTitle(up to 200 characters, usually the cover line), because without one LinkedIn shows the filename. PDF only, up to 100 MB; LinkedIn's 300-page cap is not checked for you, which a 12-slide deck will never hit. The user confirms the full post there before anything goes out. - Not connected: the user posts the PDF by hand, as before.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
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.

