How do I install the Creating Slides skill?

Run npx skillmds@latest add quick-brown-foxxx/creating-slides 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 Creating Slides 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 Creating Slides?

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 Creating Slides free to use?

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

Who published Creating Slides?

quick-brown-foxxx (@quick-brown-foxxx) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Creating Slides by quick-brown-foxxx

Name: Creating Slides
Author: quick-brown-foxxx

Creating Slides

Use when the user asks to create slides, a presentation, a deck, or any slides-like deliverable. Sets up an open-slide workspace and hands the real slide work to open-slide's own auto-installed agent skills. Not for editing slide content directly — bootstrap the workspace first, then work together.

File contents

Overview

Slides are built with open-slide, a slide framework made for agents. It scaffolds a workspace that ships its own agent skills (/create-slide, /slide-authoring) and a hot-reload dev server. Your job is to get that workspace running and rely on those skills — not to write the slides from scratch.

Workflow

Scaffold the open-slide workspace:

npx @open-slide/cli init -h
npx @open-slide/cli init <deck-name> [OPTIONS]

Ask the user where to save the slides before initializing anything.
Initialize the workspace:
- If the target is a monorepo — add the deck as a workspace subproject using the monorepo's package manager (npm/pnpm/…).
- If it is not a monorepo — create a self-contained subproject, using pnpm by default unless the environment prefers another manager.
Recommend restarting the session in the new workspace directory. That lets the session auto-load the open-slide skills installed there, which is the smoothest path.
Or continue in the current directory. Then load only what you need to understand the workspace:
- Read the workspace AGENTS.md for hard rules.
- Read the frontmatter (name + description) of every skill under .agents/skills to learn what is available. Do not load full skill bodies up front — lazy-load them on demand when a skill becomes relevant.
Start the dev server with the active package manager (pnpm run dev or npm run dev).
Tell the user the port/URL where the deck is served.
Work together — follow open-slide's own skills for authoring, reviewing in the browser, and iterating on the deck.

Notes

This skill is high-level. The concrete deck logic lives in the installed open-slide skills; this skill only owns setup and handoff.

---name: creating-slidesdescription: Use when the user asks to create slides, a presentation, a deck, or any slides-like deliverable. Sets up an open-slide workspace and hands the real slide work to open-slide's own auto-installed agent skills. Not for editing slide content directly — bootstrap the workspace first, then work together.---## OverviewSlides are built with [open-slide](https://github.com/1weiho/open-slide), aslide framework made for agents. It scaffolds a workspace that ships its ownagent skills (`/create-slide`, `/slide-authoring`) and a hot-reload dev server.Your job is to get that workspace running and rely on thoseskills — not to write the slides from scratch.## Workflow1. **Scaffold** the open-slide workspace: ```bash npx @open-slide/cli init -h npx @open-slide/cli init <deck-name> [OPTIONS] ```2. **Ask the user where to save the slides** before initializing anything.3. **Initialize the workspace:** - If the target is a **monorepo** — add the deck as a workspace subproject using the monorepo's package manager (npm/pnpm/…). - If it is **not** a monorepo — create a self-contained subproject, using **pnpm by default** unless the environment prefers another manager.4. **Recommend restarting the session** in the new workspace directory. That lets the session auto-load the open-slide skills installed there, which is the smoothest path.5. **Or continue in the current directory.** Then load only what you need to understand the workspace: - Read the workspace `AGENTS.md` for hard rules. - Read the frontmatter (name + description) of every skill under `.agents/skills` to learn what is available. Do **not** load full skill bodies up front — lazy-load them on demand when a skill becomes relevant.6. **Start the dev server** with the active package manager (`pnpm run dev` or `npm run dev`).7. **Tell the user the port/URL** where the deck is served.8. **Work together** — follow open-slide's own skills for authoring, reviewing in the browser, and iterating on the deck.## NotesThis skill is high-level. The concrete deck logic lives in the installed open-slide skills; this skill only owns setup and handoff.

Frequently asked questions