agentleFS
puntorigenpuntorigen/avatar-skills/carousel-generator/SKILL.md

carousel-generator

Skill3 starsChanged 4 months agoMITView on GitHub

Research the winning carousel structure of Instagram competitors and generate on-brand carousels (per-slide images + caption + hashtags) for any brand. Scrapes the real carousels of a Top-10 competitor list via Apify, proves whether carousels beat reels, derives a slide-by-slide blueprint with Gemini vision, fuses it with reel-discovery narrative patterns, then produces 4:5 slides with Gemini 3 Pro Image (asset-generator), keeping brand palette/typography/identity consistent across slides. Use when the user asks to create an Instagram carousel, study what carousels a competitor/niche is winning with, replicate a winning carousel structure, or produce branded carousel slides with copy and hashtags.

  • Reads credentials

4 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. 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 2

    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:

    Before writing any copy, use the AskQuestion tool to ratify the direction.

    line 85
  2. Distinctive:

    Do not skip this. Present sensible defaults derived from the blueprint and let the user adjust:

    line 86
  3. Very specific:

    Add --dry-run to review the exact per-slide prompts before spending credits.

    line 119

“Common” is measured: kept by at least 6 in 10 of the 4 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 Generator (winning structure → on-brand carousel)

Turn a topic + a brand into a finished Instagram carousel: investigate what carousels the competition is winning with, decompose the winning structure, confirm the angle with the user, then generate the slides, caption and hashtags — all on-brand and visually consistent.

Built on top of two skills bundled in this repo (credentials are reused, nothing new to configure):

  • Image generation → asset-generator (Gemini 3 Pro Image, key from its config.json).
  • Apify token + scraping patterns → reel-discovery (token from its config.json).

When to use

  • "Create an Instagram carousel about <topic> for <brand>."
  • "What carousels is <competitor / niche> winning with? Copy that structure."
  • "Turn this idea into a branded carousel with caption and hashtags."

Setup (one-time)

pip3 install -r .cursor/skills/carousel-generator/scripts/requirements.txt

Credentials are auto-resolved (no setup needed if the sibling skills are configured):

  • Gemini key ← GEMINI_API_KEY env → this skill's config.json → asset-generator/config.json.
  • Apify token ← APIFY_TOKEN env → this skill's config.json → reel-discovery/config.json.

To store them in this skill directly (optional):

python3 .cursor/skills/carousel-generator/scripts/setup_key.py --show   # what's resolved
python3 .cursor/skills/carousel-generator/scripts/setup_key.py \
  --gemini-api-key AIza... --apify-token apify_api_...

The flow (follow in order)

flowchart TD
  msg["Mensaje del usuario + marca"] --> research["1. Investiga tema + scrapea carruseles del Top 10"]
  research --> blueprint["2. Deriva blueprint slide-por-slide + patrones reel-discovery"]
  blueprint --> ask["3. PREGUNTA al usuario (selección): ángulo, puntos, nº slides, dónde va su rostro, CTA"]
  ask --> plan["4. Redacta el copy por slide alineado a la marca"]
  plan --> gen["5. Genera slides (4:5, identidad + estilo consistente)"]
  gen --> caption["6. Genera caption + hashtags"]
  caption --> out["Salida: slides numerados + caption.txt + hashtags.txt + blueprint.md"]

Step 1 — Research the winning carousels

Scrape the competitor Top-10 (or any handle list), separate carousels vs reels, prove which format wins, rank the best carousels and download every slide.

python3 .cursor/skills/carousel-generator/scripts/research_carousels.py \
  --handles sanandoatuex_,leoquins,doctoraflorez \
  --per-profile 12 --top 6 --out-dir runs/rupturas

Omitting --handles uses the built-in Top-10 default. Read runs/rupturas/summary.md for the carousel-vs-reel evidence and the ranked winners.

Step 2 — Derive the blueprint

Gemini vision reads the downloaded slides and labels each one (portada/idea/cita/dato/recap/cta), the hook technique and caption structure; it fuses this with the reel-discovery narrative patterns. Falls back to a heuristic blueprint if vision is unavailable.

python3 .cursor/skills/carousel-generator/scripts/analyze_structure.py \
  --run-dir runs/rupturas --max 4

Produces runs/rupturas/blueprint.md (the molde to replicate).

Step 3 — Confirm with the user (REQUIRED, interactive)

Before writing any copy, use the AskQuestion tool to ratify the direction. Do not skip this. Present sensible defaults derived from the blueprint and let the user adjust:

  • Ángulo / patrón narrativo (listicle P1, contrarian P2, lectura de mente P3, pregunta P4, how-to P5).
  • Puntos clave (los ítems/ideas que irán en las slides).
  • Nº de slides (por defecto el typical_slide_count del blueprint).
  • Dónde aparece su rostro (portada, cierre, ambos, o ninguno).
  • CTA (guardar / comentar / seguir / enlace).

Step 4 — Write the slide plan

Turn the confirmed answers into a plan.json (schema in REFERENCE.md, sample in examples/plan.example.json): one entry per slide with role, headline, body, show_face, style, plus an optional caption and hashtags. Keep copy on-brand (tone from the brand profile) and one idea per slide.

For hashtags, build a ranked set from the winners:

python3 .cursor/skills/carousel-generator/scripts/research_hashtags.py \
  --run-dir runs/rupturas --seed superartuex --limit 25

Step 5 — Generate the carousel

python3 .cursor/skills/carousel-generator/scripts/generate_carousel.py \
  --plan plan.json --brand arnoldo --out-dir out/mi-carrusel
  • --brand is a name in brands/ (e.g. arnoldo) or a path to a brand JSON.
  • The cover (slide 1) is generated first and passed as a style reference to the rest so every slide looks like one coherent set.
  • Add --dry-run to review the exact per-slide prompts before spending credits.

Output in out/mi-carrusel/: slide_01.png … slide_NN.png, caption.txt, hashtags.txt, plan.used.json.

Brands

Reusable profiles live in brands/. Copy brands/_template.json for a new brand (palette, fonts, tone, language, default slide count, logo + identity photos). brands/arnoldo.json is preconfigured for the ruptures/grief niche. To use a real face, add photo paths to assets.identity_photos and set show_face: true on the relevant slides.

Notes

  • Carousels are downloaded as sidecars (all child images) via the Apify IG actor.
  • Visual consistency: brand assets + slide-1 reference are fed to --ref.
  • Everything is Spanish-first by default (the niche is Spanish-speaking).
  • Generated slides and runs/ are media, so they are git-ignored by the repo.

See REFERENCE.md for the plan schema, brand schema, slide styles and troubleshooting.

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.