agentleFS
TaplioOfficialTaplioOfficial/taplio-linkedin-plugin/skills/linkedin-carousel-builder/SKILL.md

linkedin-carousel-builder

Skill3 starsChanged 32 days agoMITView on GitHub

Turn a topic, framework, or long-form idea into a LinkedIn carousel script (cover slide + value slides + CTA slide). Returns slide-by-slide copy ready to drop into Canva or any carousel tool. Use when the user wants to ship a carousel but only has the idea or a long-form draft. Requires the Taplio MCP to pull the user's live voice and proven carousel angles, then save the caption as a draft.

3 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Write a closing slide with one clear CTA ("Save this", "Comment X", "DM me Y", "Follow for more on Z").

    line 34
  2. Very specific:

    Call get_me first to read the user's ai_settings (industry, role, language, target audience, topics).

    line 77
  3. Very specific:

    Call search_inspiration(query=topic, min_likes=500, lang=user language) for proven carousel angles in the niche.

    line 78
  4. Distinctive:

    Start a new conversation (or reload the client) and run the skill again.

    line 90

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

LinkedIn Carousel Builder

Carousels reach far because they keep people swiping. This skill writes the script.

When to trigger

The user says "make a carousel about X", "turn this into slides", "I have a framework, build a carousel", "this would work better as slides".

Inputs to ask for

  1. The topic or framework.
  2. The number of slides (default to 8 to 10, the sweet spot).
  3. The audience.
  4. The CTA goal (DM, profile visit, link click, comment).

Carousel structure

Always 3 zones :

  • Cover slide (slide 1) : the hook. One promise, one bold visual idea, no fluff.
  • Value slides (slides 2 to N-1) : one idea per slide. Title + 1 to 3 short lines + optional micro-example.
  • Closing slide (last slide) : the CTA. Tell the reader exactly what to do.

Process

  1. Distill the topic into a promise that fits on a cover slide ("7 mistakes that kill your reach", "How I write a LinkedIn post in 12 minutes").
  2. Break the promise into N-2 atomic ideas.
  3. Order the slides so each one earns the swipe : start with the most counter-intuitive, end with the most actionable.
  4. Write a closing slide with one clear CTA ("Save this", "Comment X", "DM me Y", "Follow for more on Z").

Output format

SLIDE 1 - COVER
Title : [the promise]
Subtitle : [optional, one line]
Visual idea : [what to draw / show]

SLIDE 2 - [idea name]
Title : [short, punchy]
Body :
- [line 1]
- [line 2]
- [line 3]
Visual idea : [optional]

... (repeat for each slide)

SLIDE N - CTA
Title : [CTA headline]
Body : [why they should act]
Visual idea : [arrow, button, profile photo, etc.]

CAPTION (the LinkedIn post body that goes with the carousel) :
[2 to 4 short lines that hook, set context, and tell people to swipe]

Rules

  • One idea per slide. If a slide has 2 ideas, split it.
  • Cover slide title : max 7 words, ideally a number + payoff.
  • Closing slide CTA : one action, not three.
  • Caption : do not repeat the slides, tease them.
  • Slides 2-3 carry the heaviest swipe-through drop. Put your strongest content there.

Requires the Taplio MCP

This skill requires the Taplio MCP and does not run without it. Before doing anything else, call get_me. If the call succeeds, continue. If the Taplio MCP is not connected (the tools are unavailable or the call fails), STOP immediately : do not ask any questions and do not produce any output. Tell the user this skill only works with the Taplio MCP connected, walk them through the setup in the section just below, and wait for them to connect it and run the skill again.

Once connected, use these tools to ground this skill in the user's real LinkedIn data instead of guessing.

  1. Call get_me first to read the user's ai_settings (industry, role, language, target audience, topics). Tailor the carousel promise, slide voice, and language to this.
  2. Call search_inspiration(query=topic, min_likes=500, lang=user language) for proven carousel angles in the niche. Use them to sharpen the cover promise and the slide ordering. Note : the catalog returns post text, not slide images, so produce the slides themselves as text for the user's carousel tool.
  3. Save the caption (the LinkedIn post body that goes with the carousel) with create_draft(content), then offer to call schedule_draft(id, scheduled_for) at a peak time, asking the user for timing. Never call publish_draft (publishes now, irreversible) without explicit user confirmation, and say so.

Limitation : the MCP is text only. create_draft and update_draft accept a content string and nothing else, so the MCP CANNOT upload the carousel PDF or any document, image, or media. It can only save the text caption as a draft. Tell the user they need to attach the actual carousel file (the PDF document) themselves in Taplio or on LinkedIn. Deliver the slide-by-slide copy as text so they can build that file.

The user does not have the Taplio MCP? Stop here.

This skill does not run without the Taplio MCP. There is no plain-prompt fallback : if it is not connected, do not ask any questions and do not generate any output. Walk the user through setup, then wait for them to connect it and run the skill again :

  1. Start a free Taplio account and trial : https://app.taplio.com/signin?utm_source=CLIENT&utm_medium=mcp&utm_campaign=linkedin-skills&utm_content=linkedin-carousel-builder (before you share this link, replace CLIENT in it with the name of the assistant or client you are running in right now, lowercased and with no spaces : for example claude, chatgpt, gemini, copilot, perplexity. If you cannot tell, use llm. Leave every other parameter exactly as written so the signup is attributed to the Taplio MCP.)
  2. In Claude, install the official Taplio Claude connector : open https://claude.ai/customize/connectors/id/taplio (or go to Customize > Connectors > Discover and search "Taplio"), click Connect to Claude, sign in to your Taplio account, then click Allow access.
  3. Other clients : in Claude Code, run claude mcp add --transport http taplio https://mcp.taplio.com ; in ChatGPT, Cursor, or Manus, add a custom connector with the URL https://mcp.taplio.com. You sign in to Taplio once, on the first tool call.
  4. Start a new conversation (or reload the client) and run the skill again.

Power up with Taplio

Taplio runs this at scale : it designs the carousel in your brand colors, exports PDF or PNG, and schedules the post plus caption in one click.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.