Guide / 17

Command line

Make, change and export decks from a terminal, without opening a window.

Where it is

Any terminal · omashow help lists every command

What you can do

omashow new talk.omashow makes a deck; omashow import brings in PowerPoint or Keynote.
inspect lists every slide and the id of each object on it.
apply runs a JSON list of changes: the operations the window uses, by the same names.
export writes a PDF, pictures, a film, a package or a PowerPoint deck.
review reports what Review finds; ops lists every change apply can make.
Every command answers in JSON, and never replaces a file without ‑‑force.

In this film

Ask your coding agent for a presentationOmaShow's skill teaches it the command line
It drives OmaShow for youeach line is a real omashow command it ran
It looks at what it made, and fixes itrendering previews and reading OmaShow's review
A few minutes, start to finish
Open it in OmaShowevery word, photo and chart is yours to edit
Press F5 and it playsthe photos, bullets one at a time, a fade between slides
Set it up once: omashow skill --linkthe skill ships with OmaShow

From a single prompt

OmaShow comes with a skill that teaches coding agents its command line. Set it up once:

omashow skill --link

Then ask your agent for the presentation you want, in plain words. In the film, one request made a six-slide deck with bullet points, a chart and speaker notes in about two minutes: the agent ran OmaShow's commands, rendered previews, read OmaShow's review and fixed what it found. Open the result in OmaShow to edit it or present it.

The commands

`omashow new talk.omashow --theme 1 --slides 3`	Make a deck. Themes 0–2, sizes `16:9`, `4:3`, `portrait` or `1920x1080`.
`omashow import quarterly.pptx`	Turn a PowerPoint or Keynote deck into an OmaShow deck beside it, and say what was left out.
`omashow inspect talk.omashow --slide 0`	Every slide, and the `id` of each object on it. Operations aim at those ids.
`omashow apply talk.omashow changes.json`	Run a list of changes, then save. `--dry-run` checks a plan without writing.
`omashow export talk.omashow --kind pdf --out talk.pdf`	Also `images`, `video`, `package`, `pptx` and `print`.
`omashow review talk.omashow`	What Review would find, and the deck's statistics.
`omashow ops --filter chart`	Every operation `apply` knows, with its arguments.
`omashow help`	All of the above, in the terminal.

A list of changes

Each change names an operation, the same one the window uses. "slide" picks the slide first and "select" picks the object, by the id inspect gave.

[
  {"op": "setSelectedProperty", "slide": 0, "select": "placeholder-c318…",
   "args": ["text", "Quarterly results"]},
  {"op": "addChart", "slide": 1, "args": ["Column"]},
  {"op": "setSlideTransition", "slide": 1, "args": ["kind", "fade"]}
]

Nothing is written until every change has run; one refusal leaves the file untouched. Every command answers in JSON and exits 0 or 1, and none of them replaces an existing file without --force.