---
description: Workshop setup check — verify this machine and install anything missing (uv, Python, Graphify)
---

You are running the setup check for the workshop **Build Your Research Second Brain with Claude Code**. The person running this may never have used a terminal before today. Be brief, calm, and concrete. Never use `sudo`. Never install a system Python — uv manages Python here.

Go through the checks in order. Fix only what is missing, and re-verify after each fix. If the same fix fails twice, stop and report (step 5) instead of retrying.

## 1. Right folder?

Confirm this is the starter workspace: `CLAUDE.md`, `inbox/`, `sources/`, and `.claude/commands/setup-check.md` exist here.

If not, stop and tell the student exactly this: type `/exit`, open the terminal inside the `research-second-brain` folder (macOS: right-click the folder → *New Terminal at Folder* · Windows: type `powershell` in the folder's address bar), run `claude`, then run `/setup-check` again.

## 2. Graphify already installed?

Check `command -v graphify`, falling back to `"$HOME/.local/bin/graphify"` (on Windows also try `graphify.exe`). If it is found and `--version` prints a version, the CLI is installed — skip to step 4.

## 3. Install uv, then Graphify

- Check `command -v uv` (fallback `"$HOME/.local/bin/uv"`). If missing, install it:
  - macOS / Linux: `curl -LsSf https://astral.sh/uv/install.sh | sh`
  - Windows: `powershell -ExecutionPolicy ByPass -c "irm https://astral.sh/uv/install.ps1 | iex"`
- Then install Graphify pinned to the class version: `uv tool install graphifyy==0.7.19` (yes, double `y` — that is the real package name). Use the full path to `uv` if it is not on PATH yet in this session.
- If uv warns that its tool directory is not on PATH, run `uv tool update-shell`. Full paths are fine for the rest of this session.

## 4. Register the /graphify skill (always run this)

Run `graphify install --platform claude` (full path is fine). This copies the `/graphify` skill into the student's own Claude Code config, so after the course it works in **any** folder on their machine — not just this workspace. Safe to re-run; it just overwrites with the same version.

The new skill only loads when Claude Code restarts — that is the student's final step (see the report).

## 5. Smoke test (free — no tokens, no graph build)

- `graphify --version` prints `0.7.19` (full path is fine).
- Find Graphify's Python: on macOS/Linux read the shebang of the `graphify` script (`head -1`) and run `<that python> -c "import graphify; print('import ok')"`. On Windows, if the shebang trick fails on an `.exe`, accept a working `graphify --version` as the smoke test instead.
- Count the files in `inbox/` — at least 1 expected (a fresh kit has 7 demo notes).

## 6. Report

Print exactly this checklist shape — real values, `✅` pass / `❌` fail, nothing else around it:

```
Setup check — Research Second Brain
✅ Claude Code     running inside the starter workspace
✅ uv              <version>
✅ Python          <version> (managed by uv)
✅ Graphify        0.7.19 — CLI installed
✅ /graphify       skill registered for your whole machine
✅ Inbox           <N> notes ready to graph

🎉 All green — one last step: type /exit, then run claude again.
   When Claude Code is back, type / and you'll see /graphify in the list.
   Then drop a ✅ in the Zoom chat.
```

If anything failed: show its `❌` line with a one-line reason, and tell the student to paste that exact line into the Zoom chat — the instructor takes it from there. Re-running `/setup-check` is always safe; it only fixes what is missing. If Graphify was just installed but a *new* terminal later can't find it, the fix is simply to close and reopen the terminal.
