acquisition-channel-advisor

Evaluate acquisition channels using unit economics, customer quality, and scalability. Use when deciding whether to scale, test, or kill a growth channel.

Quality

83%

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

Quality

Content

77%

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 clear sequenced workflow, concrete formulas, and thresholds. Its weaknesses are token efficiency (heavy length and repetition) and progressive disclosure (most detail is inline in one large file rather than split into reference files).

Suggestions

Cut the redundant Purpose paragraph (it duplicates the frontmatter intent line) and condense the basic metric glosses like 'CAC (Customer Acquisition Cost)' that Claude already knows.

Move the four full recommendation-pattern templates and the ten Common Pitfalls into reference files under references/, leaving SKILL.md as an overview that links one level deep.

Collapse the repeated blank-laden template blocks into a single parameterized pattern to reduce repetition across the Scale / Optimize / Kill / Invest sections.

Dimension	Reasoning	Score
Conciseness	The body runs ~640 lines with notable padding — the Purpose section restates the frontmatter intent nearly verbatim, recommendation templates repeat large blank-laden blocks, and basic metric definitions (e.g. 'CAC (Customer Acquisition Cost)') restate concepts Claude already knows. It is structured and instructional rather than pure fluff, so it clears level 1, but it could be tightened substantially.	2 / 3
Actionability	It gives concrete formulas (CAC = Monthly Spend / Customers Acquired per Month; Magic Number = (New MRR × 4) / S&M Spend), numeric decision thresholds, a decision matrix, and four fully-specified recommendation patterns with enumerated options — copy-paste ready guidance.	3 / 3
Workflow Clarity	Steps 0–5 are explicitly sequenced, each with 'Agent asks / calculates / flags' substeps, and the ✅/⚠️/🚨 flag bands act as evaluation checkpoints. Because this is advisory rather than a destructive/batch operation, the missing validate-retry loops do not cap the score.	3 / 3
Progressive Disclosure	Sections are well organized, and external references are clearly signaled (workshop-facilitation skill, examples/ folder), but there are no bundle files and the long recommendation templates and ten inline Common Pitfalls are content that could be split into separate reference files, leaving a monolithic single file rather than an overview pointing one level deep.	2 / 3
	Total	10 / 12 Passed

Description

90%

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 well-constructed: it pairs a clear capability statement with an explicit 'Use when' trigger and uses natural PM vocabulary. Its only weakness is specificity, leaning on one verb plus three lenses rather than a list of discrete actions.

Dimension	Reasoning	Score
Specificity	It states 'Evaluate acquisition channels using unit economics, customer quality, and scalability', naming the domain plus three evaluation lenses, but relies on a single action verb ('Evaluate') rather than enumerating multiple distinct concrete actions, so it sits at the domain-and-some-actions level rather than the comprehensive-action list.	2 / 3
Completeness	It answers both what ('Evaluate acquisition channels using unit economics, customer quality, and scalability') and when via an explicit 'Use when deciding whether to scale, test, or kill a growth channel' clause.	3 / 3
Trigger Term Quality	Natural PM phrasing is well covered — 'acquisition channels', 'growth channel', and the decision trigger 'whether to scale, test, or kill' are terms a user would actually say when they need this skill.	3 / 3
Distinctiveness Conflict Risk	The acquisition-channel / unit-economics framing plus the 'scale, test, or kill' trigger carves out a clear niche that is unlikely to fire for unrelated skills.	3 / 3
	Total	11 / 12 Passed

Validation

81%

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 — 13 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (656 lines); consider splitting into references/ and linking	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
relative_links	Relative link issues: 1 suspicious	Warning

	Total	13 / 16 Passed

Repository: deanpeters/Product-Manager-Skills
Path: skills/acquisition-channel-advisor/SKILL.md
Commit: 9971018

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