---
title: "Bisque Claude Code"
description: "Install the skills as a plugin from Bisque's own marketplace."
canonical: https://bisque.cloud/docs/present/works-with/claude-code
---

# Claude Code

Install the skills as a plugin from Bisque's own marketplace.

Page: https://bisque.cloud/docs/present/works-with/claude-code
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`.

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:

```sh
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

```sh
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.

## Where it fits

This page is about getting the skills into Claude Code. For what to ask for and
how to change a presentation, see [present](/docs/present). For reading one
back, see [watch](/docs/present/watch).