How do I install the Slide Deck skill?

Run npx skillmds@latest add adityahegde712/slide-deck in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Slide Deck safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Slide Deck?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Slide Deck free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Slide Deck?

AdityaHegde712 (@adityahegde712) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Slide Deck by adityahegde712 — Agent Skill

Name: Slide Deck
Author: AdityaHegde712

Slide Deck

Design slide decks and presentations using an HTML-first visual prototyping workflow. Invoke whenever the user asks to create, redesign, or materially modify a presentation, slide deck, PowerPoint, pitch deck, report deck, or individual slides where content placement or visual design must be decided.

File contents

Slide Deck Design Workflow

Design presentation slides visually in HTML before treating the deck design as final.

1. Resolve Presentation Direction

Determine relevant presentation constraints: purpose, audience, narrative, desired takeaway, content requirements, tone, visual direction, branding, slide count/presentation length, density, aspect ratio, existing templates/references. Resolve material ambiguities before locking visual decisions.

2. Design Slides in HTML

Create proposed slides using HTML/CSS as the primary visual design surface for direct control over content, placement, hierarchy, typography, spacing, imagery, composition, sizing, and visual rhythm. HTML must represent intended final slides, not rough placeholders.

3. Render the Slides

Render HTML slides in a browser. Inspect output for: clipping, overflow, alignment, hierarchy, readability, density, consistency, balance, and visual defects. Correct rendering issues before presenting.

4. Capture Screenshots

Capture screenshots of rendered slides and present them to the user to judge content, layout, and visual direction from the rendered composition.

5. Iterate With the User

If changes are requested: (1) Modify HTML/CSS -> (2) Rerender affected slides -> (3) Inspect results -> (4) Capture updated screenshots -> (5) Present to user. Repeat until approved. Treat approved rendered slides as the visual reference for the final artifact.

Completion Check

Before finalization, verify:

Purpose, audience, and constraints resolved.
Non-placeholder HTML/CSS slides created and browser-rendered.
Rendered slides visually inspected for defects.
Screenshots captured, presented to user, and iterated upon until explicit user approval.

---name: slide-deckdescription: Design slide decks and presentations using an HTML-first visual prototyping workflow. Invoke whenever the user asks to create, redesign, or materially modify a presentation, slide deck, PowerPoint, pitch deck, report deck, or individual slides where content placement or visual design must be decided.---# Slide Deck Design WorkflowDesign presentation slides visually in HTML before treating the deck design as final.## 1. Resolve Presentation DirectionDetermine relevant presentation constraints: purpose, audience, narrative, desired takeaway, content requirements, tone, visual direction, branding, slide count/presentation length, density, aspect ratio, existing templates/references. Resolve material ambiguities before locking visual decisions.## 2. Design Slides in HTMLCreate proposed slides using HTML/CSS as the primary visual design surface for direct control over content, placement, hierarchy, typography, spacing, imagery, composition, sizing, and visual rhythm. HTML must represent intended final slides, not rough placeholders.## 3. Render the SlidesRender HTML slides in a browser. Inspect output for: clipping, overflow, alignment, hierarchy, readability, density, consistency, balance, and visual defects. Correct rendering issues before presenting.## 4. Capture ScreenshotsCapture screenshots of rendered slides and present them to the user to judge content, layout, and visual direction from the rendered composition.## 5. Iterate With the UserIf changes are requested: (1) Modify HTML/CSS -> (2) Rerender affected slides -> (3) Inspect results -> (4) Capture updated screenshots -> (5) Present to user. Repeat until approved. Treat approved rendered slides as the visual reference for the final artifact.## Completion CheckBefore finalization, verify:- [ ] Purpose, audience, and constraints resolved.- [ ] Non-placeholder HTML/CSS slides created and browser-rendered.- [ ] Rendered slides visually inspected for defects.- [ ] Screenshots captured, presented to user, and iterated upon until explicit user approval.

Frequently asked questions