---
name: doomscroll-get-started
area: Getting Started
surfaces: [plugin, skills]
description: Set up DoomScroll.build for an AI coding agent in two steps, then offer the first video.
---

# Set up DoomScroll.build for your AI coding agent

This playbook prepares your coding agent for DoomScroll.build, which turns a pull request or a local
diff into a short narrated video rendered and watched there. Install the guidance once per coding agent and sign in once per
machine; nothing is created or posted until the user asks for a video.

## How to run

- Run section 1 once per coding agent and section 2 once per machine.
- In section 1, try the DoomScroll.build plugin first and use standalone skills only if the plugin can't be used.
- If a step is blocked, record why and continue with the remaining steps.
- Perform actions directly when terminal or file access is available. Do not merely return commands for the user to copy.
- Pause only for the one browser sign-in in section 2; everything else runs without the user.

## 1. Add DoomScroll.build guidance

Install either the plugin or standalone skills, not both.

### Preferred: DoomScroll.build plugin

Check for Node.js 18+ (`node --version`) and install it if missing and possible, then run:

```bash
npx --yes plugins add doomscroll-build/doomscroll-plugin -y
```

Fall back to skills if the agent doesn't support plugins, the installer reports it unsupported, or Node.js can't be
installed. The plugin's script then lives at
`~/.claude/plugins/marketplaces/doomscroll/skills/doomscroll-video/scripts/doomscroll.mjs`.

### Fallback: standalone skills

```bash
npx --yes skills add doomscroll-build/doomscroll-plugin -g -y -a claude-code
```

For another coding agent, pass that agent to `-a` instead, with a project install unless it supports global skills. The
skill's script then lives at `~/.claude/skills/doomscroll-video/scripts/doomscroll.mjs`.

Confirm the `doomscroll-video` skill is present (list the agent's skills) and note which of the two script paths exists;
that path is `<script>` below.

## 2. Sign in

```bash
node <script> login
```

It prints a link and a short code and opens the link in the browser. One page: the user signs in with GitHub there and
clicks Approve; the script finishes by itself and saves a key for this machine. Pause until it returns. If the browser did
not open, show the user the printed link. Then verify:

```bash
node <script> me
```

It prints the GitHub login, the credits left and `connection`. When `connection.automatic` is false, tell the user in one
sentence that connecting GitHub at `connection.connectUrl` makes a video for every new PR by itself. Every GitHub account gets 5 free videos a day; use the GitHub account
that can access the target repository. No GitHub App installation is needed.

## 3. Offer the first video

If the current folder is a git repository with an open pull request or uncommitted changes, offer to make a video of
it. When the user says yes, follow the `doomscroll-video` skill: it says what the video will be (a 1–2 minute walkthrough
in chapters Currently → The change → After → Blast radius), so fill its notes richly and, for a change people see, walk
through the real UI and send before/after screenshots. For a PR, `scripts/pr-video.sh` (next to `<script>`) submits the
current branch's PR and posts its "cooking" GIF comment. To put the video in the PR, use `--publish`: DoomScroll.build
posts its hosted preview and link through the user's GitHub account; Stealth mode must be off and the user needs write
access to the repository. Never upload the MP4 to GitHub. Verify the returned job id and give the user the video's
`watchUrl` right away as a clickable link, named by its place: "Watch it on doomscroll.build: <link>" (it shows the video
cooking, then plays it). Keep polling until it finishes, show the link again when it is ready and open it in the user's
browser; the script does that by itself for an explicit request (`--no-open` skips it). If you cannot open a browser, say
so and give the link.
Installing the plugin or skill alone never creates a video or touches a PR.

## Completion

Report only verified state, in this block:

```
🎬 DoomScroll.build agent setup is ready.
Guidance: plugin | skills | blocked (<why>)
Script: <path that exists>
Signed in: @<login> (<n> free videos left today) | not signed in (<why>)
Automatic PR videos: on (plugin hooks) | GitHub App | off | skills only
Reload needed: yes | no
```

No terminal? Connect DoomScroll.build's remote server instead. In Claude (web, desktop, mobile) open
https://claude.ai/customize/connectors?modal=add-custom-connector&connectorName=DoomScroll.build&connectorUrl=https%3A%2F%2Fdoomscroll.build%2Fmcp
and click Add, then Connect. Then try it: https://claude.ai/new?q=Use%20DoomScroll.build%20to%20make%20a%20short%20review%20video%20of%20a%20GitHub%20pull%20request.%20Ask%20me%20for%20the%20pull%20request%20link%20first. Other clients: https://github.com/doomscroll-build/doomscroll-plugin#or-connect-the-mcp-server