Skip to the rows

agentsclimarketplace

Short form carousel li

Skill r-bart/scribetronic-plugin/plugins/scribetronic/skills/short-form-carousel-li

Claude Code plugin marketplace for scribetronic — 23 writing skills + workflow hooks. Companion to the scribetronic CLI on npm.

Install

npx -y skills add r-bart/scribetronic-plugin --skill short-form-carousel-li

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

LinkedIn carousel — multi-slide PDF post (8–10 slides typical). Derives from a long-form piece OR a strong listicle / how-to topic. Use when repurposing a published long-form into LinkedIn's highest-engagement format, or when a user has a step-by-step / numbered insight that benefits from one-idea-per-slide pacing.

SKILL.md

3.8 KB, as published. Nobody here has run it

Metadata

inherits: ../short-form-voice-adjustments/SKILL.md
input: a long-form piece OR a strong listicle/how-to topic
format: LinkedIn carousel (PDF, 8-10 slides)

short-form-carousel-li

A LinkedIn carousel is a swipe-through PDF post. High engagement on LinkedIn, requires its own structure — not a thread, not a post, not a slide deck for a talk.

This skill produces the content for the carousel, in slide-by-slide form. The visual design is a separate concern (Figma / Canva / Tella, etc.).

When to use

You have a strong listicle (5-8 items) that benefits from one-item-per-slide pacing.
You have a how-to with 5-7 steps.
You have a launch-retro with strong numbers — carousel format makes the numbers POP.

When NOT to use:

Hot-takes — they need flow, not slide breaks.
Observations — single slide isn't worth a carousel.
Devlogs — too granular per item.

Structure (8-10 slides)

SLIDE 1 — Cover
  - Bold title (5-9 words)
  - Subtitle (one line — the promise / outcome)
  - Author handle/photo

SLIDE 2 — The hook / pain
  - 1-2 sentence statement of the problem or contrarian claim
  - Optional: a strong number

SLIDES 3 to N-2 — Content (1 idea per slide)
  - Header: the point as a short line (3-7 words)
  - Body: 1-3 short sentences elaborating
  - Optional: a single concrete example, number, or short quote

SLIDE N-1 — Summary or "what to do now"
  - Restate the takeaway as a list of 3 actions OR 1 punchy summary

SLIDE N — CTA
  - "Found this useful? Follow [@handle] for more on [topic]."
  - Optional: link to long-form ("Full breakdown in my newsletter")
  - Save / share prompt OK here (LinkedIn norm) but kept simple

Rules

One idea per slide. If a slide has two points, split it.
Headers do the work. Reader will skim headers first. Each header must convey the point standalone.
Bodies are short. Max 30-40 words per slide.
Numbers, names, and dates earn slides. A slide with a specific number is 3x more memorable than a slide with abstraction.
8-10 slides is the sweet spot. Fewer = use a regular post. More = lose the audience by slide 12.
Cover slide must promise + deliver. Don't bait. If your cover says "5 mistakes", the carousel must contain exactly 5 mistakes, named.

Anti-patterns

Carousels that are just a long post split into slides. The format requires reshaping.
Slide bodies longer than 50 words. Reader is swiping, not reading an essay.
Walls of text on cover slide. Cover = promise + author. That's it.
"Save this!" / "Share this!" / 10 emojis on the CTA slide. Restrained CTA wins.
Inconsistent slide structure. Once you set the pattern (header + body + example), stick with it across all content slides.

Workflow

Confirm the source content is carousel-shaped (listicle, how-to with discrete steps, retro with numbers).
Draft the cover: title + 1-line promise.
Draft slides 3 to N-2, one idea per slide. Headers first, then bodies.
Draft the summary slide (N-1). Restate as actions or one punch.
Draft the CTA slide.
Read top-to-bottom. Cut any slide that doesn't earn its place. Aim for 8.
Hand off to design (Figma / Canva). Content is locked at this point.

Output

A markdown file with one section per slide, ready to be designed visually.

## Slide 1 — Cover
**Title:** [...]
**Subtitle:** [...]

## Slide 2 — Hook
[Body]

## Slide 3 — [point name]
**Header:** [...]
**Body:** [...]

...

Gives 1 of the 12 instructions most slides presentations skills give

Counted across 568 of the 571 authors here whose files we hold, read 2026-08-06

include a visual element on every slidein 52 of 568, across 21 files
put one idea per slidehere, and in 50 of 568, across 42 files
state the design approach before writing codein 38 of 568, across 8 files
validate XML immediately after each editin 37 of 568, across 7 files
rasterize gradients and icons as PNG images before referencing themin 37 of 568, across 7 files
generate and inspect thumbnails to validate layoutin 37 of 568, across 7 files
commit to a single visual motif across every slidein 37 of 568, across 12 files
use web-safe fonts onlyin 36 of 568, across 7 files
keep 0.5 inch minimum marginsin 35 of 568, across 9 files
use two-column layout for slides with charts or tablesin 34 of 568, across 5 files
save a template inventory analysis to a filein 33 of 568, across 4 files
use subagents to visually inspect rendered slidesin 33 of 568, across 9 files

Said here and by no other author read

use listicle how-to or retro source content
make headers convey the point standalone
include specific numbers names and dates
ensure the cover slide promise matches the content
keep the cta slide restrained

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.