Skip to content
Conduit

skill

one-slide

One-page PowerPoint Skill that turns sparse or complete input into source-traceable, editable professional slides.

marcozhou26/one-slidecommunitylistedunreviewednot running here yet

Set up

Skills are installed by placing their folder where your agent loads skills.

Install instructions come from the README

Skills do not use an MCP config. Follow the steps in the README below; one-click install arrives with accounts.

README

synced Oct 14, 2026

OneSlide

Create one natively editable PowerPoint slide from Markdown, natural-language input, or supplied material. Version 2.5.4 accepts the current Markdown directly; a companion JSON specification or a separate planning Skill is not required.

Download OneSlide · Skill instructions · Report an issue

Get started

  1. Download the release ZIP and retain its top-level one-slide folder.
  2. Copy it into the Skills directory of a compatible agent client, such as ~/.codex/skills/.
  3. Refresh the client and invoke $one-slide with your Markdown or material.

Example:

Create one editable slide comparing overdue rates and average resolution time for these service teams. Keep all supplied counts, periods and units.

A complete design is implemented directly. With sparse input, the agent infers non-blocking design details without requiring a template form. Missing business facts are not filled from reference examples. For a selected page in a multi-page Markdown file, include its page number.

Approved visual references

The nine-page reference library contains page previews, individual usage guidance and the matching PPTX. It is bundled inside this release, so installation does not depend on a separate local shared directory. Deck Foundry's release bundles the same reference snapshot.

References guide grouping, alignment, scales and reading order. They do not supply business data or override a locked design. Existing chart modules remain reusable implementation tools; historical output files are not default design references.

Output and content handling

Each run delivers exactly one native PPTX on a supported 16:9, 9:16 or 3:4 canvas. Text, charts, shapes and connectors remain native objects. Builds, previews and checks stay in the working directory.

Additional source-verification and simulation notes go into speaker notes by default. Calculation conditions, periods, units, business status and uncertainty that changes the claim remain visible. See content placement.

Requirements

Use a compatible Codex runtime with Node.js, Python 3 and @oai/artifact-tool, resolved through the runtime contract. Full native application checks require Microsoft PowerPoint. The generic Presentations authoring rules are not loaded when OneSlide is selected.

python3 scripts/check_environment.py

Contents

  • SKILL.md: entry point and scope.
  • bridge/: input, page selection and content interpretation.
  • implementer/: native construction and layout checks.
  • verifier/: checks against the current input and actual page.
  • references/: contracts and bundled visual references.
  • scripts/ and tests/: environment and implementation checks.
  • showcase/: historical examples retained for repository continuity; current reference selection uses the approved library above.

Historical effective-page-spec-2.2 inputs are supported only when explicitly supplied. They do not replace or constrain a current Markdown handoff.

Licensing

Existing licenses are preserved: Skill code and instructions use Apache License 2.0; eligible original documentation and examples use CC BY 4.0 as specified in CONTENT-LICENSE.md. Supplied or adapted reference artwork retains its own rights and is not granted an additional redistribution license by bundling. See also LICENSE, NOTICE, and TRADEMARKS.md.

Ordinary generated slides do not require an author watermark.

↑↓ navigate openesc close