Claude Code plugin

Four slash commands that bring Harvv into Claude Code: install the pixel, diagnose why your visitors are abandoning, generate a fix from detected behavior, and review your issues — all without leaving the editor.

Install

/plugin install github:harvv-hq/harvv-claude-plugin

Run that inside any Claude Code session. The plugin installs in seconds and registers five slash commands.

Commands

/harvv:install — Set up the pixel in this project

The fast path for a fresh project. Claude:

  1. Detects your project type (Next.js, Shopify, WordPress, Astro, Vite, plain HTML, etc.)
  2. Asks for your email
  3. Creates a free Harvv account + site + pixel key automatically (no manual signup)
  4. Injects the pixel snippet into the right file for your stack
  5. Sends you a welcome email with a magic link to set your dashboard password

You go from npm install to live pixel in under a minute.

/harvv:why — Diagnose a visitor problem

Ask Claude things like:

Claude pulls the relevant signals from your Harvv dashboard via the API, correlates against your codebase, and gives you a grounded answer with the specific evidence cited.

/harvv:fix — Generate a code fix from a detected issue

Point Claude at a specific issue ID or paste the issue title; it pulls the AI-enriched element context (selector, surrounding DOM, click handler if any) and generates a precise code change. Works best on dead clicks and broken click handlers where the fix is mechanical.

/harvv:issues — Review your active issues

Lists everything Harvv has open for your sites: dead-click clusters, rage-click bursts, slow API endpoints, layout-shift outliers, form- abandonment patterns. Sorted by impact (sessions affected). One-line summary each; ask for detail on any.

/harvv:setup — Check the setup, teach Harvv the business, schedule reports

The onboarding skill. It uses the Harvv MCP connector (claude mcp add --transport http harvv https://harvv.com/mcp), not the API key, because it reads what Harvv has observed and writes what only you know. Claude:

Not a developer? The plain three-step version with links is at harvv.com/claude.

The same skill runs in claude.ai: download harvv-setup.skill, add it under Settings → Skills, connect the Harvv connector, then say "set up Harvv".

A second skill answers "why is nobody buying": it finds where shoppers get stuck between the cart and the order, looks at those pages the way a phone shows them, walks the checkout in your assistant's browser (stopping before any personal details), and ends with a fix list split into what you can change and what your platform has to. Download harvv-why.skill and add it the same way.

API key setup (one-time)

The pixel-install command works without an account. The other three commands (why / fix / issues) need an API key so Claude can read your dashboard. Once installed, get a key:

  1. Open the classic portal → your site → Settings → API Keys (Studio has no API-key screen yet)
  2. Click Create Key
  3. Copy the hv_live_… value (shown once)
  4. The first time you run /harvv:why or /harvv:fix, Claude will prompt for it. It's stored securely via Claude Code's userConfig system — never written to your repo.
Plugin location. The plugin source is at github.com/harvv-hq/harvv-claude-plugin. Four skills live in claude-plugin/skills/ — each is a markdown file Claude reads at the start of a session for that command's context.

Source