CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

72

Quality

89%

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

78%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 body is a well-structured, tactical playbook that assumes competence and routes detail to seven real reference files with clear one-level-deep navigation. Its main weakness is mild repetition of the brand-vs-performance and hook-is-the-whole-game framings, and deferral of the most copy-paste-ready templates to references.

Suggestions

Consolidate the brand-vs-performance framing so it is stated once (intro or dedicated section) rather than re-derived across the opening, the section, and worked examples, to tighten conciseness.

Inline one complete copy-paste-ready variation matrix template (or a filled naming-convention example block) so the body is self-sufficient for the most common production task without opening a reference.

Add an explicit "validate before advancing" checkpoint in the sequential testing waterfall (e.g., a statistical-significance or minimum-spend gate) to convert the implicit advancement criteria into explicit validation steps.

DimensionReasoningScore

Conciseness

The body is tactical and assumes competence without explaining basic concepts, but repeats a few theses that could be trimmed — the brand-vs-performance distinction appears in the intro, the dedicated section, and worked examples, and the "hook is the whole game" thesis is stated verbatim in both the Hook patterns section and the Closing. It is not a 5 because of these repeated framings; it is not a 3 because the bulk is efficient and free of padding about concepts Claude already knows.

4 / 5

Actionability

It provides concrete actionable guidance — the naming convention `launch2026_meta-reel_hookA_bodyB_ctaC_v1`, asset library paths `concepts/launch-2026/hooks/`, the second-by-second pacing table, numbered hook patterns with applicability, and a 5-step testing waterfall with variant counts. It is not a 5 because the deepest copy-paste-ready templates are deferred to reference files rather than fully present inline, leaving minor gaps in the body itself.

4 / 5

Workflow Clarity

The sequential testing waterfall is a clearly numbered 5-step sequence with per-stage variant counts and winner-advancement criteria, and the fatigue section includes a detect-then-act decision tree as a feedback loop. It is not a 5 because the checkpoints are mostly implicit (advancement criteria) rather than explicit validation steps, and not a 3 because sequencing and a feedback loop are clearly present.

4 / 5

Progressive Disclosure

The body is a well-organized overview where each topic points one level deep to a real reference file via clearly signaled links ("Detail in [`references/...`]"), and a consolidated Reference files section lists all seven bundled files with one-line descriptions; all referenced paths resolve to actual files. It is not a 4 because navigation is easy and the split is clean with no nested or buried references.

5 / 5

Total

17

/

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 a strong, third-person statement of capability: it names the domain, enumerates concrete capabilities comprehensively, and provides exhaustive explicit trigger terms covering platforms and scenarios. It clearly answers both what the skill does and when to use it with minimal conflict risk.

DimensionReasoningScore

Specificity

The description lists multiple concrete capabilities comprehensively — "Hook patterns, format selection, video pacing, variation systems, sequential testing methodology, fatigue detection, brand-voice alignment without conversion dilution, and platform-specific creative norms" — matching the anchor for listing multiple specific concrete actions with comprehensive coverage. It is not a 4 because coverage is broad and concrete rather than having only minor gaps.

5 / 5

Completeness

It explicitly answers both what ("How to produce ad creative that converts at performance scale") and when via two explicit trigger clauses ("Triggers on..." and "Also triggers when..."). It is not a 4 because the "when" is fully explicit with concrete trigger phrases rather than merely present.

5 / 5

Trigger Term Quality

It includes comprehensive natural trigger terms and synonyms — "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" — plus scenario triggers. It is not a 4 because the keyword coverage is exhaustive across platforms and phrasings rather than missing a few natural terms.

5 / 5

Distinctiveness Conflict Risk

It carves a clear niche around ad creative production with platform-specific triggers (Meta, TikTok, LinkedIn) and explicit scope boundaries, minimizing conflict risk. It is not a 4 because the niche and triggers are distinct enough that overlap risk with related skills is minimal.

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.

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
rampstackco/claude-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.