CtrlK
BlogDocsLog inGet started
Tessl Logo

ads

When the user wants help with paid advertising campaigns on Google Ads, Meta (Facebook/Instagram), LinkedIn, Twitter/X, or other ad platforms. Also use when the user mentions 'PPC,' 'paid media,' 'ROAS,' 'CPA,' 'ad campaign,' 'retargeting,' 'audience targeting,' 'Google Ads,' 'Facebook ads,' 'LinkedIn ads,' 'ad budget,' 'cost per click,' 'ad spend,' or 'should I run ads.' Use this for campaign strategy, audience targeting, bidding, and optimization. For bulk ad creative generation and iteration, see ad-creative. For landing page optimization, see cro.

72

Quality

90%

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 well-structured operational reference with strong actionability and clean progressive disclosure via four real bundle references. The RSA spec's self-check loop is a standout; minor trimming and validation tightening in the optimization sections would push it higher.

DimensionReasoningScore

Conciseness

Mostly lean operational content (tables, percentages, frameworks, the RSA spec) that adds detail Claude would not already know, with only minor over-explanations such as "showing ads to people who already bought wastes spend" that could be trimmed.

4 / 5

Actionability

Highly executable guidance throughout — concrete naming conventions, budget split percentages, ad-copy frameworks, video-ad timestamp structure, optimization levers keyed to symptoms, and a copy-paste-ready RSA output template with exact character limits.

5 / 5

Workflow Clarity

Clear sequencing from "Before Starting" context-gathering through platform selection, structure, and optimization, with the RSA section providing an explicit self-check feedback loop and pre-launch checklist; minor validation gaps remain in the looser optimization sections.

4 / 5

Progressive Disclosure

Well-signaled one-level-deep references (ad-copy-templates.md, audience-targeting.md, platform-setup-checklists.md, conversion-tracking.md — all present in ./references/), with detail appropriately split out and inline content limited to overview frameworks.

5 / 5

Total

18

/

20

Passed

Description

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

A strong description with comprehensive trigger terms, explicit what/when coverage, and clear boundary routing to adjacent skills. The only mild gap is that the stated actions are strategic-level rather than granular verbs.

DimensionReasoningScore

Specificity

Lists several concrete actions — "campaign strategy, audience targeting, bidding, and optimization" — alongside named platforms (Google Ads, Meta, LinkedIn, Twitter/X), but the action verbs stay somewhat high-level rather than granular, matching the anchor with minor coverage gaps.

4 / 5

Completeness

Explicitly answers both what ("help with paid advertising campaigns... campaign strategy, audience targeting, bidding, and optimization") and when ("When the user wants..." / "Also use when the user mentions...") with concrete trigger phrases, plus boundary routing to ad-creative and cro.

5 / 5

Trigger Term Quality

Comprehensive natural-term coverage including synonyms and platform-specific phrases — "PPC," "paid media," "ROAS," "CPA," "ad spend," "cost per click," "should I run ads," plus "Google Ads"/"Facebook ads"/"LinkedIn ads" — exactly matching the comprehensive-synonym anchor.

5 / 5

Distinctiveness Conflict Risk

Clear paid-ads niche with distinct trigger terms, and explicit disambiguation ("For bulk ad creative generation and iteration, see ad-creative. For landing page optimization, see cro") minimizes overlap with sibling skills.

5 / 5

Total

19

/

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

relative_links

Relative link issues: 7 suspicious

Warning

Total

15

/

16

Passed

Repository
joshmanders/dotfiles
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.