agentleFS
saypage-aisaypage-ai/saypage-plugin/skills/carousel-post/SKILL.md

carousel-post

Skill0 starsChanged 11 days agoMITView on GitHub

Plan and build an Instagram carousel (a cover that makes people swipe, one point per slide, a summary worth saving, one ask), check each slide's crop with Saypage's post preview, and publish it with Saypage when the user asks. Use for requests like "make slides from this", "I want a multi-image post", "carousel for my recipe", or when an idea with steps, a list or a comparison would not fit in one image.

2 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

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    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:

    Before any image exists, show the copy as a numbered list and let the user change it.

    line 32
  2. Very specific:

    Write the caption with instagram-caption.

    line 58
  3. Very specific:

    When the last slide asks for a keyword, set up the automation that answers it (the saypage skill), with the user's approval.

    line 64

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

Pick a carousel when people will want to come back to the content: a recipe, a method in steps, a comparison, a checklist, a before and after. Each swipe tells Instagram the post is holding attention, and Instagram may show the post again, opening on slide 2, to people who scrolled past it: slide 2 needs its own pull.

A single surprising claim, or anything that has to be seen moving, works better filmed: point the user to reel-script instead.

1. Plan the slides

Aim for five to ten. Saypage publishes up to 10 images per post (the Instagram app takes 20, which very few ideas fill).

  • Slide 1, the cover: a promise of eight words at most, big enough to read in the grid.
  • Slide 2: the reason to care, in a sentence. Someone may see this slide first.
  • The middle: one point each, a short headline and no more than about 30 words below it. When the text runs longer, give it a second slide.
  • Second to last: everything on one slide, the version people screenshot or save.
  • Last: a single action: save, send to a friend, or comment a keyword.

Small touches that help: a "4/8" counter so people know how far they are, and the handle in a corner of every slide, since screenshots get shared without the caption. Use only the quantities, prices, steps and results the user gave.

Before any image exists, show the copy as a numbered list and let the user change it.

2. Size and layout

  • 1080×1350 px (4:5) for every slide. It is the tallest feed format; Saypage crops feed images outside 4:5 to 1.91:1, and Instagram gives every slide the first one's shape.
  • The profile grid shows posts in a 3:4 frame, which shaves a little off each side of a 4:5 image: leave at least 60 px between the cover's text and its left and right edges.
  • On a phone the slide shrinks to about a third: keep text at 40 px or more. One accent color, and the user's own fonts and colors when they have a brand.
  • Prepare one alt text per slide (alt_texts, in slide order).

3. Make the images

  • With a shell (assistants that can run commands): one HTML section per slide at 1080×1350 px, rendered to PNG or JPEG with headless Chrome or whatever is installed, then each file uploaded with start_image_upload and confirm_image_upload.
  • In chat apps: the user designs the slides in their usual tool (or picks photos) and adds them through the link from request_upload_link; list_images then gives each one's reference.
  • JPEG, PNG or WebP, up to 5 MB each.

4. Check, then publish if asked

  1. preview_instagram_post with the slides in order, and look at each one as Instagram will receive it. A cut headline or face: change fit, or use pad.
  2. Write the caption with instagram-caption. On a carousel the caption's first line does the hooking, because the cover has only a few words.
  3. Publishing needs can_publish_posts in get_account; it is optional and off by default. With it on: prepare_instagram_post (kind: "feed", images, caption, alt_texts), show the user the slides and final caption, and call publish_instagram_post once they say go. Otherwise the user posts from the app.
  4. When the last slide asks for a keyword, set up the automation that answers it (the saypage skill), with the user's approval.

Output

CAROUSEL  ·  7 slides  ·  1080×1350

1  COVER    Sourdough in 5 steps
2  WHY      No stand mixer, no fancy flour, 24 hours start to finish.
3           1. Feed the starter the night before
...
6  ALL-IN-ONE  The 5 steps on one slide
7  ASK      Comment BREAD and I'll send you the printable recipe.

Caption: hook in the first line, one ask, 3 hashtags (instagram-caption)

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.