Share
SerhiiKorniienko/bullshit-detector
Turn a BS report (or any analysis result) into ready-to-paste posts for X/Twitter, LinkedIn, Facebook, Reddit, Hacker News, or a newsletter issue — plus a branded image carousel (PNGs + PDF) for…
Build a LinkedIn document post (carousel) - slide-by-slide copy, the cover that earns the swipe, and the PDF to upload.
Install Li Carousel
$ npx skills add Jakeschincariol/linkedin-agent-skill --skill li-carousel -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Jakeschincariol/linkedin-agent-skill li-carousel --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Jakeschincariol/linkedin-agent-skill.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/li-carousel .claude/skills/li-carousel && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "li-carousel" agent skill from https://github.com/Jakeschincariol/linkedin-agent-skill/tree/main/skills/li-carousel into .claude/skills/li-carousel/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "li-carousel", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/Jakeschincariol/linkedin-agent-skill/tree/main/skills/li-carouselType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add Jakeschincariol/linkedin-agent-skill --skill li-carousel -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Jakeschincariol/linkedin-agent-skill li-carousel --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Jakeschincariol/linkedin-agent-skill.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/li-carousel .agents/skills/li-carousel && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "li-carousel" agent skill from https://github.com/Jakeschincariol/linkedin-agent-skill/tree/main/skills/li-carousel into .agents/skills/li-carousel/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "li-carousel", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Jakeschincariol/linkedin-agent-skill --skill li-carousel -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Jakeschincariol/linkedin-agent-skill li-carousel --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Jakeschincariol/linkedin-agent-skill.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/li-carousel .cursor/skills/li-carousel && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "li-carousel" agent skill from https://github.com/Jakeschincariol/linkedin-agent-skill/tree/main/skills/li-carousel into .cursor/skills/li-carousel/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "li-carousel", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/Jakeschincariol/linkedin-agent-skill.git --path skills/li-carousel--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Jakeschincariol/linkedin-agent-skill --skill li-carousel -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Jakeschincariol/linkedin-agent-skill li-carousel --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Jakeschincariol/linkedin-agent-skill.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/li-carousel .gemini/skills/li-carousel && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "li-carousel" agent skill from https://github.com/Jakeschincariol/linkedin-agent-skill/tree/main/skills/li-carousel into .gemini/skills/li-carousel/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "li-carousel", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install Jakeschincariol/linkedin-agent-skill li-carouselInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add Jakeschincariol/linkedin-agent-skill --skill li-carousel -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Jakeschincariol/linkedin-agent-skill.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/li-carousel .github/skills/li-carousel && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "li-carousel" agent skill from https://github.com/Jakeschincariol/linkedin-agent-skill/tree/main/skills/li-carousel into .github/skills/li-carousel/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "li-carousel", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Jakeschincariol/linkedin-agent-skill --skill li-carousel -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Jakeschincariol/linkedin-agent-skill li-carousel --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Jakeschincariol/linkedin-agent-skill.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/li-carousel .opencode/skills/li-carousel && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "li-carousel" agent skill from https://github.com/Jakeschincariol/linkedin-agent-skill/tree/main/skills/li-carousel into .opencode/skills/li-carousel/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "li-carousel", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
li-carousel- GitHub stars
- 1.6k
- Token cost
- ~715 tokens
- SKILL.md length
- 336 words
- Files
- 1
- Skills in repo
- 11
- Repo updated
- First seen
- Licence
- MIT
At a glance
Build a LinkedIn document post (carousel) - slide-by-slide copy, the cover that earns the swipe, and the PDF to upload.
- The user says carousel
- SKILL.md covers When to use it instead of a…, Structure, Slide copy rules and Making the PDF, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Slides for LinkedIn
What it does
Li Carousel is an agent skill from Jakeschincariol/linkedin-agent-skill. 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.
Its SKILL.md is about 720 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Documents & Office, covering Slides and decks and PDF. It works with LinkedIn. The repository describes itself as: Eleven free Claude skills that run a LinkedIn account: posts off 21 hook formulas, comments, replies, profile score, weekly plan, and a humanizer that strips the AI fingerprint… The licence is MIT.
When your agent uses it
- The user says carousel
- Slides for LinkedIn
- Turn this into a carousel
- Has a list-shaped idea that would die as a text post
Example prompts
- “carousel”
- “document post”
- “slides for LinkedIn”
- “/li-carousel”
What it can do on your machine
Read from SKILL.md and the folder at commit add2c23. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Li Carousel loads about 715 tokens when it runs. Until then it costs about 73 tokens; SKILL.md has 336 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from Jakeschincariol/linkedin-agent-skill at commit add2c23, republished under its MIT licence (© Jakeschincariol). 336 words, ~715 tokens.
Download SKILL.mdSave it as
.claude/skills/li-carousel/SKILL.md (or your agent's skills folder).- 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
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.
Nothing is uploaded to LinkedIn. The user posts the PDF themselves.
© Jakeschincariol, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/li-carousel of Jakeschincariol/linkedin-agent-skill.
Open the folder on GitHubat commit add2c23
Compare with similar skills
Li Carousel next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Li Carousel this skillJakeschincariol/linkedin-agent-skill | 1.6k | — | ~715 | Automated safety check: Pass | MIT | |
| ShareSerhiiKorniienko/bullshit-detector | 154 | — | ~857 | Automated safety check: Pass | MIT | |
| Paper Deckzsyggg/paper-craft-skills | 1.3k | — | ~1.4k | Automated safety check: Pass | None | |
| Paper2slidesQuZhan51496/paper2anything | 469 | — | ~3.8k | Automated safety check: Notes | Apache-2.0 | |
| Ky Markdown RebuilderKyrieCheungYep/ky-markdown-rebuilder | 117 | — | ~5.7k | Automated safety check: Pass | None | |
| Threads Carouselitchernetski/threads-carousel-claude-skill | 108 | — | ~3.5k | Automated safety check: Pass | MIT |
Similar skills
Paper Deck
zsyggg/paper-craft-skills
将论文、技术文章或知识内容制作成高真实感的 AIGC 幻灯片。先做叙事结构和逐页视觉导演，再调用生图模型生成每一页 16:9 slide image，最后合成为 PPTX/PDF。适合论文汇报、组会、公开课、技术分享、商业化研究展示；当用户提到“论文PPT”“AI生成PPT”“不像AI的PPT”“高质感幻灯片”“逐页生图PPT”时使用。
Paper2slides
QuZhan51496/paper2anything
Turn an academic paper PDF into a presentation deck (.pptx) end-to-end.
Ky Markdown Rebuilder
KyrieCheungYep/ky-markdown-rebuilder
Rebuild visual documents into reliable Markdown by combining text extraction with page or screenshot alignment.
Threads Carousel
itchernetski/threads-carousel-claude-skill
Convert text posts into visual carousel images or presentations for Threads, Instagram, LinkedIn, TikTok, YouTube.
Social Media Carousel
danielmeppiel/agentic-sdlc-handbook
Multi-slide carousel design for Instagram, LinkedIn, and Twitter/X with layout rules and hooks.
More from Jakeschincariol/linkedin-agent-skill
All 11 skills in this repoLi Audit
Jakeschincariol/linkedin-agent-skill
Post-mortem on what the user has already published - which posts actually worked, why, and what to stop doing.
Li Comment
Jakeschincariol/linkedin-agent-skill
Write comments on other people's LinkedIn posts that read as a person with an opinion, not a bot.
Li Dm
Jakeschincariol/linkedin-agent-skill
Write connection notes and DM follow-ups that get replies - the 200-character invite, the first message, and the two follow-ups.
Li Human
Jakeschincariol/linkedin-agent-skill
Strip the machine fingerprint out of any draft - em dashes, AI slop words, invisible watermark characters - and score it against a five-check detection panel before it goes out.
Li Inbox
Jakeschincariol/linkedin-agent-skill
Triage the LinkedIn inbox - sort connection requests and DMs into leads, recruiters, peers and spam, and draft the replies worth sending.
Li Plan
Jakeschincariol/linkedin-agent-skill
Build the week on LinkedIn - what to post, when to post it, and who to engage with.
Related
Works with
Categories
Questions about Li Carousel
What does Li Carousel do?
Build a LinkedIn document post (carousel) - slide-by-slide copy, the cover that earns the swipe, and the PDF to upload. Li Carousel is an agent skill from Jakeschincariol/linkedin-agent-skill. Build a LinkedIn document post (carousel) - slide-by-slide copy, the cover that earns the swipe, and the PDF to upload.
When should I use Li Carousel?
Li Carousel fits situations like: the user says carousel; slides for LinkedIn; turn this into a carousel; has a list-shaped idea that would die as a text post.
How do I install Li Carousel in Claude Code?
Run `npx skills add Jakeschincariol/linkedin-agent-skill --skill li-carousel -a claude-code`. Or copy the skill folder (skills/li-carousel in Jakeschincariol/linkedin-agent-skill) into .claude/skills/li-carousel in your project. Claude Code loads it when a task matches its description.
How do I install Li Carousel in Codex?
Run `npx skills add Jakeschincariol/linkedin-agent-skill --skill li-carousel -a codex`. Or copy the skill folder (skills/li-carousel in Jakeschincariol/linkedin-agent-skill) into .agents/skills/li-carousel in your project. Codex loads it when a task matches its description.
Can I use Li Carousel in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Jakeschincariol/linkedin-agent-skill --skill li-carousel -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/li-carousel, .gemini/skills/li-carousel, .github/skills/li-carousel and .opencode/skills/li-carousel in your project.
What does Li Carousel need to run?
SKILL.md names no scripts, command-line tools or credentials: Li Carousel is instructions for the agent only.
Does Li Carousel access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Li Carousel safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Li Carousel use?
Li Carousel is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Li Carousel use?
About 715 tokens (SKILL.md is roughly 2.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Li Carousel?
Skills that share tags, products or a category with Li Carousel: Share (SerhiiKorniienko/bullshit-detector, 154 stars), Paper Deck (zsyggg/paper-craft-skills, 1.3k stars), Paper2slides (QuZhan51496/paper2anything, 469 stars) and Ky Markdown Rebuilder (KyrieCheungYep/ky-markdown-rebuilder, 117 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Li Carousel?
Jakeschincariol (a GitHub user) maintains it in Jakeschincariol/linkedin-agent-skill, which has 1,627 GitHub stars. The repository holds 11 skills in this directory. The repository was last updated on September 17, 2026.
Source: Jakeschincariol/linkedin-agent-skill on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.