agentleFS
hiteshbandhuhiteshbandhu/skills-i-use/skills/ig-carousel/SKILL.md

ig-carousel

Skill1 starsChanged 5 months agoMITView on GitHub

Designs and renders Instagram carousels (4:5 slides) as one continuous panorama that is sliced into slides: sticker cut-outs from photos or video stills, bold type, tape, torn paper and halftone that bleed across slide edges, a hook slide first and a single CTA on the last slide. Spec-driven renderer, no design app needed. Triggers on "make a carousel", "instagram carousel", "swipe post", "turn this video into a carousel", "carousel with a CTA", "slides for instagram".

12 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use ig-profile, ig-dm and 4 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • JakeschincariolSkill

    ig-profile

    Score an Instagram profile out of 100 against a 12-part rubric and rewrite the parts that lose points - name field, bio, link, highlights, pinned three, grid. Use when the user says "optimize my profile", "fix my bio", "score my Instagram", "why don't people follow me", or pastes their profile and asks how it reads.

    Also in 8 projects that use this

  • JakeschincariolSkill

    ig-dm

    Write Instagram DMs that get replies - the keyword delivery, the first message to someone who engaged, the collab pitch, and the two follow-ups. Use when the user says "DM this person", "what do I send them", "outreach message", "how do I follow up", "pitch this brand", or is reaching out to someone specific.

    Also in 8 projects that use this

  • vava2684Skill

    ig-reply

    Instagram 貼文留言智慧回覆。抓某篇貼文底下的新留言,由 Claude 在對話裡依貼文內容與留言者語言生成友善回覆,再透過 Graph API 自動送出。觸發時機:使用者說「回覆留言」「處理 IG 留言」「回 IG」「IG 自動回覆」「抓留言來回」「回我 IG 那篇」等。

    Also in 7 projects that use this

  • +3 more from Jakeschincariol

The file

We split this skill into the rules it gives an agent

8 rules. 0 are common, 8 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 11 edited versions we read keep these.

  • 8

    Distinctive

    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:

    Ask only what changes the post: what is the single CTA (comment a keyword, DM, link in bio, save), and whether there are people who must …

    line 37
  2. Distinctive:

    Write the slide list as one line each: hook → 3–6 beats that build → CTA.

    line 41
  3. Distinctive:

    Put at least one element across every seam (a torn strip, tape, a sticker or a pen) so the swipe feels continuous.

    line 53
  4. Distinctive:

    no headline clipped by an overlapping element

    line 58
  5. Distinctive:

    No full stops in headlines.

    line 72
  6. Distinctive:

    Never cover a face with type or tape.

    line 73
  7. Distinctive:

    Ask before downloading outside assets (fonts, photos).

    line 74
  8. Distinctive:

    Keep personal details about the people or project out of any shared or public file.

    line 75

“Common” is measured: kept by at least 6 in 10 of the 11 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

IG Carousel: a swipe post that ends in one ask

You design the carousel, render it from a JSON spec, look at it, fix it, and deliver numbered slides. Everything runs locally.

Supporting files:

  • principles.md: carousel structure, hook and CTA rules, layout and safe zones, a fairness checklist for real people
  • scripts/carousel.py: the renderer (read the docstring for the spec format)
  • examples/spec.example.json: a neutral 5-slide spec to copy

Scripts: carousel.py reads your spec and images and writes JPEGs into the out dir you pass. Nothing else.

Output: {SKILL_OUTPUT_DIR}/ig-carousel/<project>/: spec.json, stickers/, slide_01.jpg…, sheet.jpg. See ../OUTPUT.md.


Step 1: Brief

SettingDefault
Slides5–8 (Instagram allows up to 20; fewer, stronger slides win)
Size1080×1350 (4:5)
Goalone action, stated on the last slide only
Sourcephotos, or stills pulled from video
Copyabout 2–4 words of headline per slide, no full stops

Ask only what changes the post: what is the single CTA (comment a keyword, DM, link in bio, save), and whether there are people who must not appear.

Step 2: Story before pixels

Write the slide list as one line each: hook → 3–6 beats that build → CTA. The hook must work alone in the feed. Each beat is one idea with one visual. The last slide repeats the promise and gives exactly one action. See principles.md.

Step 3: Make stickers

Pick stills with clear subjects. Cut them out with any matting tool, e.g. the reel-edit skill's vision/bin/fg (Apple Vision subject lift, macOS) or rembg. One PNG matte per still (white = keep). Crop the matte when a prop steals focus. Give each person no more than one appearance unless the brief says otherwise.

Step 4: Spec and render

  1. Copy examples/spec.example.json. Panorama x runs across all slides (slide i = [i*1080, (i+1)*1080)).
  2. Put at least one element across every seam (a torn strip, tape, a sticker or a pen) so the swipe feels continuous.
  3. python3 scripts/carousel.py spec.json out/
  4. Open out/sheet.jpg and the hook and CTA slides at full size. Check:

    • text inside the safe zone
    • nothing important cut by a seam
    • no headline clipped by an overlapping element
    • faces not covered
    • CTA legible at thumbnail size

    Fix the spec and re-render. Usually 2–3 rounds.

Step 5: Deliver

Send the slides in order with a 3-line note: slide order, the CTA and what to do when people respond, plus a suggested caption that repeats the CTA. If the CTA promises something (an invite, a link), tell the user they must actually follow up.

Hard rules

  • One CTA, last slide only. No "follow, like, share and comment" lists.
  • Hook slide: big type, a reason to swipe, a swipe cue.
  • No full stops in headlines. Bold, few words.
  • Never cover a face with type or tape; equal prominence for people in group content.
  • Ask before downloading outside assets (fonts, photos); state licences.
  • Keep personal details about the people or project out of any shared or public file.

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.