agentleFS
lumizonelumizone/social-content-os-claude-skill/skills/carousel-builder/SKILL.md

carousel-builder

Skill0 starsChanged 5 months agoMITView on GitHub

Build a 7–10 slide Instagram/LinkedIn carousel (1080x1350) from a topic or script AND render the slides to PNG. Use when the user wants a carousel, slides, a slide deck for IG/LinkedIn, or says "zrob karuzele o X", "slajdy na instagram", "carousel", "make a carousel", "build slides", "turn this into a carousel". Writes slide-by-slide copy (scroll-stop hook, tension+value middle with light/dark rhythm, identity CTA), a per-slide JSON background-image prompt, generates the background imagery via the fal-media skill, then renders crisp on-brand PNG slides via the bundled render_carousel.py (headless Chrome). Outputs the slide PNGs plus a caption.

6 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

2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 6 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Keep each slide to one idea.

    line 38
  2. Very specific:

    Keep copy specific and human.

    line 74

“Common” is measured: kept by at least 6 in 10 of the 6 edited versions of this file we could read. “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-builder

Produce a finished, renderable carousel: on-brand copy + real PNG slides. Default output: English. Text is rendered as crisp HTML/CSS (never baked into an image model, which mangles paragraph text); imagery is the optional background layer. Reference: carousel mechanics §10, ABC §3, JSON prompting §12 in ../social-content-os/reference/frameworks.md. Load ../social-content-os/brand.json.

Inputs

  • Topic, script, or the winning hook (from hook-lab).
  • Slide count (default 8; range 7–10).
  • Platform (IG default). Whether to generate background imagery (default yes).

Build steps

  1. Structure the deck (ABC across slides):
    • Slide 1 — Scroll-Stop (hook, dark theme): the hook on a specific pain point. Highest visual energy.
    • Middle — Tension & Value: one idea per slide, numbered. Alternate theme light/dark for the "rhythm check". Match visual energy to narrative energy (high contrast on tension, calmer on teaching).
    • Final — Identity CTA: align the CTA with who the viewer wants to become, plus the comment-trigger ("Comment WORD").
    • Keep each slide to one idea; headline short, body 1–2 lines max.
  2. Write slides.json in a new carousel folder (default ./carousels/<slug>/slides.json). Schema:
    {
      "slides": [
        {"n":1,"type":"hook","theme":"dark","eyebrow":"SECTION TAG",
         "headline":"...","body":"","bg_image":"bg-1.png","bg_prompt":"..."},
        {"n":2,"type":"value","theme":"light","eyebrow":"...","headline":"...","body":"..."},
        {"n":8,"type":"cta","theme":"dark","eyebrow":"...","headline":"...","body":"..."}
      ]
    }
    type is hook | value | cta. bg_prompt is the JSON-style image brief (subject as metaphor, not decoration; brand mood/palette); bg_image is the filename it will be saved as.
  3. Generate backgrounds (if enabled): for slides with a bg_prompt, invoke the fal-media skill to generate each background image and save it into the carousel folder as the bg_image filename. Use a 4:5 / portrait size. Put NO hex codes or on-screen text in the image prompt — describe the scene/mood only (the typography is added by the renderer). Hero slides (1 and the CTA) benefit most; teaching slides can stay solid-color (omit bg_image) for legibility.
  4. Render: run python3 <this skill dir>/render_carousel.py ./carousels/<slug> to produce slide-01.png … slide-NN.png (2160x2700, downscale-safe for IG/LinkedIn).
  5. Write the caption by handing the topic to the caption-writer skill (or inline a quick one): hook line + 2–4 value lines + the comment-trigger CTA + 3–6 hashtags. Remind the user to add music so it also hits the Reels feed.

Output

  • The carousel folder with slides.json and the rendered slide-*.png.
  • The caption.
  • A one-line note on what to test next (Best of Nine: recreate this format 3x with different hooks).

Keep copy specific and human. No AI tells (no em-dashes, en-dashes, smart quotes, "unlock/elevate/dive in"). If fal-media or Chrome is unavailable, still write slides.json and the copy, and tell the user what's missing.

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.