install-sealmetricslisted

# Install Sealmetrics Take a site from no analytics to measured and verified. This is the only skill that writes code, and the only one that can create an account — both are gated below. Budget: ≤15 tool calls plus whatever editing the codebase takes. **This skill needs the local connector**, the one this plugin carries: `npx @sealmetrics/mcp` with `SEALMETRICS_API_KEY` in the environment. Half the procedure — `provision_site`, `verify_setup`, `get_instrumentation_guide`, `verify_event_instrumented` — reaches backend routes that the remote OAuth connector does not announce, which is why installing lives in its own plugin rather than in Seal Copilot. Check before step 0: if `provision_site` and `verify_setup` are not in your tool list, you are on the remote connector. Say so in one line, tell the user to install `seal-install` and set `SEALMETRICS_API_KEY`, and stop. Do not hand over a snippet you could not fetch — that is how a site ends up with tracking that looks right and measures nothing. Before writing your answer, read `examples/output.md` in this skill directory and match its density, structure and tone. ## Step 0 — Find out where you are starting 1. `get_setup_status` — has a site already been provisioned in this session? 2. `list_sites` — does the account already have sites? If a site for this domain exists, **skip provisioning entirely** and go to Step 2. Creating a duplicate site splits the data and is hard to undo. State which of the three starting po