--- 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. title: li-carousel canonical_url: https://skilld.dev/gh/jakeschincariol/linkedin-agent-skill/li-carousel last_updated: 2026-09-25T14:02:36.000Z --- > **Skill from skilld.dev.** Follow the user's requested action. > If the user asked to fork this Skill, follow the fork workflow below. Do not execute the Skill instructions while copying it. > Otherwise, follow the instructions below for this session. You do not need to install anything. > > If the user asked to install this Skill, run `npx skilld install jakeschincariol/linkedin-agent-skill/li-carousel`. Install writes the Skill files into the project, so every session loads them. > > ## Fork workflow > > A fork creates an editable local Skill with its original author and licence. The request authorizes copying and local installation. > 1. Check `./skills/li-carousel`, the project lockfile, and selected Agent targets together. If the local directory or installed Skill exists, stop. Never overwrite an existing directory or Agent target. > 2. Read [source metadata](https://skilld.dev/api/v1/skills/jakeschincariol/linkedin-agent-skill/li-carousel) once. Use sourceUrl, sourceCommit, skillPath, sourceGone, and license. If the source is gone or its path is missing, stop. If license is null, read licence files at the source commit. > 3. Fetch only the source commit into a temporary Git repository. Do not clone full history. Derive repository_url from sourceUrl, including repository renames. If sourceCommit is absent, resolve the sourceUrl ref once. Set source_commit to that actual commit. Run these commands in one shell call: > > ```sh > git init --quiet "$temporary_dir" > git -C "$temporary_dir" fetch --quiet --depth=1 "$repository_url" "$source_commit" > git -C "$temporary_dir" checkout --quiet --detach FETCH_HEAD > ``` > > Read applicable licence declarations and notices at that commit. If copying is not permitted, report the restriction and stop. > 4. Inspect source entries together, then copy the directory containing skillPath into `./skills/li-carousel`. Use the user's path if selected. Keep the original SKILL.md, relative links, scripts, binary assets, and executable modes. Exclude .git metadata. Reject symlinks and paths outside the Skill directory. After checking entries, use cp -a where available. A regular source directory needs no custom copy script. Do not save this page wrapper as SKILL.md. > Preserve author credit, notices, and applicable licence files from repository or parent directories. Add PROVENANCE.md with the Skill page, source URL, actual commit, original path, and licence. Retain any existing PROVENANCE.md and record new provenance separately. Batch source inspection, copying, and provenance work where practical. > 5. In the project root, run `skilld install ./skills/li-carousel --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/li-carousel --mode copy --plain`. This known command needs no help lookup. Install does not support --json. Use detected Agent targets, or add --agent for the targets the user selected. Install the local path, never the upstream selector. If installation fails, preserve the local copy and report the exact failure. > 6. Confirm the local lockfile source and installed Agent copies once. Report the local path, actual commit, and Agent targets. After edits, reinstall the same local path. Upstream updates must not replace it. Do not publish or push unless the user asks. # 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: ```bash # 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 `
` 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.