AF ad-creative
When the user wants to generate, iterate, or scale ad creative — headlines, descriptions, primary text, or full ad variations — for any paid advertising platform. Also use when the user mentions 'ad copy variations,' 'ad creative,' 'generate headlines,' 'RSA headlines,' 'bulk ad copy,' 'ad iterations,' 'creative testing,' 'ad performance optimization,' 'write me some ads,' 'Facebook ad copy,' 'Google ad headlines,' 'LinkedIn ad text,' or 'I need more ad variations.' Use this whenever someone needs to produce ad copy at scale or iterate on existing ads. For campaign strategy and targeting, see paid-ads. For landing page copy, see copywriting.
When the user wants to generate, iterate, or scale ad creative — headlines, descriptions, primary text, or full ad variations — for any paid advertising…
As a process F 47/100 · Will not run — References files that are not bundled: ../../tools/REGISTRY.md, ../../tools/integrations/google-ads.md, ../../tools/integrations/meta-ads.md
How to improve
- The text references files that are not there: add them or drop the references.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 3. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: ../../tools/REGISTRY.md - warning
missing-refreference to a missing file: ../../tools/integrations/google-ads.md - warning
missing-refreference to a missing file: ../../tools/integrations/meta-ads.md - warning
missing-refreference to a missing file: ../../tools/integrations/linkedin-ads.md - warning
missing-refreference to a missing file: ../../tools/integrations/tiktok-ads.md
Process rating: all ten parameters 47/100
- 0Tools and files. 5 referenced file(s) missing: ../../tools/REGISTRY.md, ../../tools/integrations/google-ads.md, ../../tools/integrations/meta-ads.md
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 4 mutating operations with no state check
- 60Result and completion. Output format stated, no completion criterion
- 70When it triggers. States when to use, but not when not to
- 100Steps. 80 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3195 tokens
- low 12 top-level sections: this looks like several domains in one skill
- low No test case covers injection arriving through data
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +1No license
- +2Single-language instructions
- +3Description length 649: enough signal without eating the budget
- +4Structure: 42 headings
- +3Step-by-step instructions: 80 items
- +3Output format is stated explicitly
- +4Has examples (6 code blocks)
- +4Reference files are cited in the instructions (2 of 2)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 79.