---
title: "The /present skill"
description: "Your agent can present anything."
canonical: https://bisque.cloud/docs/present
---

# /present

Your agent can present anything.

Page: https://bisque.cloud/docs/present
Install: `npx skills add bisque-cloud/presenter`

`npx skills add bisque-cloud/presenter` copies the Agent Skills into any agent's skills directory. In Claude Code you can install them as a plugin instead, from a terminal: `claude plugin marketplace add bisque-cloud/presenter`, then `claude plugin install presenter@bisque-cloud`. The plugin's skills are `/presenter:present`, `/presenter:watch` and `/presenter:video`.

Ask your agent for a presentation. You get slides that play with narration, in
any browser, so you can watch what it did instead of reading it. It's a link,
so you can send it to anyone.

You don't write slides and you don't record anything. You say what you want
covered, and the agent writes it, narrates it, and publishes it. Ask in plain
English, or type `/present`.

## What to ask for

The best requests point at something the agent can go and read — your repo, a
pull request, a document, or work it just finished.

> /present what changed in this pull request, two minutes

> Make a presentation on how auth works in this codebase, for a new engineer.

> Turn Thursday's incident report into a five-minute presentation for the team.

> /present what you did on the migration and what's left

Say how long it should run and who it's for. "A two-minute briefing for the
team" and "a fifteen-minute walkthrough for a new hire" produce different
presentations, and the agent can't guess which one you meant.

Be specific about the source. "Make a presentation about our product" gives the
agent nothing to work from. "Present the three things that changed in v2, from
the changelog" gives it everything.

## Changing it

Ask for changes in plain English. The agent republishes to the same link, so
anything you already sent people keeps working.

| You want                | Say                                       |
| ----------------------- | ----------------------------------------- |
| A slide reworded        | "slide three is too long, cut it in half" |
| A different order       | "move the pricing slide to the end"       |
| A different voice       | "use a warmer voice"                      |
| The whole thing shorter | "get this under three minutes"            |
| A new slide             | "add a slide on what we're doing next"    |
| A file to upload        | "make that a vertical video I can post"   |
| It findable by anyone   | "make it public"                          |
| It locked to you        | "make it private"                         |
| A word said wrong       | "it's pronouncing Bisque wrong"           |

Revise as much as you want. Fixing one slide leaves the rest alone, so a change
takes seconds rather than a full rebuild, and narrating costs nothing however
many times you redo it.

Every presentation starts unlisted: anyone with the link can open it, and
nobody else will find it.

## The first time

Three things happen once, before the agent writes any slides.

**You sign in.** The agent opens a browser and gives you a code to approve.

**You pick a handle.** Presentations are published under it, like a username.
Your first one can't be renamed or released later, so pick one you're happy to
keep.

**You pick a voice.** There's no default. The voices are big downloads and they
differ a lot — a few hundred megabytes at the small end, a few gigabytes at the
large end, and some let you clone your own voice from a recording. The agent
lists them with their sizes and asks you to choose. Your first presentation
after that takes a few extra minutes while the download finishes.

Every presentation after the first goes straight from request to link.

## Good to know

Narration is made on your machine, so it's free and there's no per-word bill.
Publishing goes to bisque.today, which is where the watch link lives.

The small, fast voice and the voice aligner don't run on Intel Macs. The larger
voices all do, so an Intel Mac still gets nine voices; cue timing inside a
slide is approximate there.

Codex CLI's default sandbox blocks the network, so installing, signing in, and
publishing each ask for approval the first time.

If a publish fails, ask the agent to run the check-up. It runs
`node present.mjs doctor`, which tests the whole chain, from the narration
engine to your handle, and speaks a test word to prove audio works. The usual
causes are no Node on the machine, a network approval that wasn't granted, or
not being signed in.

## Where it fits

`present` gets you a link. If you want a file to upload instead, ask for a video
and [video](/docs/video) takes over from there.

Do it in that order. The video is made from whatever the link currently plays,
so change the presentation first and render the video after.