CtrlK
BlogDocsLog inGet started
Tessl Logo

meta-ad-policy-checker

Pre-flight policy check for Meta ads. Takes ad copy plus advertiser context, resolves and fetches the relevant Meta transparency-center policy pages at runtime, and returns a Pass / Fix Required / Block verdict with cited findings and rewrites.

63

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/ads/composites/meta-ad-policy-checker/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 highly actionable and well-sequenced with explicit checkpoints, but carries some redundant prose and repeated statements that could be trimmed for token efficiency.

Suggestions

Trim the motivational intro and 'Core principle' paragraph, or fold them into a single concise sentence, since Claude can infer the rationale.

Deduplicate the 'Meta is the final gatekeeper' point — state it once in 'What This Skill Will Not Do' and remove the restatement from Output Standards.

Add an explicit re-validation loop for rewrites (e.g., re-run the check on a suggested rewrite to confirm the verdict improves) to close the workflow validation gap.

DimensionReasoningScore

Conciseness

Mostly efficient methodology and tables, but padded by motivational intro prose, a 'Core principle' paragraph restating the methodology/source split, and a repeated 'Meta is the final gatekeeper' statement across Output Standards and What This Skill Will Not Do.

3 / 5

Actionability

Provides copy-paste-ready guidance: a verbatim output template with field-by-field structure, concrete fetch URL, content-driven and category-driven lookup tables, a severity model, and a quantified caching rule — specific examples cover the common cases.

5 / 5

Workflow Clarity

Clear 6-phase sequence with an explicit fetch fallback checkpoint (404 → site-restricted search → log 'policy URL drift'), satisfying the batch/destructive cap; minor validation gaps remain on the reasoning output (no re-run-if-rewrite-still-flagged loop).

4 / 5

Progressive Disclosure

Well-organized with clear section headers and a justified single-file design (the maintenance note explains the slug list is inline for single-file updates); no external references are needed, though at ~199 lines some peripheral content could be split.

4 / 5

Total

16

/

20

Passed

Description

75%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.

The description is specific, concrete, and clearly distinct, but it lacks an explicit 'Use when...' trigger clause, capping completeness at 3 and leaving a few natural trigger terms unspecified.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use before launching or submitting any Meta ad, or when reviewing a disapproved ad.'

Include more natural user-facing trigger terms such as 'ad approval', 'disapproval', 'ad review', or 'Facebook ads'.

Consider naming the Special Ad Category handling in the description to further sharpen distinctiveness.

DimensionReasoningScore

Specificity

Names multiple concrete actions across the full pipeline — 'resolves and fetches the relevant Meta transparency-center policy pages at runtime' and 'returns a Pass / Fix Required / Block verdict with cited findings and rewrites' — giving comprehensive coverage rather than a few actions.

5 / 5

Completeness

The 'what' is clear and concrete, but there is no explicit 'Use when...' trigger clause; the 'when' is only weakly implied by 'Pre-flight', which per the rubric caps completeness at 3.

3 / 5

Trigger Term Quality

Includes natural terms ('Meta ads', 'ad copy', 'policy check') but omits common user phrasings like 'ad approval', 'disapproval', 'ad review', or 'Facebook ads', leaving a few natural synonyms missing.

4 / 5

Distinctiveness Conflict Risk

Targets a sharp niche — 'Meta ads' and 'Meta transparency-center policy pages' — with distinct triggers and minimal overlap risk against other marketing/ad skills.

5 / 5

Total

17

/

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.

Validation15 / 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
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.