nexu-io/codex-slides · Archived
Compatibility entry point for opening and operating Codex Slides in Codex's in-editor Browser, including scenario selection, Design Files, brand systems, decks, and Play mode.
npx skills add nexu-io/codex-slides --skill codex-slides-browser
This repository is archived — consider an actively maintained alternative.
Create, research, revise, restyle, present, inspect, and export Codex Slides slide decks from C…
16 installsVerify that Codex Slides changes are durably reflected in project state and visibly reflected i…
12 installsCollect and persist structured presentation requirements for Codex Slides, including scenario c…
12 installsCompatibility entry point for researching a current topic into a source-backed Markdown brief a…
12 installsRelated neighbors and high-traction skills in the same topics — useful to compare before installing.
Guidance for distinctive, intentional visual design when building new UI or reshaping an existi…
866.4K installsBrowser automation CLI for AI agents. Use when the user needs to interact with websites, includ…
810.4K installsReview UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "chec…
617.3K installsBuild, deploy, evaluate, optimize, fine-tune, and manage Microsoft Foundry agents, models, and …
576.5K installsDebug Azure production issues on Azure using AppLens, Azure Monitor, resource health, and safe …
568.9K installsOther skills from nexu-io/codex-slides.
npx skills add nexu-io/codex-slides
Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.
master
Parsed from SKILL.md frontmatter.
Files included with this skill beyond the listing page.
SKILL.md
2,739 B
SUMMARY.md
342 B
This specialized skill remains for compatibility. The canonical codex-slides sibling skill owns the full workflow and portable CLI.
opencodexslides when the MCP tool is available. Otherwise runnode ../codex-slides/scripts/codex-slides.mjs open --json '<input>' from this skill directory. Pass projectId when the user named a deck; otherwise omit it for the create workspace. Use view:"scenarios" for the 24-workflow catalog, view:"design-files" plus projectId and optional filePath for project files, or view:"brand-system" plus projectId for the brand editor.
stop after printing the URL and do not ask the user to open it manually. Follow browserHandoff.url exactly so slide, panel, version, mode, checkpoint, conversation, and run focus are preserved.
research, outline, or rendering call. Submit the topic in that UI so it creates a durable project and opens the guided workspace. Use start_project / CLI start-project only if UI submission needs a deterministic fallback, then navigate its project resource immediately.
outline review, inspiration/style selection, render, deck review. Do not run the entire workflow invisibly in the Codex conversation.
and mutations, then reload or inspect the Browser result.
Long Deck Agent, outline, and render operations can continue after navigation. Use startprojectrun, retain its runId, and use getprojectrun, waitprojectrun, or cancelprojectrun without closing the Browser.
Use the Browser for scenario/slot selection, @ Design File references, brand system editing, Play from the current slide or the beginning, dual-window presenter mode, speaker notes editing/AI generation, slide navigation, direct on-canvas marking, layout inspection, and other visual interactions. If the Browser capability is unavailable in the current Codex surface, return the resource link and explain that limitation rather than claiming it opened.