agentleFS
Sign inStart free
styfinitystyfinity/linkedin-engine/skills/linkedin-carousel-writer/SKILL.md

linkedin-carousel-writer

Skill9 starsChanged 4 months agoMITView on GitHub

Turn a post into carousel slide copy that mirrors the post 1:1, a cover hook plus 6-9 one-idea body slides plus a CTA slide. Use when you want a post to travel further as a saveable carousel.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 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.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read the post and find its beats: the hook, each supporting idea, the close.

    line 16
  2. Distinctive:

    No em-dashes, no exclamation marks.

    line 28

≈ “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 Writer

Saveable infographics are the most-saved content type, and saves make a post travel. This skill rewrites a post as carousel slides that mirror it beat for beat, so the carousel and the post reinforce each other.

Inputs

  • The post, or the topic to build from: $ARGUMENTS
  • The brief (persona, voice profile, offer, pains) loads automatically. If you were handed a topic and no post, write the post beats first, then map slides to them.

Do this

  1. Read the post and find its beats: the hook, each supporting idea, the close. The slide order maps to this order 1:1.
  2. Cover slide. Take the hook, big and bold. It must read as a thumbnail and stop the scroll on its own.
  3. Body slides, 6 to 9 of them. One idea per slide, plus a single line of caption. Each body slide maps to one beat of the post.
  4. CTA slide. One ask only: comment the keyword, then connect. Keep it short.
  5. Re-read top to bottom. Cut any slide that carries a second idea or repeats the one before it.

Output

Slide-by-slide copy, labelled Slide 1 to Slide N. Under each slide, a one-line design note: what to emphasise visually (the number, the word, the contrast). End with a one-line pointer: render these as 1080x1350 slides in any carousel tool.

Rules

  • One idea per slide. If a slide needs "and", split it.
  • Plain words. The cover must work as a thumbnail at small size.
  • No em-dashes, no exclamation marks. Short lines, not paragraphs.
  • This drafts copy only. The operator approves before anything is rendered or posted.
  • Frame any method as Styfinity's own operating principle, never a named outside source.

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.

Check your setup, free