martech-auditlisted

# martech-audit Use this as the front door to the martech-verify bundle. It chooses and runs the existing specialist audits; it is not a fifth detector and must not invent checks of its own. ## Workflow 1. Inventory only the files the user supplied or explicitly placed in scope. Do not search unrelated directories, upload files, or paste raw records into the conversation. 2. Use filenames, extensions and headers to classify the inputs. Avoid reading or printing data rows merely to decide which audit applies. 3. Select the smallest useful set of specialists: | Input or question | Specialist | |---|---| | URLs, page locations, event values, logs, privacy concern | `pii-scan` | | Tagged/final URLs, campaign taxonomy, Unassigned traffic | `utm-lint` | | Platform conversions plus CRM/finance conversions | `conversion-reconcile` | | Ordered routing rules plus real leads | `routing-simulate` | A broad audit of a URL export may warrant both `pii-scan` and `utm-lint`. Two conversion exports may also contain URLs worth scanning, but do not expand a narrow request without explaining why the extra read-only check is relevant. 4. Resolve the selected sibling skill directory from the installed bundle, read that skill's `SKILL.md`, and follow its agent workflow. In a normal bundle installation the sibling skills sit beside this directory under `skills/`. If they are absent because this folder was copied alone, tell the user to install the full