Individual skill
change-history-checker
Query Google Ads account change history up to 90 days back using the `change_status` resource (vs the 30-day limit of `change_event`). Auto-invoke when user says "what changed in [account]", "change history for [account]", "what did I do in [month]", "audit account changes", or "review optimization history".
change-history-checker/SKILL.md
Source commit 90f0e419f2d820789d5e50eee1237ab9fd14dfc6
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 11, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 80
- Repository last updated
- Aug 25, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- ai-agents Repository topic
- ai-skills Repository topic
- claude-code Repository topic
- google-ads Repository topic
- google-ads-api Repository topic
- ppc Repository topic
- ppc-automation Repository topic
- security Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
README.mddoc · 2,729 bytesSKILL.mdcore · 5,794 bytesSKILL.mdcore · 5,794 bytesexamples.mddoc · 5,307 bytesreferences/history-windows.mddoc · 7,226 bytesrules.mddoc · 7,003 bytesscripts/check_change_history.pyruns · 6,937 bytes
Read excerpt
# Change History Checker
Owns one workflow: answer "what changed in this account?" from the API —
grouped what-changed-when counts up to 90 days back (the API's hard cap for
`change_status`), with an explicit escalation ladder for the questions the
counts can't answer (who did it, what the old values were, anything older).
The judgment layer — routine vs investigate, the attribution ladder, flag
decisions — is [`rules.md`](rules.md). The two-resource window semantics,
API-enforced query rules, and standalone patterns are
[`references/history-windows.md`](references/history-windows.md).
## Prerequisites