property-explorerlisted

# Property Explorer 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. Discover the analytical surface area of a specific Sealmetrics account so every later skill knows what to use. Run **once per site** at engagement start, then again after major tracking changes. Budget: ≤15 calls — higher than other skills because the value compounds across every future run. **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, resolve the site from the list, asking if there are several, and never delete the other account's files. Rules in `skills/seal-copilot/references/state-schema.md`, "A cached site belongs to one connection". ## Step 1 — List all property keys across all tables ``` list_property_keys(table=conversions) list_property_keys(table=microconversions) list_property_keys(table=conversion_items) ``` **(local only)** Also run `list_segments` — saved segments are part of the analytical surface and belong in the inventory. For up to three that look business-rele