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

76%

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

85%

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

The body is highly actionable with a well-sequenced, checkpoint-driven workflow and a self-contained structure appropriate for a single-file analytical skill. Only minor conciseness gains remain from removing duplicated trigger phrases and the restated core principle.

Dimension	Reasoning	Score
Conciseness	Largely efficient and instruction-dense with no conceptual over-explanation, but the 'Core principle' paragraph restates the description and 'Trigger Phrases' duplicates the 'When to Use' list, so some tokens could be trimmed.	2 / 3
Actionability	Provides copy-paste-ready guidance: concrete web_search query templates, a numeric weighted scoring matrix, dollar-threshold budget tiers, and a full markdown output template plus a pre-launch checklist.	3 / 3
Workflow Clarity	A clear Phase 0-4 sequence with explicit checkpoints ('Minimum 500 impressions per variant before judging', 'do NOT optimize yet') and a Month 3 feedback loop ('If working… / If not working: Diagnose…').	3 / 3
Progressive Disclosure	No bundle files exist and the body has no nested references; per the scoring notes a single-file skill with no need for external references scores 3 when sections are well-organized, which the phased headings achieve.	3 / 3
	Total	11 / 12 Passed

Description

67%

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 specific and distinctive, naming concrete inputs and outputs, but lacks an explicit 'Use when' trigger clause and misses several natural keyword variations a user would say.

Suggestions

Add an explicit 'Use when...' clause with natural triggers, e.g. 'Use when a founder asks where to run ads, which ad platform to pick, or how to allocate a small ad budget.'

Expand trigger terms to include common phrasings users actually say: 'Google Ads or Facebook Ads', 'which ad platform', 'where to spend my ad budget'.

Trim the closing sentence ('Prevents the common mistake of spreading a small budget across too many platforms') to keep the description focused on capabilities rather than justification.

Dimension	Reasoning	Score
Specificity	Names multiple concrete actions — 'Analyzes ICP, competitor ad presence, budget constraints, and product type' and two distinct outputs ('recommend which 1-2 paid channels', 'provides a 90-day ramp plan').	3 / 3
Completeness	Clearly answers 'what' but 'when' is only implied via 'For founders who don't know where to start'; there is no explicit 'Use when...' clause, which caps completeness at 2 per the rubric.	2 / 3
Trigger Term Quality	Has relevant terms ('paid ads', 'paid channels', 'budget') and a natural phrase ('where to start with paid ads'), but misses common variations users say like 'Google Ads', 'Facebook Ads', or 'which ad platform'.	2 / 3
Distinctiveness Conflict Risk	A clear niche (paid channel selection for founders, anchored by the budget-concentration angle) with distinct triggers unlikely to conflict with unrelated skills.	3 / 3
	Total	10 / 12 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: 8866b2a

Reviewed: 2 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.