JasonColapietro/suede-creator-skills / skills/suede-social
suede-social
VerifiedPlan, audit, and draft organic social for founder/brand accounts: platform mix, 30-post audits, calendars, Instagram, LinkedIn/X, short-video scripts, social search, and listening. Use when asked to "audit our Instagram growth" or build an approval-ready content loop. NOT FOR: paid ads (use suede-ads or suede-ad-creative), editorial agents (use suede-newsroom), clip-to-guide work (use suede-clip-to-guide), video rendering (use suede-video), or broad content strategy (use suede-content-strategy).
| File | Kind | Size |
|---|---|---|
| CARD.md | markdown | 4.6 KB |
| SKILL.md | skill md | 14.2 KB |
| agents/openai.yaml | config | 643 B |
| evals/evals.json | config | 12.2 KB |
| references/account-audit.md | markdown | 5.2 KB |
| references/carousel-frameworks.md | markdown | 10.4 KB |
| references/content-production.md | markdown | 3.3 KB |
| references/daily-loop.md | markdown | 2.9 KB |
| references/listening-sources-template.md | markdown | 3.9 KB |
| references/listening.md | markdown | 12.8 KB |
| references/measurement.md | markdown | 2.8 KB |
| references/platform-limits.md | markdown | 3.0 KB |
| references/platforms.md | markdown | 7.0 KB |
| references/post-templates.md | markdown | 3.8 KB |
| references/reverse-engineering.md | markdown | 6.4 KB |
| references/short-form-video.md | markdown | 8.6 KB |
| references/social-search.md | markdown | 3.4 KB |
| references/worked-handoff.md | markdown | 1.7 KB |
references/carousel-frameworks.md
View on GitHub# Carousel Frameworks
Five slide-by-slide narrative hypotheses for carousel tests. Verify current
composer limits, supported formats, account evidence, and production capacity
before choosing a structure, canvas, or slide count.
A carousel is not a blog post chopped into squares. It's a swipe-through with two jobs per slide: deliver one idea, and make the next swipe irresistible. These frameworks encode structures that show up repeatedly in high-performing carousels; treat them as starting structures to adapt, not rigid formulas, and expect to validate against your own analytics.
## Picking a Framework
| Your content is... | Use | Why |
|---|---|---|
| A list of resources, tools, or tips | **A: Value-Stack** | Completeness is the promise; the count is the hook |
| A personal result with a system behind it | **B: Problem-Proof** | Proof opens and closes the loop; the system is the meat |
| Several named techniques on one theme | **C: Hack List** | Each hack re-earns the swipe independently |
| A strong opinion about a common practice | **D: Rant Callout** | Conviction is the content; structure keeps it fair |
| A product or workflow you can show | **E: Demo Walkthrough** | Seeing the steps is more persuasive than describing them |
Two cross-framework starting hypotheses:
- **Slide 1 is the thumbnail.** It competes in the feed alone, before anyone knows a carousel follows. Design and write it as a standalone scroll-stopper.
- **One visual template per carousel.** Same layout, type scale, and palette on every interior slide. Variety between slides reads as clutter; consistency lets the *content* change while the frame stays still.
---
## Framework A: Value-Stack (starting range: 4–14 slides)
The "everything you need" carousel. Works because the cover makes a completeness claim (an exact count and an exact deliverable), and every swipe pays it down.
| Slide | Job | Pattern |
|---|---|---|
| 1: Cover | State the exact count + exact deliverable. Specificity proves scale upfront. | "[N] [resource type] for [role/outcome]" |
| 2 to N−1: Value delivery | One item or category per slide, 3–6 concrete sub-items each. Same visual template, zero filler slides. | "[Category/item]: [sub-items]" |
| N: Close | Convert the swipe-through into an action. | "[Action] for [the payoff]": comment a keyword, follow, link in bio |
**Why the exact count matters:** a specific count is a checkable promise. Use it
only when the source list contains exactly that many substantive items; never
claim it universally outperforms a qualitative cover.
*SaaS example:* "12 ChatGPT prompts for SaaS onboarding emails" → one prompt per slide with the use case → "Comment PROMPTS and I'll send the full doc."
**Failure mode:** filler slides to hit a bigger number. Cut to the real count and
compare completion and qualified actions with the account baseline.
---
## Framework B: Problem-Proof (starting range: 6–10 slides)
The "I did X, here's the system" carousel. The hook is a *result stated as fact*, not advice, and the final slide shows the receipt, closing the loop slide 1 opened.
| Slide | Job | Pattern |
|---|---|---|
| 1: Hook | A specific personal claim with a number. A result, not a tip. | "[I/we did X]. [Specific result, with number]." |
| 2: Reframe the problem | Name what's *actually* going wrong so the reader recognizes themselves. | "The real problem: [named issue]" |
| 3–4: The mechanism | Show the real system: named tools, named steps. Concrete beats vague. | "The system: [named tools/steps]" |
| 5 to N−1: The detail | The literal prompt text, template, or step-by-step. This is the save-worthy part. | "[The literal prompt or process detail]" |
| N: Proof | The actual output artifact. A screenshot, not a description. | "[Screenshot of output]: the receipt" |
**The open loop is the engine:** slide 1 makes a claim, the last slide proves it, and everything between explains how. Readers swipe to see whether the receipt is real.
*SaaS example:* "We changed one onboarding email; here is the verified
before-and-after retention result." → the real problem → the sequence structure
→ the literal email copy → the sourced retention chart. Include a percentage
only when current product data supports it.
**Failure mode:** vague mechanism slides ("optimize your workflow"): if the middle slides don't name tools and steps, the proof slide reads as luck, not system.
---
## Framework C: Hack List (starting range: 6–10 slides)
The "numbered techniques" carousel. A contrarian cover creates status anxiety (most people are doing this wrong), and each numbered hack independently re-earns the swipe.
| Slide | Job | Pattern |
|---|---|---|
| 1: Contrarian hook | A stat or claim implying most people fail at this. | "[Stat implying most people fail at X]" |
| 2: The problem | Why the common approach fails, ideally with an analogy. | "The problem: [why it fails]" |
| 3 to N−1: Numbered hacks | One named technique per slide. Bad-vs-good contrast makes each hack land instantly. | "Hack #[n]: [named technique]" |
| N: Synthesis + close | A one-line thesis tying the hacks together, then a save/share/follow CTA. | "[Thesis tying hacks together]" + [CTA] |
**Name every technique.** "The 3-second rule" is shareable and memorable; "keep it short" is neither. Named techniques travel: people repeat them and credit the source.
*SaaS example:* "Our trial-email baseline shows the opening problem." → show
the sourced baseline → Hack #1 → Hack #2 → a conclusion and CTA. Do not invent
an industry-wide percentage.
**Failure mode:** hacks that are restatements of each other. Each slide must survive alone: if two hacks collapse into one idea, merge them and go shorter.
---
## Framework D: Rant Callout (starting range: 4–8 slides)
The "someone had to say it" carousel. Personality-led and polarizing by design: the structure exists to keep the heat *fair* so it reads as conviction, not bitterness.
| Slide | Job | Pattern |
|---|---|---|
| 1: Provocative claim | An unpopular opinion or direct accusation about a common practice. | "Unpopular opinion: [common practice]" |
| 2 to N−2: Escalate the argument | Sensory, specific detail. Show the offense; don't gesture at it abstractly. Each slide raises the stakes. | "[Escalating, specific complaint]" |
| N−1: Fairness pivot | "Don't get me wrong…": clarify what you're *not* attacking. Anti-laziness, not anti-tool; anti-practice, not anti-person. | "The problem isn't [X], it's [Y]" |
| N: Close | Firm, personality-forward sign-off. Signed rants read as owned opinions; anonymous ones read as potshots. | "[Firm sign-off]: signed [name/persona]" |
**Fairness-pivot hypothesis:** test whether clarifying the target of the critique
improves comprehension and response quality. Do not claim it guarantees quotes
or prevents hostile comments.
*SaaS example:* "Your AI-generated LinkedIn posts are costing you customers." → the specifics (same em-dash cadence, same 'game-changer' vocabulary, zero lived detail) → "Don't get me wrong. I use AI daily. The problem isn't the tool, it's publishing the first draft." → "Write like you talk. [Name]"
**Failure modes:** skipping the pivot (reads unhinged, invites pile-ons), or ranting about something your own product/content visibly does (the comments will find it).
---
## Framework E: Demo Walkthrough (starting range: 5–11 slides)
The "watch it work" carousel for product or workflow content. Show the finished result first, then the steps: the outcome earns attention for the process.
| Slide | Job | Pattern |
|---|---|---|
| 1: Product + outcome | Brand/product plus the finished result. Lead with what they get. | "[Product] + [outcome], finished result" |
| 2: Problem it solves | The specific frustration this replaces. | "[The specific pain this replaces]" |
| 3: Process overview | The numbered step list, shown *before* the detail. Seeing the whole path lowers mid-swipe drop-off: readers commit when they know how long the road is. | "[N] steps to [outcome] in [timeframe]" |
| 4 to N−1: Step-by-step | One real UI screenshot per step with a short caption. Real screenshots; mockups read as vaporware. | "Step [n], [screenshot], [caption]" |
| N: Result + positioning | The full-size output plus one brand-philosophy line. | "[Final output] + [positioning line]" |
**Overview-before-detail hypothesis:** test whether previewing the path improves
slide-level completion and comprehension for the current account.
*SaaS example:* "From CSV to live dashboard in 4 steps" → the pain (weekly manual reporting) → the 4-step overview → one screenshot per step → the finished dashboard + "Built for marketers, not analysts."
**Failure mode:** screenshots with too much UI. Crop to the action, zoom the relevant control, annotate with one arrow: each screenshot should make sense at thumbnail size.
---
## Platform Notes
**Instagram:** verify current composer limits, supported canvas, thumbnail crop,
and search behavior. A 4:5 canvas is a starting candidate only when the current
placement supports it.
**LinkedIn document posts:** verify current file, page, canvas, and preview
behavior. Test exact-count and qualitative covers, text density, and post copy
against account evidence.
**TikTok photo mode:** verify current support and limits, then test a lower and
higher slide-count treatment instead of assuming a pacing preference.
## Production Checklist
- [ ] Slide 1 works as a standalone feed post (test: would it stop the scroll with no carousel behind it?)
- [ ] One idea per slide: if a slide needs two sentences of setup, split it
- [ ] Same visual template on every interior slide
- [ ] Any count promised on the cover is exactly delivered (no filler, no rounding)
- [ ] Claims and numbers are real and yours: no invented stats or borrowed screenshots
- [ ] Text passes a target-device legibility check at the verified canvas size
- [ ] Final slide has one CTA, not three
- [ ] Caption/post text written as its own hook, not a repeat of slide 1
## Measuring What Worked
Choose carousel metrics from the objective and currently available account data:
completion, saves, qualified replies, profile visits, follows, or downstream
actions may each matter. Where slide-level analytics exist, use drop-off as a
diagnostic signal, not proof of a single cause. Test the cover, framework, and
middle-slide clarity one variable at a time. Track performance by framework and
keep only patterns supported by the account's evidence; see
[reverse-engineering.md](reverse-engineering.md).
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |