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.

62

Quality

73%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/ads-creative-development/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Discovery

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is a strong skill description that thoroughly covers what the skill does (performance ad creative production across multiple dimensions) and when to use it (with extensive trigger terms and scenario-based conditions). The description is specific, uses natural language that users would employ, and carves out a distinct niche. The only minor concern is that it's somewhat verbose, but the detail serves the purpose of disambiguation.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions and concepts: hook patterns, format selection, video pacing, variation systems, sequential testing methodology, fatigue detection, brand-voice alignment without conversion dilution, and platform-specific creative norms.

3 / 3

Completeness

Clearly answers both 'what' (produce ad creative that converts, hook patterns, format selection, testing methodology, fatigue detection, etc.) and 'when' with explicit trigger terms and scenario-based triggers ('when a team is producing creative at scale, planning a creative test cycle, or auditing why creative is not converting').

3 / 3

Trigger Term Quality

Excellent coverage of natural terms users would say: 'ad creative', 'hook patterns', 'creative testing', 'ad variations', 'creative fatigue', 'video ads for Meta', 'TikTok creative', 'LinkedIn ad creative', 'creative refresh', and scenario-based triggers like 'auditing why creative is not converting'.

3 / 3

Distinctiveness Conflict Risk

Occupies a clear niche around performance ad creative production with distinct triggers like 'hook patterns', 'creative fatigue', 'ad video pacing', and platform-specific terms (Meta, TikTok, LinkedIn). Unlikely to conflict with general marketing or branding skills due to the performance/conversion focus.

3 / 3

Total

12

/

12

Passed

Implementation

47%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill is a comprehensive creative strategy guide with strong workflow structure and useful tactical frameworks (sequential testing, fatigue detection, variation matrices). However, it is significantly over-length, repeating key points multiple times and explaining concepts Claude already understands. The content sits in an awkward middle ground—too detailed for an overview file but duplicating the reference files it points to, undermining progressive disclosure.

Suggestions

Cut the content by 50%+: remove the opening preamble about brand vs performance creative (or reduce to 2 sentences), eliminate the closing section that restates the hook importance, and trim narrative explanations throughout to bullet-point guidance.

Move detailed content (12 hook patterns, platform norms, format selection details) entirely into the reference files and keep only a 1-2 sentence summary with link in the main SKILL.md, trusting the progressive disclosure structure.

Add concrete, copy-paste-ready ad copy examples—actual hook text, actual CTA text, an actual naming convention applied to a real example—rather than describing what good creative looks like narratively.

Provide the referenced bundle files (hook-pattern-library.md, format-decision-matrix.md, etc.) so the progressive disclosure structure actually functions.

DimensionReasoningScore

Conciseness

Extremely verbose at ~2500+ words. Extensively explains concepts Claude already knows (what brand vs performance creative is, what PDF-style basic definitions of ad formats are, what fatigue means). The opening paragraphs are pure preamble. The 'Performance vs brand creative' section belabors a distinction that could be stated in two sentences. The closing section repeats the hook importance point already made earlier. Many sections contain redundant restatements.

1 / 3

Actionability

Provides concrete hook patterns, a video pacing table, fatigue signal thresholds, naming conventions, and a variation matrix formula—all useful tactical guidance. However, there is no executable code, no actual ad copy examples ready to use, no template text to copy-paste. The worked examples are described narratively rather than shown as concrete artifacts. The guidance is specific but stops short of fully actionable output.

2 / 3

Workflow Clarity

The sequential testing methodology is clearly sequenced (hooks → bodies → CTAs → formats → evergreen rotation) with explicit advancement criteria. The fatigue detection section provides a clear decision tree with specific thresholds. The 10-consideration framework provides a structured audit checklist. Validation checkpoints are present (fatigue signals trigger refresh decisions).

3 / 3

Progressive Disclosure

References to seven separate reference files are well-organized and clearly signaled with descriptive summaries. However, no bundle files are provided, so the references are dead links. The main SKILL.md itself is monolithic—much of the inline content (hook patterns, platform norms, format details) duplicates what the reference files presumably contain, defeating the purpose of progressive disclosure.

2 / 3

Total

8

/

12

Passed

Validation

90%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

10

/

11

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.