Menu

Individual skill

account-diagnostic

0upvotes

42-point Google Ads account inspection (44 with the local-service preset) — discrete GREEN/YELLOW/RED checks across 14 categories (conversion tracking, pacing, impression share, quality score, search-term waste, keyword health, creative, RSA assets, account settings, PMAX config, negative keywords, placement safety, extensions, video & Demand Gen automation), scored into one overall verdict with estimated monthly waste, then triaged per rules.md. Auto-invoke when user says 'run diagnostic', 'inspect account', '40-point inspection', 'diagnostic for [account]', 'audit [account]', or 'account health check'.

account-diagnostic/SKILL.md

Read pinned source

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.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# 42-Point Account Diagnostic

Like a mechanic's multi-point vehicle inspection, but for Google Ads
accounts. Every check lands on an explicit GREEN/YELLOW/RED verdict with a
finding, a dollar impact where one can be estimated, and a "do this" action
line — no narrative to interpret.

One operator owns the workflow end to end: run the inspection → present the
scored report → triage the findings (`rules.md`) → route each actionable
finding to its fix skill. The diagnostic itself never changes an account.

*Naming note: 42 checks on a standard run; the local-service preset adds two
for 44. "40-point inspection" survives as a trigger because the instrument
grew from its original 40 core checks.*
Back to top