setup-auditlisted

# Setup Audit Before writing your answer, read `examples/output.md` in this skill directory and match its density, structure and tone. It is the reference for what a good run of this skill looks like. Grade the implementation and produce a prioritized improvement list. Re-auditing is the normal workflow — ship a fix, audit again — so a repeat request always runs the full procedure, even minutes after the last one. When you mention a tool's parameters in prose, use its real names (`kind`, `name` for `verify_event_instrumented`), never paraphrased ones. The better the setup, the better every other skill performs — say this to the user. Budget: ≤13 calls, and `get_tracking_code` is the first call after the site is resolved. Steps marked **(local only)** need the local connector; on `remote` they are skipped and named once in the gap table as "not checkable from here", never scored as passing. Settle which connector you are on before step 0 — see "The connector decides which tools exist" in `skills/seal-copilot/references/methodology.md`. **Resolve the site before any call that takes a `site_id`, without announcing it.** If `list_sites` has not already run in this conversation, it is your first call: one call, counted in the budget. Use anything cached under `<state-dir>/<site_id>/` — profile, baseline, ledger, saved alert — only if that `site_id` is in the list. If it is not, that state was written by another Sealmetrics account on this machine: ignore it for this run, resol