CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ad-policy-compliance

Checks ad creative and landing pages against platform advertising policies for Google, Meta, LinkedIn, TikTok, and Reddit. Use when pre-checking ads for policy compliance, fixing rejected ads, reviewing restricted content, or navigating industry-specific ad rules.

Quality

79%

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/ad-policy-compliance/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%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 content is highly actionable reference material with concrete fixes and worked examples, and the pre-submission workflow is clear. Its main weaknesses are inlined bulk (no progressive disclosure — platform manuals should be separate reference files), duplicated checklist content, and a promotional footer that wastes tokens.

Suggestions

Split each platform's policy checklist (Google, Meta, LinkedIn, TikTok, Reddit) and the industry-specific rules into separate files under references/ (e.g. references/google-ads.md), keeping SKILL.md as a concise overview with clearly signaled one-level-deep links.

Remove the promotional 'About this skill' footer and the ad-performance tips ("less polished = better", text-in-image delivery advice) — they consume tokens without adding policy-compliance value.

Replace the separate pre-launch checklist template with a pointer to the universal checks section (or vice versa) to eliminate the duplicated checklist, and add an explicit appeal→re-review feedback loop to the rejection-fix workflow.

DimensionReasoningScore

Conciseness

The body is mostly dense, platform-specific policy data Claude does not reliably know, but it includes unnecessary padding: a promotional 'About this skill' footer with marketing links, a pre-launch checklist template that largely duplicates the earlier universal checks, and performance tips ("Native-feeling content performs best", "Less text = more delivery") that are ad advice rather than policy guidance.

3 / 5

Actionability

Concrete, executable guidance throughout: violation→example→fix tables, approved/rejected copy rewrites ("Are you overweight?" → "Many people manage their weight with..."), appeal methods per platform, and a worked financial-services review with a verdict. Minor gaps — unsourced appeal 'success rate' percentages and vague directives like "comply with local regulations" — keep it below fully copy-paste-ready.

4 / 5

Workflow Clarity

The pre-submission workflow is clearly sequenced by check category (copy → targeting → landing page → legal), the checklist template ends in an explicit APPROVED/BLOCKED gate, and the worked example shows PASS/WARNINGS/REQUIRED FIXES. Not a 5 because the appeal→re-review feedback loop is only implicit and per-platform scans are presented as static checklists rather than an ordered procedure.

4 / 5

Progressive Disclosure

Section headers are clear and well-ordered, but the file is ~570 lines with all five platform-specific policy manuals, industry rules, trademark tables, and appeal data inlined in SKILL.md and no references/ files at all — content that clearly belongs in separate one-level-deep reference files is inline, matching the anchor 3 pattern rather than a well-split structure.

3 / 5

Total

14

/

20

Passed

Description

87%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: it states concrete capabilities in third person, names all five target platforms, and includes an explicit 'Use when' clause covering the main usage triggers. The only shortcoming is that it under-sells some capabilities (trademark rules, industry-specific rules, rejection fixes) that the body delivers.

DimensionReasoningScore

Specificity

"Checks ad creative and landing pages against platform advertising policies for Google, Meta, LinkedIn, TikTok, and Reddit" names concrete actions and objects across five platforms, but omits capabilities the body covers (rejection fixes, trademark rules, industry-specific rules), matching the 'several specific actions; minor gaps' anchor rather than comprehensive coverage.

4 / 5

Completeness

Explicitly answers both 'what' (checks ad creative and landing pages against policies for five named platforms) and 'when' ("Use when pre-checking ads for policy compliance, fixing rejected ads, reviewing restricted content, or navigating industry-specific ad rules") with concrete trigger phrases, in third-person voice.

5 / 5

Trigger Term Quality

Natural phrases users would say are present ("pre-checking ads", "fixing rejected ads", "policy compliance", "restricted content"), but common variations like "ad disapproved" or "ad appeal" are missing, so coverage is good rather than comprehensive.

4 / 5

Distinctiveness Conflict Risk

The ad-policy-compliance niche is clearly distinct — specific platforms, specific artifacts (ad creative, landing pages), and specific scenarios (rejected ads, restricted content) — with minimal risk of triggering for an unrelated skill.

5 / 5

Total

18

/

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

skill_md_line_count

SKILL.md is long (572 lines); consider splitting into references/ and linking

Warning

Total

15

/

16

Passed

Repository

Synter-Media-AI/free-skills

Path

skills/ad-policy-compliance/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.