SKILL.md
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:
``bash 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.