Installs into .claude/skills of the current project.
Are you the author of Gads History?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/arcbaslow-gads-history)
---
name: gads-history
description: Change-event log and audit history. See what changed in the account recently; diff one saved audit against another.
user-invokable: true
argument-hint: "<customer-id> [--changes [--days N]] | [--list] | [--diff A B]"
license: MIT
metadata:
version: "0.1.0"
---
Routes to `scripts/gads_history.py`.
```
python scripts/gads_history.py --customer <id> --changes --days 7 --json
python scripts/gads_history.py --customer <id> --list --json
python scripts/gads_history.py --customer <id> --diff <ts-a> <ts-b> --json
```
Audit history is auto-populated when `gads_audit.py` is invoked with
`--save-history`. The diff output groups findings into `resolved`,
`new`, and `unchanged`.
Reports, history and notification formatting include nested findings. New demographic
findings carry campaign, dimension and bucket identity. History uses entity metadata
when present; legacy findings without it use their full message, so changed text
can appear as a resolved and new finding.
History-query failures return a redacted JSON error and exit code 3. Treat a
failed history read as missing evidence, not proof that nothing changed.
