# Bisque — skills that let your agent present its work Ask your agent for a presentation and watch what it did, instead of reading it. It writes the slides, narrates them on your machine, and gives you a link you can also send. Free, open source, works in Claude Code, Codex CLI, and Gemini CLI. Install: `npx skills add bisque-cloud/presenter` Source: https://github.com/bisque-cloud/presenter --- # Skills What you ask for, and what comes back. ## /present Your agent can present anything. Page: https://bisque.cloud/docs/present 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. ### 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. ## /video Turn a presentation into an MP4. Page: https://bisque.cloud/docs/video Ask for a video and you get an MP4 you can upload. It's made from a presentation you've already published, so it sounds exactly like the link does. Ask in plain English, or type `/video`. It needs a Mac. ### What to ask for Point at a presentation and say where it's going. > Make that a vertical video for TikTok. > Render the Q3 review as an MP4 I can put on YouTube. > Turn bisque.today/p/nick/q3-review into a Short. It works on anything with a link, including presentations you didn't make. Give it one presentation rather than a channel — a channel lists many, and it'll stop and ask which one you meant. ### Changing it | You want | Say | | ------------------ | -------------------------------- | | A vertical video | "make it vertical, for Shorts" | | A square one | "square, for a feed post" | | Widescreen | "normal YouTube shape" (default) | | It saved somewhere | "put it in ~/Movies" | Vertical and square aren't crops. The presentation gets drawn again in that shape, so nothing is cut off the sides. To change what the video _says_, change the presentation. Ask [present](/docs/present) to republish it, then ask for the video again. This step only turns a presentation into a file; it never re-records the narration, so asking it to would give you something that no longer matches the link. ### The first time It downloads what it needs to render, under 30 MB. The agent tells you before it starts, and it only happens once. On Linux or Windows there's no MP4. Send the link instead — it plays in any browser, on any platform. ### While it runs A render takes about as long as the presentation runs, sometimes longer. A four-minute presentation is a several-minute render. Ask the agent to run it in the background and tell you how it's going. It'll report which stage it's on instead of leaving you watching a blank terminal. ### Where it fits `video` is the last step. [present](/docs/present) makes the presentation and owns everything about how it reads and sounds; this turns it into a file. Change first, render after. --- # Works with Running present after another tool. ## gstack Your gstack team can present their work. Page: https://bisque.cloud/docs/gstack Every [gstack](https://github.com/garrytan/gstack) command ends with a report in your terminal: a reviewed plan, a bug list, a security audit, the week in review. `present` turns that report into a narrated presentation, so you can sit back and watch it instead of scrolling it. The finding comes first, then the reasoning, then the evidence, in a few minutes. It's a link, so if someone else needs the same thing, you send it to them. Skills stack. Put `/present` on the same line as any gstack command and the report gets presented as soon as it's written. ### See it work > **You:** /retro /present > > **Agent:** Twelve merges this week, 765 files touched. Ship of the week: … > > Presenting that. Eight slides, four minutes. > https://bisque.today/p/you/the-week-of-august-19 > > **You:** I'm sending this to my investors. Start with what shipped, skip > the file names, and get it under three minutes. > > **Agent:** Reordered, five slides, 2:40. Same link. Want it public, or > keep it unlisted for just them? > > **You:** unlisted Sit back while the agent's work is presented to you. If someone else needs it, send them the link. ### What each stack becomes | Type | You watch | | ------------------------ | -------------------------------------------------------------------------------------- | | `/retro /present` | The week: what shipped, what to fix, what to do differently next week | | `/office-hours /present` | The idea you brought, the premises it challenged, three approaches, and the assignment | | `/autoplan /present` | The plan after four reviews, what each reviewer changed, and the calls left to you | | `/qa /present` | Every bug it found, the screenshot for each, and which ones it already fixed | | `/cso /present` | Findings ranked by severity and confidence, what was checked and came back clean | | `/ship /present` | What went out, the tests that ran, and the link to the pull request | The presentation is built from the report the command already produced. There is nothing extra to write. ### Changing it The agent republishes to the same link, so anything you already sent keeps working. | You want | Say | | ------------------------------- | -------------------------------------------- | | It shorter | "get this under two minutes" | | The finding first | "open on the biggest bug, then the rest" | | Less detail for a non-engineer | "this is for the CEO, cut the file names" | | A slide reworded | "slide three is too long, cut it in half" | | A file for Slack or YouTube | "make that a video I can upload" | ### The first time The first `/present` 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. ### Where it fits This page is about stacking `present` onto gstack. For everything else it can do, and what to say when something looks wrong, see [present](/docs/present). For turning the link into a file, see [video](/docs/video).