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.

Quality

67%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/ads/composites/paid-channel-prioritizer/SKILL.md

Quality

Content

66%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, actionable skill with concrete query templates and a usable output format, but it carries some redundancy (duplicate trigger lists) and lacks explicit validation checkpoints in its research and scoring workflow.

Suggestions

Consolidate the "When to Use" and "Trigger Phrases" sections into one to remove redundancy and save tokens.

Add an explicit validation checkpoint after Phase 1 channel scoring (e.g., "Confirm top channel meets minimum viable budget and creative readiness before recommending") to strengthen the workflow.

Move the channel context notes table and budget-allocation tiers into a references file to improve progressive disclosure and reduce inline bulk.

Dimension	Reasoning	Score
Conciseness	Mostly efficient structured content, but the repeated trigger-phrase list ("When to Use" plus a later "Trigger Phrases" section), the lengthy core-principle illustration, and large blank template tables add padding that could be trimmed without losing signal.	3 / 5
Actionability	Provides concrete executable web_search query templates, a fillable channel-scoring matrix with explicit weights, and a copy-ready markdown output template; the matrix cells remain placeholders ("[1-10]") rather than fully worked examples, leaving minor gaps.	4 / 5
Workflow Clarity	The Phase 0→4 sequence is clear and includes a pre-launch checklist, but there is no validation checkpoint after competitor research or scoring, and Month 1 explicitly says "do NOT optimize yet" without a verification gate before proceeding — checkpoints are largely implicit.	3 / 5
Progressive Disclosure	Well-organized with clear section headers and one-level-deep structure; no bundle files are present so all content is inline, but the phases are appropriately scoped and the output template is clearly signaled, with only minor cases (channel context table) that could live in a reference file.	4 / 5
	Total	14 / 20 Passed

Description

68%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, specific description that names concrete actions and a clear use case, but it omits an explicit "Use when..." trigger clause and leans on domain vocabulary rather than the natural phrases users actually say.

Suggestions

Add an explicit "Use when an early-stage founder asks where to run ads or which ad platform to start with" clause to lift completeness and trigger coverage.

Include natural user phrasing such as "where should I run ads," "which ad platform," or "Google Ads or Facebook Ads" as trigger terms in the description.

Tighten the "Prevents the common mistake..." sentence or move it to the body; it is rationale rather than capability and dilutes the trigger signal.

Dimension	Reasoning	Score
Specificity	States multiple concrete actions — "Analyzes ICP, competitor ad presence, budget constraints, and product type," "recommend which 1-2 paid channels to start with," and "provides a 90-day ramp plan" — with minor coverage gaps versus the exhaustive anchor.	4 / 5
Completeness	Clearly answers "what" (analyze inputs to recommend channels and a 90-day plan) and implies "when" via the founder-audience framing, but lacks an explicit "Use when..." clause with concrete trigger phrases, which caps it below 5.	4 / 5
Trigger Term Quality	Targets the audience ("founders who don't know where to start with paid ads") but lacks natural query phrases a user would speak; "paid ads," "paid channels," and "90-day ramp plan" are domain terms rather than the colloquial variants (e.g., "where should I run ads") that appear only in the body.	3 / 5
Distinctiveness Conflict Risk	The paid-channel-selection niche is fairly distinct with a clear anti-pattern ("Prevents the common mistake of spreading a small budget across too many platforms"), though it overlaps broadly with general marketing/advertising skills.	4 / 5
	Total	15 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: gooseworks-ai/goose-skills
Path: skills/ads/composites/paid-channel-prioritizer/SKILL.md
Commit: 2523432

Reviewed: 7 days ago

Table of Contents

Discovery Implementation Validation

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.