Render multi-slide carousels from HTML templates via Playwright. Use when: producing carousel posts.
Scanned 6/8/2026
Install via CLI
openskills install indranilbanerjee/socialforge---
name: render-carousels
description: "Render multi-slide carousels from HTML templates via Playwright. Use when: producing carousel posts."
argument-hint: "[--post <id>] [--all] [--template <type>]"
effort: high
user-invocable: true
---
# /socialforge:render-carousels — Carousel Renderer
Produce multi-slide carousel images from HTML/CSS templates using Playwright headless rendering.
## Supported Templates
| Template | Slides | Best For |
|----------|--------|----------|
| generic-8slide | 8 | General purpose |
| comparison-10slide | 10 | Feature comparisons |
| case-study-10slide | 10 | Client success stories |
| tips-5slide | 5 | Quick tips |
| playbook-8slide | 8 | Step-by-step playbooks |
| recap-6slide | 6 | Event/month recaps |
| data-infographic-6slide | 6 | Data-driven infographics |
| quote-card-single | 1 | Single quote cards |
## Process
1. Select template based on post's `carousel_type`
2. For each slide:
- Inject content (title, body, data points, statistics)
- Apply brand colors via CSS variables (--brand-primary, --brand-secondary, etc.)
- Apply brand fonts
- If slide needs background image: generate or compose via image-compositor
3. Render each slide via Playwright (headless Chromium → PNG, 1080x1080)
4. Show first and last slide to user for approval
5. Compile all slides into PDF (for LinkedIn document upload)
6. Resize slides for other platforms if needed
## Rules
- First slide = hook/title with brand identity
- Last slide = CTA with brand logo and contact info
- Max text per slide: 40 words (LinkedIn) | 25 words (Instagram)
- All slides use brand fonts and colors from brand-config.json
- Slide dimensions: 1080x1080 default (configurable per brand)
## Scripts Used
- render_carousel.py — Playwright HTML→PNG rendering
## Timeout & Fallback
- Per-slide render: 15-second timeout. If Playwright hangs, retry without custom fonts.
- Full carousel: 3-minute timeout for 10 slides.
- If Playwright unavailable: flag for manual rendering, save populated HTML for export.
No comments yet. Be the first to comment!
Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
**Complete production-ready guide for Google Gemini embeddings API** This skill provides comprehensive coverage of the `gemini-embedding-001` model for generating text embeddings, including SDK usage, REST API patterns, batch processing, RAG integration with Cloudflare Vectorize, and advanced use cases like semantic search and document clustering. ---
Interview, source-challenge, verify, save, and ADR-gate fuzzy coding requests into Codex-ready implementation specs. Use when a feature, bugfix, refactor, migration, repo-wide change, or architecture task needs user-verified requirements, source-backed decisions, durable architecture decisions, acceptance criteria, validation commands, rollout notes, saved spec/ADR files, and a Codex execution prompt. Do not use when already fully specified or when the user wants direct implementation now.
Use when a repo needs CodeGraph plus ast-grep for Codex MCP setup, exploration, impact analysis, structural search, or safe refactor planning.