---
description: Read-only GA4 property audit with a scored report, analyst caveats and a change list
argument-hint: [GA4 property ID or snapshot file or focus area]
---

Use the ga4-audit skill for this task: $ARGUMENTS

Read martech-context/ first if it exists, especially stack.md, decisions.md and the tracking plan.
If $ARGUMENTS is empty or vague, ask for the GA4 property ID and how you may read it: the official GA4 MCP server, the snapshot script with the user's own read-only credentials, or exports from the GA4 interface.
Also ask for the expected hostnames, payment and sign-in providers, which Google Ads accounts should be linked, and whether Google Ads imports or a warehouse depend on this property.
Follow the skill's procedure in order and finish with its acceptance checks.
Stay read-only. Never create, edit, archive, link, change a filter's state or write an annotation in GA4, and never start the GA4 MCP server with --allow-write.
Never ask for tokens, API secrets, IP address lists or user emails in chat. Screenshots are cropped first: no secret values, IP addresses or people's names.
Work in an audit folder in the user's project, never inside the skill folder.
Ask for approval before any test that submits a form, places an order or clicks a consent banner on a live site.
Hand back the scored report with its coverage, the analyst caveats, the inventories and a change list a person with the named role can apply.

If the ga4-audit skill is not installed, install it with: npx skills add https://www.martechdevs.com --skill ga4-audit -a claude-code