The skills run in any agent that reads Agent Skills, and the presentations MCP server reaches the rest. Whichever you use, you get the same watch link.
| Agent | How it connects |
|---|---|
| Claude Code | A plugin, or npx skills add |
| Codex CLI and Gemini CLI | npx skills add |
| Claude Cowork | The Bisque plugin, nothing to install |
| Cursor and VS Code | MCP, one click |
Claude Code
Claude Code can run the skills two ways: copied in as Agent Skills, or installed as a plugin from Bisque's own marketplace. Both give you the same three skills, narrate on your machine, and publish to the same watch URL. The difference is what you type to call them.
Install as a plugin
From a terminal:
claude plugin marketplace add bisque-cloud/presenter
claude plugin install presenter@bisque-cloud
Adding the marketplace installs nothing on its own; the second command
installs present, watch, and video as the presenter plugin. Inside a
Claude Code session, the same two steps are
/plugin marketplace add bisque-cloud/presenter and
/plugin install presenter@bisque-cloud.
A plugin namespaces its skills, so they are /presenter:present,
/presenter:watch, and /presenter:video.
Install as skills
npx skills add bisque-cloud/presenter
This copies the three skills into ~/.claude/skills/, and they answer to
/present, /watch, and /video. The same command puts them in
~/.agents/skills/ for Codex CLI and Gemini CLI, so it is the route to take
when you use more than one agent.
What differs
| Route | You type | Where it runs |
|---|---|---|
| Plugin | /presenter:present, /presenter:watch, /presenter:video | Claude Code |
npx skills add | /present, /watch, /video | Claude Code, Codex CLI, Gemini CLI |
Everything else is the same: the agent writes the slides, your machine narrates them, Bisque hosts them, and you get a link. Pick one route; installing both gives you two names for the same skill.
Skills stack either way. Put the skill on the same line as another command and
the report it produces is presented as soon as it's written. With the plugin
that is /retro /presenter:present; with the skills it is /retro /present.
See it work
You: /presenter:present what changed in this pull request, two minutes, for the reviewers
Agent: Reading the diff. Opening on the migration, then the limiter. https://bisque.today/p/you/pr-412-rate-limits
You: /presenter:watch that link. Does it say why the old limiter was removed?
Agent: Yes, on the limiter slide: it counted retries as requests. Here's the moment: https://bisque.today/p/you/pr-412-rate-limits?t=48
The first time
The first publish signs you in, asks you to pick a handle, and asks you to pick
a voice. The voices are downloads, from a few hundred megabytes to a few
gigabytes, so the first presentation takes a few extra minutes. Every one after
that goes straight from command to link. watch needs none of this for a
public or unlisted presentation.
Codex CLI and Gemini CLI
npx skills add bisque-cloud/presenter
This puts the three skills in ~/.agents/skills/, where both agents find
them, and they answer to /present, /watch, and /video. Your machine
narrates, exactly as in Claude Code. Codex CLI's default sandbox blocks the
network, so installing, signing in, and publishing each ask for approval the
first time.
Claude Cowork
In Claude Cowork, the Bisque plugin turns a document, a thread, or a set of numbers into a presentation people can watch, at a link you can send. There is nothing to install on your machine: Bisque records the narration and hosts the result on its side.
Install
Open Customize, then Plugins, then Add marketplace. Enter
bisque-cloud/presenter and install Bisque. It is one of two plugins in
that marketplace; the other, Presenter, is for a terminal agent on your own
machine.
Installing prompts you to sign in to Bisque. Then pick a handle at bisque.cloud/account. It is the name in every watch URL you publish, and the first one cannot be renamed, so pick one you are happy to keep.
What to ask for
Ask the way you would ask a colleague, and say who is watching.
Make a presentation out of this quarter's numbers for the leadership team.
Turn this thread into a five-minute presentation for the people who weren't in the meeting.
/bisque:present the onboarding doc, for a new hire
Claude reads the material, writes the slides and the script, and publishes. You get a watch URL that plays in any browser, on your own channel at bisque.today. The files it wrote stay in your working directory, so you keep them.
If you don't say who it's for, Claude asks before it starts.
Changing it
Change a slide and ask again. It republishes at the same URL, and the slides you did not touch keep the recording they already have, so a one-line fix costs almost nothing.
| You want | Say |
|---|---|
| A slide reworded | "slide three is too long, cut it in half" |
| It public on your channel | "make it public" |
| Only you able to open it | "make it private" |
| A different voice | "narrate it in a different voice", naming it |
A link is the default: anyone who has it can watch, and it isn't listed on your channel until you say so. Unless you name a voice, the one saved on your account is used.
Images and files
Claude cannot attach a file from your computer. Give it a web link to the image or font instead and it is fetched into the presentation when it publishes. Diagrams, icons, and charts it draws itself.
The same plugin reads presentations back: send Claude a watch link and ask what it says, or ask how many people have watched one of yours. For a terminal agent on your own machine, where narration is free and unlimited and a published presentation can be rendered to an MP4, see present.
Cursor and VS Code
Cursor and VS Code connect to Bisque over MCP rather than installing the skills. Ask either editor for a presentation and you get back the same watch URL. Bisque narrates on its side, so there is no speech model to download.
Connect
One click adds the server to your editor:
Each adds a server called bisque pointing at
https://bisque.cloud/presentations/mcp. The editor walks you through sign-in
the first time you use it: the server asks for it, you approve in a browser,
and the editor holds the connection from then on.
Any other MCP client takes the same URL over streamable HTTP.
https://bisque.today/mcp is the same server. It is listed in the MCP
registry as cloud.bisque/presentations and today.bisque/presentations.
What to ask for
Point at something in your editor and say who is watching.
Make a two-minute presentation of this pull request for the reviewers.
Present the architecture in this folder for a new engineer.
What does https://bisque.today/p/nick/q3-review say about the budget?
The agent reads the material, writes the slides and the script, publishes, and hands you the link once the narration has finished. Ask again with a change and it republishes at the same URL.
What the connection can do
Make a presentation, check whether it has finished, list the ones you have published, see how many people watched one, and read any shared presentation back as text. The full list of tools, and how to add the server by hand, is on the MCP page.
What differs from the skills
With the skills, your machine narrates. Over MCP, Bisque does, so the first
publish involves no download and the presentation can't be rendered to an MP4
from the editor; the video skill does that, on a Mac.
Where it fits
For what to ask for and how to change a presentation, see present. For reading one back, see watch.