CtrlK
BlogDocsLog inGet started
Tessl Logo

ai-ugc-ads

When the user wants to create UGC ad campaigns, recruit UGC creators, generate AI UGC content, or scale with user-generated content. Also use when the user mentions 'UGC,' 'user-generated content,' 'creator ads,' 'Spark Ads,' 'whitelisting,' 'AI UGC,' 'Arcads,' 'Creatify,' 'creator brief,' or 'UGC testing.' This skill covers the UGC growth framework from creator recruitment through AI-powered scaling. Do NOT use for technical implementation, code review, or software architecture.

78

Quality

72%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./packages/skills-catalog/skills/(gtm)/ai-ugc-ads/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Discovery

89%

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 with excellent trigger term coverage and clear completeness, explicitly stating both what the skill does and when to use it. The main weakness is that the 'what' portion could be more specific about concrete actions rather than high-level capabilities. The explicit exclusion clause is a nice touch that further reduces conflict risk.

Suggestions

Add more specific concrete actions to improve specificity, e.g., 'write creator briefs, structure Spark Ads whitelisting workflows, design A/B testing matrices for UGC creatives, plan creator outreach sequences.'

DimensionReasoningScore

Specificity

The description names the domain (UGC ad campaigns) and some actions like 'recruit UGC creators,' 'generate AI UGC content,' and 'scale with user-generated content,' but these are somewhat high-level rather than listing multiple concrete, specific actions like a score of 3 would require (e.g., 'write creator briefs, set up Spark Ads whitelisting, build testing frameworks').

2 / 3

Completeness

The description clearly answers both 'what' (create UGC ad campaigns, recruit creators, generate AI UGC content, scale with UGC) and 'when' with an explicit 'Use when' clause listing specific trigger terms. It also includes a helpful exclusion clause ('Do NOT use for technical implementation...').

3 / 3

Trigger Term Quality

Excellent coverage of natural trigger terms including 'UGC,' 'user-generated content,' 'creator ads,' 'Spark Ads,' 'whitelisting,' 'AI UGC,' 'Arcads,' 'Creatify,' 'creator brief,' and 'UGC testing.' These are terms users would naturally use when seeking help with UGC campaigns.

3 / 3

Distinctiveness Conflict Risk

The description carves out a very clear niche around UGC marketing with specific platform names (Arcads, Creatify) and explicit exclusions for technical/code tasks, making it highly unlikely to conflict with other skills.

3 / 3

Total

11

/

12

Passed

Implementation

55%

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

The skill is exceptionally actionable with concrete frameworks, specific numbers, and clear workflows that would genuinely help execute UGC campaigns. However, it is massively over-length and monolithic — cramming what should be 5-6 separate reference files into a single document. The token cost is very high, with extensive tables of benchmarks, rate cards, and platform specs that could be split into referenced files, significantly reducing the context window burden.

Suggestions

Split into a concise SKILL.md overview (under 100 lines) with references to separate files: CREATOR-RATES.md, PLATFORM-SPECS.md, AD-FORMATS.md, TESTING-FRAMEWORK.md, BENCHMARKS.md, AI-TOOLS.md

Remove information Claude already knows or can infer: general platform descriptions, basic marketing concepts, and explanations like what Spark Ads are or how whitelisting works

Consolidate the 8 ad format templates into a referenced file and keep only the Format Selection Guide table in the main skill

Remove time-sensitive benchmark data (specific CPM/CTR numbers, tool pricing) or move to a clearly dated reference file that can be updated independently

DimensionReasoningScore

Conciseness

This is extremely verbose at 400+ lines. It includes extensive benchmark tables, rate cards, platform specs, and detailed breakdowns that Claude already knows or could infer. Much of this content (e.g., explaining what UGC is, platform specs, general marketing concepts) doesn't add unique actionable value and could be condensed by 60-70%.

1 / 3

Actionability

The skill provides highly concrete, specific guidance throughout: exact budget ranges, specific DM templates, step-by-step Spark Ads setup, precise kill criteria with thresholds, the 3x3x3 testing framework with daily budgets, and a complete brief template. Nearly every section gives copy-paste-ready frameworks and specific numbers.

3 / 3

Workflow Clarity

Multi-step processes are clearly sequenced with explicit validation checkpoints. The organic-first flywheel has clear stages with timing. The testing protocol has phased steps (Hook Test → Body Test → CTA Test → Scale) with specific metrics and kill criteria at each stage. The kill/scale rules table provides explicit decision points.

3 / 3

Progressive Disclosure

This is a monolithic wall of text with 11 major sections all inline. There are no references to separate files for detailed content like the rate benchmarks, platform specs, ad format templates, or tool comparisons — all of which would be ideal candidates for separate reference files. The Related Skills section at the end references other skills but the body itself has no progressive structure.

1 / 3

Total

8

/

12

Passed

Validation

100%

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

Validation11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository
tech-leads-club/agent-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.