slideshow-script skill
✓ VerifiedGenerates five narratively distinct scripts for visual slideshows using different storytelling frameworks like AIDA, PAS, and BAB.
- GitHub stars
- 35
- Files
- 3
- Last commit
- Oct 20, 2026
- License
- MIT
- Allowed tools
- 1
What does the slideshow-script skill do?
slideshow-script generates five narratively distinct scripts for visual slideshows using different storytelling frameworks like AIDA, PAS, and BAB.
Summary generated from the skill's SKILL.md.
About the slideshow-script skill
Creating diverse social media content from a single marketing angle is what this skill enables. It generates five narratively distinct scripts for visual slideshows, TikToks, or carousels by applying different storytelling frameworks such as AIDA, PAS, BAB, Star-Story-Solution, and Stat-Flip. Instead of providing mere layout variations, it produces five unique stories with different hooks and proof points to maximize audience engagement.
An agent should load this skill when a user needs content scripts or social media storytelling. It works best when it can read brand context from files like positioning.md, audience.md, and voice-profile.md to ensure the tone and messaging are accurate. The skill produces structured YAML content specifications in the marketing/content-specs/ directory, which are designed to chain directly into the /paper-marketing tool for visual design. It handles everything from zero-context scenarios to full brand integration, ensuring each script includes slide types, animation hints, and specific visual direction recommendations.
What an agent can do with it
- 1Generate diverse social media scriptsCreate five different narrative scripts for a single positioning angle using various storytelling frameworks.
- 2Produce structured content specificationsWrite structured YAML files that contain slide details and animation hints for downstream design tools.
- 3Develop platform-agnostic storytellingWrite scripts that work across TikTok, Instagram, and YouTube Shorts without being locked to one platform.
- 4Scale content from brand filesUse existing brand positioning and voice profiles to ensure all generated scripts maintain a consistent tone.
Written from the skill's SKILL.md. Every use case is checked against a quote from it.
How to install the slideshow-script skill
Each command copies the skill folder into the client's skills directory. Restart the client or start a new session to load it.Install the slideshow-script skill in Plugin
/plugin marketplace add MoizIbnYousaf/marketing-cli /plugin install marketing-cli@marketing-cli
Install the slideshow-script skill in Claude Code
~/.claude/skills/slideshow-script/SKILL.md
$ npx degit MoizIbnYousaf/marketing-cli/skills/slideshow-script ~/.claude/skills/slideshow-scriptInstall the slideshow-script skill in Claude Code (project)
.claude/skills/slideshow-script/SKILL.md
$ npx degit MoizIbnYousaf/marketing-cli/skills/slideshow-script .claude/skills/slideshow-scriptInstall the slideshow-script skill in Codex
~/.agents/skills/slideshow-script/SKILL.md
$ npx degit MoizIbnYousaf/marketing-cli/skills/slideshow-script ~/.agents/skills/slideshow-scriptInstall the slideshow-script skill in Gemini CLI
~/.gemini/skills/slideshow-script/SKILL.md
$ npx degit MoizIbnYousaf/marketing-cli/skills/slideshow-script ~/.gemini/skills/slideshow-scriptInstall the slideshow-script skill in Claude.ai
npx degit MoizIbnYousaf/marketing-cli/skills/slideshow-script slideshow-script && zip -r slideshow-script.zip slideshow-script # claude.ai → Customize → Skills → + → Create skill → Upload a skill → slideshow-script.zip
Automated checks
Ran Nov 14, 2026Full report →Passed our automated checks. That is not a security audit: read the scripts before you let an agent run them. How checks work
- Source repository linked and reachablemoizibnyousaf/marketing-cli/skills/slideshow-script is public and reachablegithub.com/moizibnyousaf/marketing-cli/tree/HEAD/skills/slid ↗Pass
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit 2026-10-20github.com/moizibnyousaf/marketing-cli/commits ↗Pass
- No download-and-run or credential theft in scriptsNo scripts in the skill folderPass
- No hidden instructions in SKILL.mdNo override phrases, safeguard switches, credential requests or hidden charactersgithub.com/moizibnyousaf/marketing-cli/blob/HEAD/skills/slid ↗Pass
- Pre-approved tools are scopedPre-approved: Bash(mktg status *)github.com/moizibnyousaf/marketing-cli/blob/HEAD/skills/slid ↗Pass
- SKILL.md follows the Agent Skills formatValid name and description; says when to use it; 237 linesgithub.com/moizibnyousaf/marketing-cli/blob/HEAD/skills/slid ↗Pass
SKILL.md
View on GitHub/slideshow-script — Narrative Script Generation
Generate 5 different narrative scripts from a single positioning angle. Each script uses a different storytelling framework, producing 5 publishable pieces of content instead of 5 variations of 1 script.
For scripting frameworks reference, see references/frameworks.md. For content spec YAML schema, see references/content-spec-schema.md.
Why 5 Scripts, Not 5 Layouts
Old model: 1 script × 5 visual layouts = 1 usable output (pick 1, waste 4)
New model: 5 scripts × 5 visual layouts = 5 usable outputs (post all 5)
Each script has a DIFFERENT narrative, DIFFERENT hook, DIFFERENT proof points. When paired with /paper-marketing, each agent gets a unique script AND a unique design direction.
Workflow
Phase 1: Load Brand Context
Read in parallel (if they exist):
brand/positioning.md— available angles, headlines, proof pointsbrand/audience.md— pain points, desires, language patternsbrand/voice-profile.md— tone, vocabulary, do's/don'ts, signature phrases
If any files are missing, the skill still works — see Progressive Enhancement below for how to handle zero-context and partial-context scenarios.
Phase 2: Select Positioning Angle
If the user hasn't specified an angle, present the available angles from brand/positioning.md:
"Which positioning angle should I write 5 scripts for?"
[List angles from positioning.md with their headlines]
Options:
1-N. Select a specific angle
N+1. "Use the primary angle"
Phase 3: Generate 5 Scripts
For the selected positioning angle, generate 5 narratively distinct scripts — one per framework:
| # | Framework | Structure | Hook Style |
|---|---|---|---|
| 1 | AIDA | Attention → Interest → Desire → Action | Bold claim or question |
| 2 | PAS | Problem → Agitate → Solution | Pain point the audience feels |
| 3 | BAB | Before → After → Bridge | "Life before" vs "life after" |
| 4 | Star-Story-Solution | Hook character → conflict → resolution | Personal/relatable story |
| 5 | Stat-Flip | Surprising data → reframe → CTA | Shocking statistic |
Each script includes:
- Hook (slide 1) — the first thing seen, must grab in 1-3 seconds
- 5-7 slides — each with
typeannotation (stat, anchor_word, emotional_pivot, cascade, cta, logo_intro) - CTA (final slide) — clear action with URL/handle
- Animation hints — spring preset suggestion per slide (bouncy, smooth, heavy, snappy)
Script generation rules:
- All 5 must use the SAME positioning angle but tell DIFFERENT stories
- No two scripts should share the same hook
- Each script should use different proof points from the positioning doc
- Voice rules from voice-profile.md apply to ALL scripts
- Slide count can vary (5-9) based on what the narrative needs
Phase 4: Match Scripts to Visual Directions
Each script gets a recommended visual direction for /paper-marketing:
| Framework | Best Visual Direction | Why |
|---|---|---|
| AIDA | Typographic | Text IS the design, progressive revelation |
| PAS | Contrast Play / Split | Tension between problem and solution |
| BAB | Atmospheric | Emotional transformation needs breathing room |
| Star-Story-Solution | Editorial | Story flow needs magazine-like pacing |
| Stat-Flip | Data-Led | Numbers are the visual anchors |
These are recommendations — the user can override.
Phase 5: Present for Approval
Use AskUserQuestion to show all 5 scripts with their visual direction:
"Here are 5 narrative scripts for '{angle_name}', each using a different storytelling framework:"
1. **AIDA** (→ Typographic): "{hook}" — Attention grab → feature interest → desire trigger → CTA
2. **PAS** (→ Contrast Play): "{hook}" — Pain → twist → relief
3. **BAB** (→ Atmospheric): "{hook}" — Before/after transformation
4. **Star-Story-Solution** (→ Editorial): "{hook}" — Story arc → resolution
5. **Stat-Flip** (→ Data-Led): "{hook}" — Shocking stat → reframe
Options:
1. "All 5 look great" — write all 5 content specs
2. "Regenerate #{n}" — rewrite a specific script
3. "Change the angle" — try a different positioning angle
4. "Edit a script" — modify specific slides
5. "Only use 3 of these" — select a subset
Phase 6: Write Content Spec YAMLs
For each approved script, write a structured YAML file:
Path: marketing/content-specs/{project}-{framework}.yaml
Example: marketing/content-specs/lumi-aida.yaml
See references/content-spec-schema.md for the full schema.
spec_version: 1
project: lumi
content_type: tiktok-slideshow
scripting_framework: AIDA
platform:
name: tiktok
width: 1080
height: 1920
aspect: "9:16"
positioning_angle: "The 30-Second Active Gate"
visual_direction: typographic
slides:
- index: 1
type: stat
headline: "30"
subhead: "seconds."
body: null
animation_hint: spring_bouncy
role: hook
- index: 2
type: anchor_word
headline: "Breathe in"
subhead: "That's how long five deep breaths take."
body: null
animation_hint: spring_heavy
role: interest
# ... more slides
- index: 7
type: cta
headline: "lumi.com"
subhead: "Presence before everything."
body: null
animation_hint: spring_smooth
role: action
cta:
url: "lumi.com"
tagline: "Presence before everything."
handle: "@lumi"
voice_constraints:
tone: "calm, certain, mindful"
avoid: ["hype", "guilt", "exclamation marks"]
signature_phrases: ["Take 5 breaths. Unlock your phone.", "Presence before everything."]
Phase 7: Summary
Report what was written:
5 content specs written to marketing/content-specs/:
1. lumi-aida.yaml (7 slides, Typographic)
2. lumi-pas.yaml (6 slides, Contrast Play)
3. lumi-bab.yaml (7 slides, Atmospheric)
4. lumi-story.yaml (8 slides, Editorial)
5. lumi-statflip.yaml (5 slides, Data-Led)
Next: Run /paper-marketing to design each script, or /tiktok-slideshow for the full pipeline.
Standalone Usage
This skill works independently from any orchestrator:
/slideshow-scriptalone → generates scripts for manual design work/slideshow-script→/paper-marketing→ manual export (no video)/slideshow-script→/content-atomizer→ repurpose scripts as text posts/slideshow-script→/email-sequences→ use narratives in email campaigns
Progressive Enhancement
This skill works at three levels of context:
- Zero context — No brand files. Ask the user for: product name, one-sentence description, target audience, and the key benefit. Generate scripts from that. They'll be generic but functional.
- Partial context — Only
positioning.mdexists. Generate scripts from the positioning angles. Copy will be accurate but may lack voice personality. - Full context — All three brand files exist (
positioning.md,audience.md,voice-profile.md). Scripts use the right angles, speak to the right pain points, and sound like the brand.
Anti-Patterns
- Same hook across scripts — The whole point of 5 scripts is 5 chances to grab attention differently. If two scripts start with a question hook, you've wasted one. A viewer who scrolled past hook A might stop for hook B — but only if B looks and sounds different.
- Recycled proof points — Reusing the same stat in multiple scripts means a viewer who sees script 2 after script 1 hears the same argument. Each script should use different proof points from positioning.md so every post adds new information.
- Generic voice — "Transform your life" could be any brand on any platform. Viewers tune it out because they've seen it a thousand times. Using the exact vocabulary and signature phrases from voice-profile.md makes the content feel authored and recognizable.
- Platform-specific copy in scripts — Scripts are the narrative layer, not the design layer. Writing "swipe right" or "link in bio" locks the script to one platform. Keep scripts platform-agnostic so the same narrative works for TikTok, Instagram, YouTube Shorts, or any other format.
- Too many slides — Every slide the viewer must sit through is friction. If a slide doesn't advance the narrative toward the CTA, it's a drop-off point. 5-7 slides usually hits the sweet spot for social content.
- Ignoring the framework — Each framework works because of its specific psychological structure. AIDA builds desire before asking for action. PAS makes pain visceral before offering relief. Blending frameworks dilutes the psychological effect that makes each one work.
Edge Cases
- positioning.md missing — Ask the user: "What's the main angle or benefit you want to highlight?" Use their answer as the positioning angle. Offer to run /positioning-angles to build proper angles.
- Only 1-2 proof points available — Generate fewer scripts (3 instead of 5) and tell the user which frameworks were dropped and why. Quality over quantity.
- User wants fewer than 5 scripts — Respect the request. Ask which frameworks they want, or recommend the best 2-3 for their content type.
- User wants a framework not in the list — Accept custom frameworks. Ask for the structure (what are the phases?) and generate a script following that structure.
- Brand voice conflicts with framework — If the brand voice is "calm, no hype" but PAS requires agitation, dial the agitation to match the voice. Agitate with quiet observations, not exclamation marks.
Principles
- 5 narratives, not 5 variations — every output should be publishable
- Frameworks enforce diversity — AIDA and PAS produce fundamentally different stories
- Content spec is the contract — downstream skills read YAML, not prose
- Archetype annotations matter —
type: stattells Paper agents AND Remotion what to emphasize - Voice rules are non-negotiable — all 5 scripts must sound like the brand
Files in this skill
3slideshow-script skill questions
How do I install the slideshow-script skill in Claude Code?
Run npx degit MoizIbnYousaf/marketing-cli/skills/slideshow-script ~/.claude/skills/slideshow-script. Claude Code loads skills from ~/.claude/skills (all projects) or .claude/skills (one project) and uses a skill when its description matches the task.
Which clients can use the slideshow-script skill?
Any client that reads the Agent Skills format: Claude Code, Codex, Gemini CLI and claude.ai (upload as a ZIP). Scripts in the skill run only where the client allows code execution.
What storytelling frameworks are used for the scripts?
The skill uses five distinct frameworks: AIDA (Attention, Interest, Desire, Action), PAS (Problem, Agitate, Solution), BAB (Before, After, Bridge), Star-Story-Solution, and Stat-Flip.
How does the skill handle missing brand context files?
The skill uses progressive enhancement: if no files exist, it asks for product details to generate generic scripts; if only some files exist, it uses the available context to improve accuracy.
What is the output format of the generated scripts?
The skill outputs structured YAML content specifications designed to be used by downstream design tools.