CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ads-creative-development

How to produce ad creative that converts at performance scale. Hook patterns, format selection, video pacing, variation systems, sequential testing methodology, fatigue detection, brand-voice alignment without conversion dilution, and platform-specific creative norms. Triggers on ad creative, ad design, hook patterns, ad video pacing, creative testing, ad variations, creative refresh, creative fatigue, refresh ad creative, video ads for Meta, TikTok creative, LinkedIn ad creative, ad asset library. Also triggers when a team is producing creative at scale, planning a creative test cycle, or auditing why creative is not converting.

74

Quality

93%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

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

A strong, dense tactical playbook: concrete thresholds and worked examples in every section, a clearly sequenced testing waterfall with an explicit decision tree, and exemplary progressive disclosure across seven real one-level-deep references. The main costs are duplicated hook rhetoric between the Hook patterns and Closing sections, motivational padding in the Closing, and winner-advancement criteria deferred to the reference rather than stated inline.

Suggestions

Deduplicate the 'the hook is the whole game' passage, which appears nearly verbatim in both 'Hook patterns' and 'Closing' — state it once and cross-reference.

Inline the winner-advancement criteria for the testing waterfall (what makes a hook a 'winner': metric and threshold) so the sequence's checkpoints are explicit without opening the reference.

Trim the Closing's effort-distribution paragraphs to a single actionable rule; the 60/40 vs 90/10 rhetoric duplicates the hook-priority guidance already given.

DimensionReasoningScore

Conciseness

The body is mostly tight, tactical prose with short declarative sentences and no explanation of concepts Claude already knows, but there is trimmable redundancy: the "the hook is the whole game / a user who scrolled past the first second has already decided" passage appears nearly verbatim in both the Hook patterns section and the Closing, and "Same voice. Different structure." repeats across the worked examples. The Closing's effort-distribution paragraphs ("The team that puts 90% of its effort into hooks...") are motivational rather than instructional. Anti-drift check: score 5 requires every token to earn its place, which the duplication and rhetoric disqualify; score 3 would require more pervasive padding than is present.

4 / 5

Actionability

Guidance is concrete throughout: twelve named hook patterns each with example copy and a fit condition, a second-by-second 15s pacing table, a decomposition formula (1 concept × 5 hooks × 4 bodies × 3 CTAs × 2 formats), a copy-ready naming convention ("launch2026_meta-reel_hookA_bodyB_ctaC_v1"), a five-stage testing waterfall with per-stage variant counts, numeric fatigue thresholds (frequency 4–5/week, CTR decline 30%+, refresh cadence by spend tier), and platform constraints (30-character headlines, 15 RSA slots, 9:16 aspect ratios). For an instruction-only skill, the specific guidance covers the common cases; the rubric does not penalize the absence of code. Anti-drift check: score 4 would require minor gaps in the concrete guidance, but thresholds, counts, and worked examples are present for every section.

5 / 5

Workflow Clarity

The sequential testing waterfall is a clearly sequenced five-step process with per-stage variant counts and stated advancement rules ("Top 2 to 3 hooks each get 5 to 10 body variants"), the fatigue section has an explicit decision tree (metrics strong + frequency climbing → ship variants; metrics dropping → retire concept), and the 10-consideration framework defines three explicit outcomes (ship, revise, stop). The gap that keeps this below 5: the winner-advancement criteria and stage durations are deferred to the reference playbook rather than stated inline, so the checkpoints are named but their thresholds are implicit in the body. Anti-drift check: score 5 requires explicit validation steps with feedback loops fully specified, which the deferred criteria disqualify; score 3 would require the sequence itself to have gaps, which it does not.

4 / 5

Progressive Disclosure

The body is a well-sectioned overview where every topic defers its detail to one of seven one-level-deep reference files, all of which exist and contain substantive content (verified: 48–157 lines each, e.g. hook-pattern-library.md has per-pattern what/when/anti-pattern/examples; testing-cadence-playbook.md has per-stage goals). References are well-signaled twice — inline at each section ("Detail in references/...") and in a consolidated Reference files section with one-line descriptions — making navigation easy. Anti-drift check: score 4 would require minor organization gaps or unclear signaling, but the inline-plus-index pattern and consistent link format leave none.

5 / 5

Total

18

/

20

Passed

Description

100%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 exemplary: it names the domain, enumerates eight concrete capability areas, provides an extensive and redundant set of natural trigger terms including platform-specific variants, and closes with explicit scenario-based "when" triggers. No vague fluff, no over-claims, third-person compatible voice throughout.

DimensionReasoningScore

Specificity

The description lists multiple specific concrete capabilities: "Hook patterns, format selection, video pacing, variation systems, sequential testing methodology, fatigue detection, brand-voice alignment without conversion dilution, and platform-specific creative norms" — comprehensive coverage of the performance-creative domain with no vague filler. Anti-drift check: score 4 would require minor gaps in coverage, but the capability list spans production, testing, and diagnosis completely.

5 / 5

Completeness

Both questions are explicitly answered: the "what" is the full capability list under "How to produce ad creative that converts at performance scale," and the "when" is explicit via "Triggers on... Also triggers when a team is producing creative at scale, planning a creative test cycle, or auditing why creative is not converting" — concrete trigger phrases equivalent to a "Use when..." clause. Anti-drift check: score 4 would require the "when" to be less explicit, but it is not.

5 / 5

Trigger Term Quality

Trigger coverage is comprehensive with synonyms and platform-specific phrasings users would naturally say: "ad creative, ad design, hook patterns, ad video pacing, creative testing, ad variations, creative refresh, creative fatigue, refresh ad creative, video ads for Meta, TikTok creative, LinkedIn ad creative, ad asset library." Anti-drift check: score 4 would mean a few natural terms missing, but the list includes both short-form and long-form variants of each trigger.

5 / 5

Distinctiveness Conflict Risk

The description carves a clear niche (performance ad creative production) with distinct triggers that would not fire for adjacent skills like paid media strategy or analytics; terms like "hook patterns," "creative fatigue," and "refresh ad creative" are specific to this skill. Anti-drift check: score 4 would indicate minor overlap risk with closely related skills, but every trigger term is creative-production-specific rather than strategy or measurement vocabulary.

5 / 5

Total

20

/

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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

rampstackco/claude-skills

Path

skills/ads-creative-development/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.