humantonylee/future-slide

gpt-image-slide

End-to-end GPT image slide workflow. Trigger when the user wants to create a slide deck as generated images from a reference slide, source files, and a deck prompt. Runs design, plan, prompt, and render stages in order.

First seen May 15, 2026

Installation

$ npx skills add humantonylee/future-slide --skill gpt-image-slide

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from humantonylee/future-slide · top by installs.

npx skills add humantonylee/future-slide

Browse all from humantonylee/future-slide

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 146
License LICENSE
Default branch main
Open issues 0
Status Active

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,586 B
  • docs SUMMARY.md 1,552 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 213 installs

SKILL.md

GPT Image Slide Workflow

Use this skill when the user asks for the full GPT-image slide workflow, for example:

  • $gpt-image-slide
  • "create slide images from this reference slide and report"
  • "make a deck with GPT image generation"
  • "run the full future-slide image workflow"

This is the orchestrator. If the user asks for only one step, use the matching step skill instead:

  • $slide-design for DESIGN.md
  • $gpt-image-slide-plan for slide_plan.json
  • $gpt-image-slide-prompt for slide_prompts.json
  • $gpt-image-slide-render for final page_<n>.png images

Required Sequence

Run these stages in order:

  1. Extract DESIGN.md from the reference slide image or visual reference.
  2. Build slide_plan.json from DESIGN.md, user files, and the deck request.
  3. Build slideprompts.json from DESIGN.md and slideplan.json.
  4. Render page images sequentially with Codex native image generation.

Do not skip ahead. Do not render before the prompt JSON exists.

Output Contract

The full workflow should leave these files in the workspace:

  • DESIGN.md
  • slide_plan.json
  • slide_prompts.json
  • page1.png through pageN.png

Routing Rule

If the user mentions HTML, browser-rendered slides, editable web slides, or export from HTML, use the html-slide skill family instead.