Ads Creative Scoring

Score ad creatives before launch for Meta (Facebook/Instagram), TikTok Ads, YouTube Ads, Google Ads, and Amazon Ads policy and quality fit.

Security Scan

This is an instruction-only ad-creative scoring skill that asks for no credentials, installs, or file access and its runtime instructions are coherent with its stated purpose.

Purpose & Capability

The name/description (ads creative scoring across multiple platforms) matches the SKILL.md content: scoring rubric, QA notes, test plans, and platform-specific guidance. There are no unexpected required binaries, env vars, or config paths that would be disproportionate to the stated goal.

Instruction Scope

SKILL.md contains concrete instructions for generating objectives, variants, QA checks, and decision rules. It does not instruct the agent to read arbitrary local files, exfiltrate data, call unknown external endpoints, or access credentials. One note: the 'escalate with a structured handoff payload' instruction implies preparing data for another system but does not define any destination or transmission mechanism; that is a procedural detail rather than a hidden behavior.

Install Mechanism

No install spec and no code files — the skill is instruction-only. This minimizes filesystem and network installation risk.

Credentials

The skill declares no required environment variables, credentials, or config paths. Nothing in the SKILL.md attempts to read undeclared secrets or external keys.

Persistence & Privilege

Flags indicate default behavior (not always:true) and autonomous invocation is allowed (platform default). The skill does not request persistent system presence or modify other skills/configuration.

Assessment

This skill is instruction-only and internally consistent with its stated purpose. Before installing: 1) confirm your agent/platform does not automatically transmit the 'handoff payload' to external endpoints (the SKILL.md suggests producing such a payload but does not specify a destination); 2) treat outputs as advisory — use the skill alongside human review and official platform policy checks (this skill explicitly warns not to fabricate policy outcomes); 3) test with dummy or non-sensitive creative data first to validate behavior; 4) if you plan to wire the handoff into automation (e.g., ticketing or publishing), explicitly control and audit the destination and required credentials. No high-risk indicators were found in the provided files.

Purpose

Core mission:

• scoring rubric, revision notes, release decision

This skill is specialized for advertising workflows and should output actionable plans rather than generic advice.

When To Trigger

Use this skill when the user asks for:

• ad execution guidance tied to business outcomes
• growth decisions involving revenue, roas, cpa, or budget efficiency
• platform-level actions for: Meta (Facebook/Instagram), TikTok Ads, YouTube Ads, Google Ads, Amazon Ads
• this specific capability: scoring rubric, revision notes, release decision

High-signal keywords:

• ads, advertising, campaign, growth, revenue, profit
• roas, cpa, roi, budget, bidding, traffic, conversion, funnel
• meta, googleads, tiktokads, youtubeads, amazonads, shopifyads, dsp

Input Contract

Required:

• product_or_offer
• target_audience
• placement_scope

Optional:

• existing_assets
• brand_tone
• prohibited_claims
• creative_constraints

Output Contract

1. Creative Objective
2. Angle and Hook Set
3. Asset Specification
4. Test Variant Plan
5. Creative QA Notes

Workflow

1. Anchor creative goal to funnel stage and KPI.
2. Generate angle family and hook variants.
3. Map each angle to placement format requirements.
4. Define variant matrix and test order.
5. Add quality and compliance checkpoints.

Decision Rules

• If audience is cold, prioritize problem-agitation and proof-first hooks.
• If retargeting stage, prioritize offer clarity and urgency mechanics.
• If format limits are strict, simplify message hierarchy to one CTA.

Platform Notes

Primary scope:

• Meta (Facebook/Instagram), TikTok Ads, YouTube Ads, Google Ads, Amazon Ads

Platform behavior guidance:

• Keep recommendations channel-aware; do not collapse all channels into one generic plan.
• For Meta and TikTok Ads, prioritize creative testing cadence.
• For Google Ads and Amazon Ads, prioritize demand-capture and query/listing intent.
• For DSP/programmatic, prioritize audience control and frequency governance.

Constraints And Guardrails

• Never fabricate metrics or policy outcomes.
• Separate observed facts from assumptions.
• Use measurable language for each proposed action.
• Include at least one rollback or stop-loss condition when spend risk exists.

Failure Handling And Escalation

• If critical inputs are missing, ask for only the minimum required fields.
• If platform constraints conflict, show trade-offs and a safe default.
• If confidence is low, mark it explicitly and provide a validation checklist.
• If high-risk issues appear (policy, billing, tracking breakage), escalate with a structured handoff payload.

Code Examples

Creative Brief Example

creative_id: CR-001
angle: pain_to_outcome
hook: "Stop wasting ad budget in week one"
formats: [9:16_video, 1:1_image]

Variant Matrix

V1: hook_change
V2: CTA_change
V3: visual_proof_change

Examples

Example 1: New hook generation

Input:

• Existing creatives have high frequency fatigue
• Need fresh top-funnel hooks

Output focus:

• new angle families
• hook library
• test priorities

Example 2: Asset adaptation by placement

Input:

• One hero concept, multiple platforms
• Need format-safe variations

Output focus:

• per-platform format specs
• copy-length adaptation
• QA checklist

Example 3: Pre-launch creative scoring

Input:

• 12 creatives pending launch
• Limited review bandwidth

Output focus:

• quality scores
• reject/rework decisions
• launch candidate shortlist

Quality Checklist

• Required sections are complete and non-empty
• Trigger keywords include at least 3 registry terms
• Input and output contracts are operationally testable
• Workflow and decision rules are capability-specific
• Platform references are explicit and concrete
• At least 3 practical examples are included