CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ads-competitor

Research competitor paid-ad presence, messaging, creative, formats, landing pages, keyword and auction signals, transparent ad libraries, and strategic gaps across supported platforms. Use for competitor ads, ad libraries, ad spy, competitive PPC analysis, competitor creative, Google Ads Transparency, Meta Ad Library, or paid-media competitor research.

72

Quality

91%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

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.

A lean, well-sequenced research workflow with strong guardrails and no wasted tokens. Its main weakness is actionability: the sourcing step names a class of sources rather than the specific transparency libraries, and the synthesis and return steps lack a concrete method or output format.

Suggestions

Name the specific transparency libraries in the body (e.g., Google Ads Transparency Center and Meta Ad Library, with their URLs) so the sourcing step in step 2 is directly executable rather than a class of sources.

Add an explicit validation step before returning, e.g., verify every recorded source URL is accessible and that each reported claim maps to a captured source record, so step 6's 'evidence-backed' requirement has a concrete check.

Specify the output shape for step 6, e.g., a table schema for source records using the fields from step 3 plus a structured findings section for opportunities, risks, and experiments.

DimensionReasoningScore

Conciseness

The body is six directive steps plus two short guardrail statements in roughly 20 lines with zero padding or explanation of concepts Claude already knows ('Record capture date, platform, placement, observable creative/message, landing destination, and source URL'). Every token earns its place, matching the 5 anchor's lean pattern; it is not 4 because there is no over-explanation to trim.

5 / 5

Actionability

Concrete guidance exists ('Record capture date, platform, placement, observable creative/message, landing destination, and source URL'), but 'Use official transparency libraries, public ads, auction data supplied by the operator, and other terms-compliant sources' never names which libraries, and 'Cluster durable themes, formats, offers, funnel paths, and gaps' gives no method or output shape. This is the 3 anchor's 'some concrete guidance but incomplete'; not 4 because for a skill whose core tool is the ad library, leaving the specific libraries unstated is a key missing detail, not a minor gap.

3 / 5

Workflow Clarity

Steps 1-6 form a clear sequence (confirm scope, gather from sources, capture, separate fact from inference, synthesize, return deliverables), and steps 4 and 6 act as checkpoints ('never present estimates as account facts'; 'Return evidence-backed opportunities, risks, experiments, and source records'). This matches the 4 anchor's 'clear sequence with most checkpoints present; minor validation gaps'; not 5 because there is no explicit verify/retry validation step.

4 / 5

Progressive Disclosure

The skill is under 50 lines, has no bundle files (no references/, scripts/, or assets/ exist), and inlines nothing that belongs in a separate file; the body is a single titled process with separated guardrail notes. Per the simple-skill guideline it scores 5; not 4 because there are no organization gaps 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 exemplar: it states concrete, comprehensive capabilities in third person, provides an explicit 'Use for' trigger list with natural synonyms and platform names, and occupies a distinct niche with minimal conflict risk.

DimensionReasoningScore

Specificity

'Research competitor paid-ad presence, messaging, creative, formats, landing pages, keyword and auction signals, transparent ad libraries, and strategic gaps across supported platforms' enumerates eight-plus concrete research targets with comprehensive domain coverage, matching the 5 anchor's multiple specific concrete actions; not 4 because there are no coverage gaps.

5 / 5

Completeness

It explicitly answers what ('Research competitor paid-ad presence, messaging, creative, formats, landing pages...') and when ('Use for competitor ads, ad libraries, ad spy...') with concrete trigger phrases, mirroring the 5 anchor's structure exactly; not 4 because the 'when' clause is fully explicit rather than improvable.

5 / 5

Trigger Term Quality

'Use for competitor ads, ad libraries, ad spy, competitive PPC analysis, competitor creative, Google Ads Transparency, Meta Ad Library, or paid-media competitor research' covers the natural phrasings users would say plus platform-specific synonyms, comparable to the 5 anchor's synonym-complete list; not 4 because no common variation (ad spy tools, PPC, library names) is missing.

5 / 5

Distinctiveness Conflict Risk

The paid-ad competitor intelligence niche with platform-named triggers ('Google Ads Transparency, Meta Ad Library') is clearly distinguishable from generic marketing, SEO, or research skills with minimal conflict risk, matching the 5 anchor's clear-niche pattern; not 4 because the overlap with adjacent skills is negligible.

5 / 5

Total

20

/

20

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

AgriciDaniel/claude-ads

Path

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