CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ad-policy-check

Checks paid ads against the ad platform's rules (Meta, TikTok, Google, LinkedIn and others) and the brand's category rules: the copy, on-image or on-screen text, pictures and people. Rewrites what can be fixed honestly, adds the disclosures that are needed, and flags anything that needs a human or legal review, with one pass, fixed or flag line per ad and platform. Use alone when you already have the ad text or images and know where they will run; otherwise run the playbook for the job (e.g. make-static-ads, make-content, email-lifecycle).

Quality

93%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

92%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is an excellent example of lean, high-signal instruction writing: concrete rules, explicit rework loops, and a precise output format, with no filler. The sole material defect is progressive disclosure — it directs the loader to a `disclosure.md` file that is absent from the bundle and referenced without a path.

Suggestions

Add the referenced `disclosure.md` to the bundle (e.g. as references/disclosure.md) or correct the reference to wherever the disclosure rules actually live, since the body routes organic/email/creator content to it.

Use explicit relative paths or links when pointing to bundle and sibling files (e.g. [disclosure.md](references/disclosure.md), ../claims-gate/SKILL.md) so referenced files are clearly signaled and verifiable.

If per-platform rule sections grow further, split them into one-level-deep reference files (e.g. references/meta.md, references/tiktok.md) with clear links, keeping SKILL.md as the overview.

DimensionReasoningScore

Conciseness

The body is dense, telephonic rule statements with zero concept explanation — e.g. "no fake play buttons, close-X, notification badges, fake DMs" and a compact category table — and supplies non-obvious specifics ("melatonin is prescription-only in the UK and Australia"). Every token is a decision rule Claude could not reliably reconstruct, matching the 'lean and efficient' anchor.

5 / 5

Actionability

For an instruction-only skill the guidance is fully concrete: banned vs. approved wordings ("supports restful sleep" vs. "treats", "cures", "for insomnia"), an explicit rewrite strategy (situation framing instead of "you have…"), and a precise report format (`pass (Meta, TikTok)` · `fixed (what, why)` · `flag (risk, rule, decision needed)`). Per the rubric's scoring note, absence of code is not penalized when the guidance is this actionable.

5 / 5

Workflow Clarity

A clear five-step sequence (Category first → Per ad, per platform → Disclosures → Fix → Report) with gating rules ("Gambling, dating, political → most platforms need pre-authorisation: flag and stop"), an explicit feedback loop ("fix that; re-run the claims check and this check"), and verification discipline ("Never 'pass' a rule you could not check — say 'not checked: <rule>, <why>'"). This matches the top anchor's explicit validation and error-recovery loop.

5 / 5

Progressive Disclosure

Sections are well organized, but the body instructs "load `disclosure.md` instead" and no such file exists anywhere in the bundle (no references/, scripts/, or assets/ directories) — a dangling, unpathed reference. A missing referenced file plus bare inline mentions of sibling skills fits 'references present but not clearly signaled' (3) better than the minor-gaps profile of 4.

3 / 5

Total

18

/

20

Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: concrete, comprehensive, third-person, with an explicit and specific 'Use when' routing clause. The only weakness is modest trigger-term coverage — it lacks a few natural synonyms like "ad compliance" or "ad review" that a user might say.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — "Checks paid ads against the ad platform's rules", "Rewrites what can be fixed honestly, adds the disclosures that are needed, and flags anything that needs a human or legal review" — with named inputs (copy, on-image/on-screen text, pictures, people) and a concrete output ("one pass, fixed or flag line per ad and platform"). Coverage is comprehensive with no notable gaps, so it sits at the top anchor rather than 4.

5 / 5

Completeness

It explicitly answers both: what ("Checks... Rewrites... adds the disclosures... flags anything that needs a human or legal review") and when ("Use alone when you already have the ad text or images and know where they will run; otherwise run the playbook for the job"). The when-clause is concrete and explicit with trigger conditions, matching the top anchor rather than the weaker 'when' of 4.

5 / 5

Trigger Term Quality

It includes natural terms users would say — "paid ads", "Meta, TikTok, Google, LinkedIn", "the ad platform's rules", "copy", "disclosures" — but misses common phrasings like "ad compliance", "ad review", or "ad disapproved". Good coverage with a few natural terms missing matches the 4 anchor rather than the comprehensive synonym coverage of 5.

4 / 5

Distinctiveness Conflict Risk

It occupies a clear niche — paid-ad platform policy compliance — and explicitly routes adjacent jobs to named sibling skills ("make-static-ads, make-content, email-lifecycle"), minimizing conflict risk with ad-creation or claims-checking skills. Minimal overlap risk matches the 5 anchor.

5 / 5

Total

19

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

gooseworks-ai/goose-skills

Path

skills/marketing/ad-policy-check/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.