agentleFS
Sign inStart free
CodesbyFebinCodesbyFebin/linkedin-manager/skills/linkedin-carousel-writer/SKILL.md

linkedin-carousel-writer

Skill0 starsChanged 39 days agoMITView on GitHub

Turn one claim into a LinkedIn document or carousel script. Use when the user wants slides, a PDF post, or a swipe deck. Not for a single text post (use linkedin-post-writer).

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

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. Very specific:

    Not for a single text post.

    line 15
  2. Very specific:

    Read ../../references/voice-profile.md only if filled: yes.

    line 18
  3. Distinctive:

    Write 7 to 10 slides. Slide 1 is the hook, under 12 words.

    line 20
  4. Distinctive:

    No emoji. No hashtag block.

    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

Carousel writer

Build a document post as a sequence of claims, not a blog pasted onto slides.

When to use

  • "Make a carousel from this note"
  • "Turn this post into slides"
  • "Script a LinkedIn document"

Not for a single text post. Hand that to linkedin-post-writer.

Steps

  1. Read ../../references/voice-profile.md only if filled: yes. Read ../../references/story-bank.md the same way. Never invent a number.
  2. Pull one claim. If the note has three claims, ask which one leads.
  3. Write 7 to 10 slides. Slide 1 is the hook, under 12 words. Last slide is one action, not a logo dump.
  4. Each middle slide is one sentence plus one receipt (a number, a name, a failed attempt).
  5. Show the deck as a numbered list. Wait. Do not publish until the user says post.
  6. On approval, publish the caption via lib.publish only if the user also approved the caption. The slide file itself is returned for upload. This skill does not invent a file host.

Hard rules

Global voice rules: see root SKILL.md Voice rules.

  • No emoji. No hashtag block.
  • No "swipe to learn" filler.
  • Caption hook in the first 210 characters.
  • External link goes in the first comment, not the caption.

Related

  • linkedin-post-writer
  • linkedin-humanizer
  • linkedin-approval-gate
  • ../../references/voice-rules.md
  • ../../references/operator-codesbyfebin.md

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