CtrlK
BlogDocsLog inGet started
Tessl Logo

paid-channel-prioritizer

For founders who don't know where to start with paid ads. Analyzes ICP, competitor ad presence, budget constraints, and product type to recommend which 1-2 paid channels to start with and provides a 90-day ramp plan. Prevents the common mistake of spreading a small budget across too many platforms.

70

Quality

88%

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

88%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-constructed process skill: concrete decision frameworks, executable research queries, explicit thresholds and checkpoints, and a complete output template make it highly actionable with a clearly sequenced workflow. The only weaknesses are minor redundancy (duplicate trigger sections, a trivial cost table) and a monolithic single-file structure where a large output template could be split into a reference file.

DimensionReasoningScore

Conciseness

The body is dense and table-driven with little conceptual padding — it assumes Claude knows what ad platforms are and focuses on decision data and thresholds. Minor trimmable elements exist (the "Cost" table that only states everything is free, and the "Trigger Phrases" section duplicating "When to Use"), which fits anchor 4 rather than the every-token-earns-its-place standard of 5.

4 / 5

Actionability

Guidance is fully executable for an instruction-only skill: exact web_search query strings, a weighted scoring matrix with factor weights, per-channel minimum viable budgets, explicit budget-allocation thresholds, a week-by-week ramp plan, and a copy-paste output template. It is not anchor 4 because there are no meaningful gaps in the concrete guidance.

5 / 5

Workflow Clarity

Phases 0-4 are clearly sequenced with explicit checkpoints ("Minimum 500 impressions per variant before judging", "Pause worst-performing ad variant"), decision criteria in Month 3 ("If working: Increase budget 30-50%... If not working: Diagnose"), and a pre-launch checklist. No destructive or batch operations, so the validation cap does not apply; feedback loops (re-run the analysis with real performance data) are present.

5 / 5

Progressive Disclosure

The skill is a single self-contained file with no references/, scripts/, or assets/ directories, and sections are clearly organized and navigable. However, at ~230 lines it exceeds the simple-skill threshold, and content such as the ~70-line output template could arguably live in a reference file — minor organization gaps that fit anchor 4 rather than the well-signaled one-level-deep reference structure of anchor 5.

4 / 5

Total

18

/

20

Passed

Description

83%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: it states concrete third-person capabilities, the concrete deliverable (1-2 channel recommendation plus a 90-day ramp plan), and an explicit audience/situation trigger. The main gap is trigger phrasing — natural user phrasings such as "which ad platform" or "Google Ads or Facebook Ads" are absent, which also leaves the when-clause short of anchor-5 concreteness.

DimensionReasoningScore

Specificity

"Analyzes ICP, competitor ad presence, budget constraints, and product type to recommend which 1-2 paid channels" and "provides a 90-day ramp plan" list multiple concrete third-person actions with comprehensive coverage of the skill's function. This matches the 5 anchor rather than 4, where only minor gaps in coverage would be tolerated.

5 / 5

Completeness

The 'what' is explicit (analyze ICP/competitors/budget, recommend 1-2 channels, deliver a 90-day plan) and the 'when' is present as "For founders who don't know where to start with paid ads", which is explicit situational trigger guidance. It falls short of anchor 5 because it lacks concrete trigger phrasing like "Use when...", and is not anchor 3 since the when-clause is stated rather than merely implied.

4 / 5

Trigger Term Quality

"paid ads", "paid channels", and "budget" are natural user terms, but common phrasings users would actually say — "ad platform", "Google Ads or Facebook Ads", "where should I run ads" — are absent. Good coverage with a few natural terms missing fits anchor 4, not the comprehensive synonym coverage of anchor 5.

4 / 5

Distinctiveness Conflict Risk

The niche — paid-channel selection and budget concentration for early-stage founders — is clearly distinct, with terms like "paid channels", "paid ads", and "competitor ad presence" unlikely to trigger for unrelated skills. Minimal conflict risk matches anchor 5.

5 / 5

Total

18

/

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository
gooseworks-ai/goose-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.