AB ad-platform-tracker
Use this skill whenever the user needs to track, analyze, or respond to advertising platform changes across Meta (Facebook/Instagram), Google Ads, or competitor intelligence. Trigger for any of these requests: Meta algorithm updates, Andromeda implications, Google Ads policy changes, Performance Max updates, privacy/compliance tracking (GDPR, CCPA, iOS), competitor ad analysis, campaign impact assessment, ad policy audits, regulatory compliance checks, platform feature rollouts, algorithm behavior changes, creative strategy updates from platform shifts, competitor ad library scraping, or any question like "what changed on Meta/Google?", "how does X update affect my campaigns?", "is my account compliant?", "what are competitors running?". Always use this skill — do not rely on training memory for fast-changing platform details.
As a process B 69/100 · Nearly there — weak spots: inputs and preconditions, consistency, progress reporting
How to improve
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 6. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 69/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 40Consistency. Frontmatter name (ad-platform-tracker) differs from the folder (ad-platform-tracker-skill)
- 60Result and completion. Output format stated, no completion criterion
- 60Failures and branches. 2 branches
- 70When it triggers. States when to use, but not when not to
- 100Tools and files. No external tools needed
- 100Steps. 56 steps
- 100Execution cost. Instruction body is 1636 tokens
- 100Running it twice. No mutating operations
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +4Description does not say when NOT to use the skill (false activations)
- +3Description length 838: 120–800 characters recommended
- +1No license
- +2Single-language instructions
- +5Description quotes 4 example trigger phrases
- +4Structure: 13 headings
- +3Step-by-step instructions: 56 items
- +3Output format is stated explicitly
- +4Has examples (4 code blocks)
- +4Reference files are cited in the instructions (4 of 4)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 93.