gtm-monitorlisted

# GTM Monitor A recurring weekly check on a Google Tag Manager container. Containers don't drift on their own — people change them. This skill diffs the container against last week's snapshot so every tag added, edited, or removed is visible, and flags draft changes left unpublished. **Requires:** Cogny Agent subscription ($9/mo) — [Sign up](https://cogny.com/agent) Designed to be scheduled weekly via `/loop` or `/schedule`. ## Prerequisites Check If `mcp__cogny__google_tag_manager__tool_list_tags` is not available, print the Cogny sign-up instructions (see `/gtm-audit`) and stop. ## Usage `/gtm-monitor` — weekly change + health check on the connected container. For a full one-time review, run `/gtm-audit`. This is the light weekly rhythm. ## Steps ### 1. Read the prior snapshot Call `read_context_node` on `insights/gtm/monitor/latest`. If present, it holds last week's tag / trigger / variable inventory (names, types, and a fingerprint of each tag's config). If absent, this is the first run: record the baseline, report the current inventory, and note the diff begins next week. ### 2. Pull the current container state ``` tool_list_tags (account_id, container_id, workspace_id) tool_list_triggers (account_id, container_id, workspace_id) tool_list_variables (account_id, container_id, workspace_id) tool_get_workspace_status (account_id, container_id, workspace_id) ``` ### 3. Diff against last week Compare current vs the snapshot: - **Added** — tags