boar_setup

Files (3)

• SKILL.md
• env.example · templates/
• start.sh · templates/

SKILL.md (first lines)

# Setup

One command sets a repository up for this plugin. Every step checks first and only does what is missing, so running it again repairs a setup without undoing anything.

## Where this runs from

- **The first install.** The user asked, in a fresh session, to install the plugin from `boarlabsxyz/skills`. The plugin is not loaded yet, so you cannot call this skill: you are reading this file from the marketplace clone, `~/.claude/plugins/marketplaces/boarlabs/skills/boar_setup/SKILL.md`. Its root, `~/.claude/plugins/marketplaces/boarlabs/`, stands in for `${CLAUDE_PLUGIN_ROOT}` below, and for Matt's setup you read `skills/mpc_setup-matt-pocock-skills/SKILL.md` there and follow it.
- **Later**, as `/boarlabs:boar_setup`, with `${CLAUDE_PLUGIN_ROOT}` substituted.

Do every step you can, report every one you can't with the exact command or link that fixes it, and go on. Never run an interactive login yourself (`gh auth login`, `codex login`): hand it to the user.

## Steps

1. **The plugin, at project scope.** `.claude/settings.json` must declare the marketplace under `extraKnownMarketplaces.boarlabs` (GitHub `boarlabsxyz/skills`) and enable `boarlabs@boarlabs` under `enabledPlugins`. If either is missing, run from the repository root:

   ```bash
   claude plugin marketplace add boarlabsxyz/skills --scope project
   claude plugin install boarlabs@boarlabs --scope project
   ```

   `claude plugin list` shows the scope. If the plugin is installed at user or local scope, move it: install it at project scope as above, then remove the other with `claude plugin uninstall boarlabs@boarlabs --scope user` (or `--scope local`), so it is active in this repository and nowhere else, and a clone of the repository knows it too.

2. **Prerequisites.** Check each, and for each missing one tell the user what to run:
   - Node 20 or later, with `npx` (`node --version`);
   - a git repository with an `origin` remote on GitHub (`git remote get-url origin`); without one, the skills cannot push their commits (`gh repo create <name> --private --source=. --push`, or `--public`);
   - the GitHub CLI signed in (`gh auth status`; else `gh auth login`): the issue tracker is the repository's GitHub issues;
   - Codex signed in (`codex login status`; else `codex login`): it researches and reads for the other skills;
   - Google Chrome, which the bundled Playwright server drives (`npx -y playwright@latest install chrome` when it is missing). Setup signs nothing in: the first time `boar_review` meets a login wall (a private Google Doc, ClickUp, Miro), it asks the user to sign in once in its browser window, and the plugin's profile keeps the sign-in.

3. **Files in the repository root.** Never overwrite a file that exists.
   - `start.sh`: copy `${CLAUDE_PLUGIN_ROOT}/skills/boar_setup/templates/start.sh` when there is none, or when the existing one is an earlier copy of that template (its second line is `# Starts Claude Code in this repository with the variables of .env exported,`), and make it executable. Any other `start.sh` is the user's: leave it and say so. The template asks for every key of `.env.example` that `.env` lacks and writes it to `.env`, so the user never copies or edits `.env` by hand.
   - `.env.example`: copy `${CLAUDE_PLUGIN_ROOT}/skills/boar_setup/templates/env.example` when there is none; when one exists, append only the keys it lacks, each with the template's comment.
   - `.gitignore`: add `.env` and `tmp/` when they are not ignored yet.

4. **Where results can be written.** Results live on platforms, written through the session's connectors, which come from the user's account, not from this plugin. List which platforms this session can write to (Google Docs or Drive, ClickUp, Miro, Claude artifacts, …) by the tools it has, and name the ones it lacks. `mpc_to-tickets` puts only writable platforms in a ticket's Result.

5. **The issue tracker, labels and doc layout.** Call the Skill tool with `mpc_setup-matt-pocock-skills` (on the first install, read and follow its `SKILL.md` from the marketplace clone, as above). It asks nothing: the tracker is the GitHub Issues of the repository's `origin`, the labels are the five defaults, and the layout is single-context. It writes `docs/agents/`, the `## Agent skills` block of `CLAUDE.md`, and `AGENTS.md` as a symlink to `CLAUDE.md`.

6. **Commit and push.** Stage only what this run wrote or changed (`.claude/settings.json`, `start.sh`, `.env.example`, `.gitignore`, `docs/agents/`, `CLAUDE.md` and the `AGENTS.md` symlink), never `git add .`; commit on `main` with the message `chore: set up the boarlabs plugin`, and `git push -u origin main` (it also sets the upstream the other skills' `git push` uses). If the push is refused, stop and tell the user why; never force it.

7. **Hand over.** Tell the user, as numbered steps:
   1. leave this session (`/exit`);
   2. start again with `./start.sh`: it asks for the OpenRouter key (get one at https://openrouter.ai/settings/keys), writes it to `.env` and starts Claude Code.

   After that the plugin's skills, Playwright and Context7 are loaded. List anything from steps 2 to 4 that is still missing, each with its command or link.

From boarlabsxyz/skills, MIT.

More from boarlabsxyz/skills