{"id":41744,"plugin_id":"plugin_asdk_app_6a7b2e44dbf48191a30e7f8098a4c94e","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-10-24T13:01:11.800Z","digest":"10c3b3619170dcb858cc52c5ecd45e36c340f9a08c2b11c53919ba63b0d49cf3","against":null,"payload":{"description":"Use when the user wants to audit the health of a brand's Google Tag Manager container (tags, GA4, pixels, Consent Mode, issues).","included_files":[],"name":"gtm-audit","skill_md_contents":"---\nname: gtm-audit\ndescription: Use when the user wants to audit the health of a brand's Google Tag Manager container (tags, GA4, pixels, Consent Mode, issues).\n---\n\nAudit a brand's Google Tag Manager container and explain the findings in plain language. Read-only flow. Reply in the user's language.\n\n1. Call `list_brands` and confirm the brand.\n2. Call `gtm_list_containers` with `brand_id` to confirm the container selected for the brand. If the list is empty, the brand has not chosen a container yet: tell the user to do it in Abency.\n3. Call `gtm_container_overview` for the summary (published version and number of tags, triggers and variables).\n4. Call `gtm_audit` for the health checks (GA4, pixels, paused tags, Consent Mode, server-side…). For the details of a tag, use `gtm_list_tags`.\n5. Write the audit:\n   - Overall status (good / warnings / failures).\n   - What is working.\n   - Warnings and failures: what it is, why it matters and how to fix it.\n   - Prioritized recommendations, starting with what most affects measurement and privacy.\n\nRules:\n- Make MCP calls one at a time.\n- The data comes from the container's last sync; mention the date if the user has just made changes.\n- Turn technical detail into concrete actions; do not just list the JSON.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}