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.

66

Quality

80%

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

77%

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

A highly actionable, well-sequenced methodology skill with concrete templates, severity calibration, and a real fallback loop. Its main weakness is token efficiency: a motivational intro and redundant scope statements repeat across sections, and the single-file structure leaves the large output template inline.

Suggestions

Trim the opening paragraph and consolidate the "Meta is the final gatekeeper" point so it appears once instead of in both Output Standards and "What This Skill Will Not Do".

Move the Phase 5 output template and the Phase 1 lookup-key tables into a reference file (e.g. references/output-format.md) referenced from the body, slimming the SKILL.md overview.

Consider a one-line "Use when" summary at the top of the body to mirror the frontmatter gap.

DimensionReasoningScore

Conciseness

Mostly efficient methodology, but the motivational opener ("Meta disapproves ads for policy reasons constantly...") and repeated "Meta is the final gatekeeper" sentiment across Output Standards and "What This Skill Will Not Do" could be tightened.

2 / 3

Actionability

Provides concrete, copy-paste-ready guidance: exact output template, a three-level severity table, lookup-key trigger tables, and specific caching rules ("3–6 policy-page fetches total, not 30–60").

3 / 3

Workflow Clarity

Clear Phase 0–6 sequence with an explicit error-recovery fallback in Phase 2 (404 → site-restricted search → log "policy URL drift") and a grounding gate ("If you can't quote, the finding isn't grounded — drop it").

3 / 3

Progressive Disclosure

Sections are well-organized with no nested references, but it is a ~200-line monolith with no bundle files; the large output template and lookup tables could be offloaded into reference files to slim the overview.

2 / 3

Total

10

/

12

Passed

Description

82%

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 specific, third-person description with concrete actions and good trigger terms, but it omits an explicit "Use when..." clause so the "when to use" half is only implied. Adding a trigger clause would raise completeness.

Suggestions

Append an explicit trigger clause, e.g. "Use when preparing to launch Meta ads, after generating ad variants, or when an ad was disapproved and you need to find the likely policy cause."

Mention the Special Ad Category handling in the description since it materially changes which policies apply.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "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" — matching the multiple-specific-actions anchor.

3 / 3

Completeness

Clearly answers "what" (pre-flight policy check, fetches policy pages, returns verdict) but has no explicit "Use when..." clause or equivalent trigger guidance, which caps completeness at 2 per the rubric.

2 / 3

Trigger Term Quality

Covers natural terms users would say — "Meta ads", "ad copy", "policy check", "policy pages" — giving good coverage of the phrases a user invokes this skill with.

3 / 3

Distinctiveness Conflict Risk

"Pre-flight policy check for Meta ads" plus the runtime-fetch methodology carves a clear niche with distinct triggers unlikely to collide with other skills.

3 / 3

Total

11

/

12

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.