carousel-scripter
Skill1 starsChanged 39 days agoMITView on GitHub
Scripts a multi-slide Instagram or LinkedIn carousel as a hook slide, one-idea-per-slide value frames, and a single-CTA closing slide, with per-slide copy and design direction. Use when the user asks to write, script, or outline a carousel, turn a post/idea/listicle into swipeable slides, or build an Instagram carousel or LinkedIn document (PDF) post.
In this repository8 other files it gives its agents.
The file
We split this skill into the rules it gives an agent
10 rules. About 0 are common, 10 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈10
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
- Distinctive: line 16
Write each value slide as one point: a punchy headline (the layer skimmers read) plus 1-2 short support sentences.
- Distinctive: line 18
Write the closing slide with exactly one ask, tied to the value delivered ("Save this before your next launch").
- Distinctive: line 19
Add a one-line design direction per slide (what the visual shows), since copy and layout are inseparable.
- Distinctive: line 20
Write a caption that restates the hook and adds context the slides could not hold.
- Distinctive: line 33
Every slide's point lands in its first words at phone-glance speed.
- Distinctive: line 37
Do not script a carousel for a single tip, one-liner, or time-sensitive moment - recommend a Reel, single image, or text post.
- Distinctive: line 38
Do not dump a paragraph onto a slide or put more than one idea on a frame - split ideas cost swipes, and a lost swipe ends the read.
- Distinctive: line 39
Do not stack multiple asks on the closing slide.
- Distinctive: line 40
Do not ship a weak cover; if slide 1 is weak, nothing downstream matters.
- Distinctive: line 41
Do not bury the point - lead each slide with it, never with throat-clearing.
≈ “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.
Files
Carousel Scripter
Turn one idea into an ordered slide deck where slide one earns the swipe and every slide after earns the next.
Workflow
- Confirm the format fits. A carousel earns its keep on multi-step, list, or framework content. If the idea is a single quick tip or a time-sensitive moment, say so and recommend a Reel, single image, or text post instead - do not script a carousel for a one-liner.
- Confirm platform, audience, and the one outcome the post should drive (follow, save, comment, click). Default to Instagram if unstated and ask once.
- Draft 2-3 cover (slide 1) options. Each is a short headline that stops the scroll and promises a payoff - a number ("7 mistakes…"), a contrarian claim, or a clear transformation - plus a swipe cue. Spend disproportionate effort here.
- Lay out the spine: Hook (slide 1), Stakes / why-it-matters (slide 2), Value slides (3 through n-1, one point each), CTA (final slide). Target 6-10 slides total.
- Write each value slide as one point: a punchy headline (the layer skimmers read) plus 1-2 short support sentences. Front-load the point in the first words. Number each slide.
- End most value slides with a tiny open loop or forward cue so the reader wants the next slide.
- Write the closing slide with exactly one ask, tied to the value delivered ("Save this before your next launch").
- Add a one-line design direction per slide (what the visual shows), since copy and layout are inseparable.
- Write a caption that restates the hook and adds context the slides could not hold.
Platform calibration
- LinkedIn (PDF / document post): educational, framework-driven, more text tolerated, cleaner design.
- Instagram: punchier text, stronger visual dependency, fewer words per frame.
Deliverable
Produce a complete carousel script the user can hand straight to design or a template tool: 2-3 cover options with a recommendation, then a numbered slide-by-slide table where every slide carries its headline, its 1-2 support sentences, and a one-line design direction - closed by the single-CTA final slide and the ready-to-post caption. Nothing in the deliverable should require another writing pass.
Quality bar
- Slide 1 alone makes someone want to swipe; reading only the headlines still delivers the full payoff.
- 6-10 slides; exactly one idea per slide and one CTA on the final slide.
- Every slide's point lands in its first words at phone-glance speed.
- Each slide carries a copy block and a design note; a caption ships with the deck.
Do NOT
- Do not script a carousel for a single tip, one-liner, or time-sensitive moment - recommend a Reel, single image, or text post.
- Do not dump a paragraph onto a slide or put more than one idea on a frame - split ideas cost swipes, and a lost swipe ends the read.
- Do not stack multiple asks on the closing slide; a second CTA halves the chance either gets taken.
- Do not ship a weak cover; if slide 1 is weak, nothing downstream matters.
- Do not bury the point - lead each slide with it, never with throat-clearing.
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
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.

