Codex Slides Deck Skill for Codex

Compatibility entry point for scenario-led creation, Design Files, brand systems, inspecting, revising, restyling, and exporting Codex Slides slide decks. Use when a user asks Codex to make a presentation, use project files, edit an existing deck, manage slide structure, apply brand or template rules, or export PDF/PPTX.

1k tokens

context cost

the whole folder, loaded on every use

files

instructions only

copies elsewhere

how many repositories repackaged it

748

stars on the repo

on the repository, not the skill itself

Install

one command, takes just this skill from the repository

npx skills add https://github.com/nexu-io/codex-slides --skill codex-slides-deck

The instruction itself

4 sections, as written by the author

Codex Slides Deck

The canonical codex-slides sibling skill owns the complete workflow. Use the

codex_slides MCP tools when available; otherwise run its self-contained CLI

at ../codex-slides/scripts/codex-slides.mjs. Keep the live workspace available

in the in-editor Browser whenever visual review helps.

Choose the flow

Default to the live Browser workflow: open the Codex Slides home screen,

submit the request there, then operate the created project through clarify,

outline confirmation, style selection, rendering, and review. Keep the

Browser visible throughout.

If Browser UI submission fails, use start_project / CLI start-project to

create the durable project shell, immediately open its returned URL, and

continue in the UI.

Use list_scenarios / CLI scenarios when a named workflow such as business

report, document-to-deck, data insights, brand application, localization, or

batch generation fits. Upload required slot files and pass scenarioId,

materialIds, and materialContexts into creation.

Only when the user explicitly requests an unattended/headless one-call

result, call create_deck or CLI command create.

For CLI automation or recovery, call create_outline, optionally

revise_outline and rank_inspiration, then render_deck; the CLI commands

are outline, revise-outline, inspiration, and render.

For an existing deck, use list_projects or get_project, then choose the

smallest mutation tool.

Edit with the right tool

Use edit_deck for natural-language add/rewrite/redraw/optimize requests.
Use manage_slide for deterministic add, duplicate, delete, or transition.
Use regenerate_slide for one slide.
Use restyle_deck for a whole-deck template/style change.
Use upload_material before creation, editing, or restyling when a local

reference file matters.

Use upload_slide_image for a finished PNG.
Use mark_edit_slide when the user supplies an annotated PNG and wants a

clean revised slide.

Use get_speaker_notes, update_speaker_notes, and

generate_speaker_notes (CLI speaker-notes with get, set, or

generate) for presenter-only talk tracks. These notes persist per slide,

appear in the speaker window, and are embedded in PPTX export.

Use list_design_files, read_design_file, write_design_file, and

upload_design_file for the project file workspace. Pass selected paths as

designFilePaths when revising an outline or editing a deck.

Use get_brand_design_system then update_brand_design_system for persistent

project-wide brand/style rules. Redraw only when requested.

Use start_project_run for navigation-independent chat, outline, or render

work; retain the returned runId and track or cancel it explicitly.

Show and verify

Open open_codex_slides / CLI open before a new creation and keep the live

workspace visible. After a programmatic mutation, navigate or reload its

resource link and inspect the changed slide or flow; do not make the user open

the URL manually.

Follow the exact browserHandoff.url; it can focus the changed slide, speaker

notes, export, versions, Design Files, brand system, Play menu, or durable run.

Use export_deck only after the requested visual result is ready. Browser-only

controls such as Play from current/beginning, the synchronized audience and

presenter windows, notes editing, slide navigation, and direct on-canvas marking

remain available through the live workspace.

Other skills for the same job

different authors, same section of the catalogue

DOCX

by anthropics

vendor ×16

Comprehensive document creation, editing, and analysis with support for tracked changes, comments, formatting preservation, and text extraction. When Claude needs to work with professional documents (.docx files) for: (1) Creating new documents, (2) Modifying or editing content, (3) Working with tracked changes, (4) Adding comments, or any other document tasks

Comprehensive PDF manipulation toolkit for extracting text and tables, creating new PDFs, merging/splitting documents, and handling forms. When Claude needs to fill in a PDF form or programmatically process, generate, or analyze PDF documents at scale.

Presentation creation, editing, and analysis. When Claude needs to work with presentations (.pptx files) for: (1) Creating new presentations, (2) Modifying or editing content, (3) Working with layouts, (4) Adding comments or speaker notes, or any other presentation tasks

Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.

Use this skill whenever the user wants to do anything with PDF files. This includes reading or extracting text/tables from PDFs, combining or merging multiple PDFs into one, splitting PDFs apart, rotating pages, adding watermarks, creating new PDFs, filling PDF forms, encrypting/decrypting PDFs, extracting images, and OCR on scanned PDFs to make them searchable. If the user mentions a .pdf file or asks to produce one, use this skill.

Use this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files). Triggers include: any mention of 'Word doc', 'word document', '.docx', or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx files, inserting or replacing images in documents, performing find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a 'report', 'memo', 'letter', 'template', or similar deliverable as a Word or .docx file, use this skill. Do NOT use for PDFs, spreadsheets, Google Docs, or general coding tasks unrelated to document generation.

Use this skill any time a .pptx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx file (even if the extracted content will be used elsewhere, like in an email or summary); editing, modifying, or updating existing presentations; combining or splitting slide files; working with templates, layouts, speaker notes, or comments. Trigger whenever the user mentions \"deck,\" \"slides,\" \"presentation,\" or references a .pptx filename, regardless of what they plan to do with the content afterward. If a .pptx file needs to be opened, created, or touched, use this skill.

Create and edit Obsidian Flavored Markdown with wikilinks, embeds, callouts, properties, and other Obsidian-specific syntax. Use when working with .md files in Obsidian, or when the user mentions wikilinks, callouts, frontmatter, tags, embeds, or Obsidian notes.

3k tokens

How to use it

Copy the folder

Take nexu-io/codex-slides-deck from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.