CtrlK
BlogDocsLog inGet started
Tessl Logo

paid-media-strategy

A discipline for running paid media that does not light money on fire. Hypothesis writing for paid spend, channel selection, budget allocation, audience targeting, bid strategy, campaign types, what NOT to spend on, attribution reality, and the failure modes that produce expensive lessons. Triggers on paid media strategy, ad budget allocation, channel selection, paid media plan, audit my Google Ads, audit my Meta Ads, scale paid media, kill underperforming campaign, paid media hypothesis, ad spend strategy, attribution reality, performance marketing strategy. Also triggers when a team is asking how to scale paid media, or whether to add a new channel, or how to reallocate spend across channels.

65

Quality

78%

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/paid-media-strategy/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 clearly defines its domain (paid media strategy), lists numerous specific capabilities, and provides extensive trigger terms that match natural user language. The explicit trigger section and scenario-based triggers ensure Claude can confidently select this skill. The only minor weakness is the slightly informal tone ('does not light money on fire', 'expensive lessons') which, while memorable, adds flavor rather than functional clarity.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: hypothesis writing, channel selection, budget allocation, audience targeting, bid strategy, campaign types, what NOT to spend on, attribution reality, and failure modes. These are clearly defined capabilities.

3 / 3

Completeness

Clearly answers both 'what' (hypothesis writing, channel selection, budget allocation, audience targeting, bid strategy, etc.) and 'when' with explicit trigger terms and scenario-based triggers ('when a team is asking how to scale paid media, or whether to add a new channel, or how to reallocate spend').

3 / 3

Trigger Term Quality

Excellent coverage of natural terms users would say: 'audit my Google Ads', 'audit my Meta Ads', 'scale paid media', 'kill underperforming campaign', 'ad spend strategy', 'attribution reality', 'performance marketing strategy'. These are highly natural phrases a user would actually type.

3 / 3

Distinctiveness Conflict Risk

Occupies a clear niche around paid media strategy and ad spend. The specific mentions of Google Ads, Meta Ads, bid strategy, and attribution make it highly distinct from general marketing or content strategy skills.

3 / 3

Total

12

/

12

Passed

Implementation

57%

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

This is a strong strategy skill with clear opinions, good structure, and excellent progressive disclosure to reference files. Its main weaknesses are moderate verbosity (some sections explain what Claude or a senior marketer already knows) and a lack of truly executable, copy-paste-ready artifacts like audit checklists, decision trees, or template structures inline. The 11-consideration framework and hypothesis discipline are standout sections that provide real value.

Suggestions

Add an inline audit checklist (e.g., a markdown checklist for 'What NOT to spend on') that can be directly applied to an account review, making the guidance more immediately actionable.

Trim the introductory and 'What this skill is for' sections significantly—Claude doesn't need the motivation paragraph about efficiency gains or the explanation of who the audience is; jump straight to the hypothesis discipline.

Add a concrete step-by-step workflow for the most common trigger ('audit my Google Ads') with explicit validation checkpoints, e.g., 'Step 1: Pull last 90 days data → Step 2: Check against waste list → Step 3: Flag campaigns failing pre-commit rules → Step 4: Recommend scale/hold/kill for each.'

DimensionReasoningScore

Conciseness

The skill is well-written and mostly efficient, but it's quite long (~400 lines) with some sections that over-explain concepts a senior performance marketer (or Claude) would already know. The introductory paragraphs, the 'What this skill is for' section, and the closing section add context that doesn't directly instruct. Some channel descriptions repeat common knowledge. However, the content is not egregiously padded—most sections carry useful, opinionated guidance.

2 / 3

Actionability

The skill provides strong strategic guidance with specific numbers (e.g., '30+ conversions for tCPA', 'frequency above 4', '70-30 to 80-20 splits') and concrete decision rules, which is good. However, it lacks executable artifacts—no code, no command examples, no templates inline, no audit checklists with checkboxes, no example spreadsheet structures. For a strategy skill this is partially acceptable, but the guidance remains at the 'informed advice' level rather than 'copy-paste ready' operational level. The hypothesis example is excellent and concrete, but most other sections describe what to do rather than providing ready-to-use frameworks.

2 / 3

Workflow Clarity

The 11-consideration framework provides a clear sequence, and the scale/hold/kill decision output is well-defined. The hypothesis section includes pre-commitment and falsification rules, which serve as validation checkpoints. However, the skill lacks explicit step-by-step workflows for common operations like 'audit an existing account' or 'add a new channel'—these are described conceptually but not sequenced with validation gates. For a skill covering destructive budget decisions, the absence of explicit 'check X before proceeding to Y' patterns in the operational sections is a gap.

2 / 3

Progressive Disclosure

The skill has excellent progressive disclosure structure. The main body provides opinionated summaries for each topic, and seven clearly-labeled reference files are linked at relevant points throughout the text and collected in a dedicated reference section. References are one level deep, well-signaled with descriptive text, and the paths are consistent. The main file serves as a navigable overview that points to deeper detail appropriately.

3 / 3

Total

9

/

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.