Evaluate acquisition channels by unit economics, customer quality, and scalability to decide whether to scale, test, or kill.
Works with
Assesses three core dimensions: unit economics (CAC, LTV, payback period, LTV:CAC ratio), customer quality (retention, churn, NRR by channel), and scalability (magic number, addressable volume, CAC trends)
Delivers one of four recommendations: scale aggressively (LTV:CAC >3:1, payback <12mo), test and optimize (marginal economics with fixable problems), kill
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionacquisition-channel-advisorExecute the skills CLI command in your project's root directory to begin installation:
Fetches acquisition-channel-advisor from deanpeters/product-manager-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate acquisition-channel-advisor. Access via /acquisition-channel-advisor in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
0
total installs
0
this week
3.1K
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
3.1K
stars
Guide product managers through evaluating whether to scale, test, or kill an acquisition channel based on unit economics (CAC, LTV, payback), customer quality (retention, NRR), and scalability (magic number, volume potential). Use this to make data-driven go-to-market decisions and optimize channel mix for sustainable growth.
This is not a channel strategy framework—it's a financial lens for channel evaluation that helps you avoid scaling unprofitable channels or killing channels with fixable problems. Use when deciding how to allocate marketing budget across channels.
A systematic approach to evaluate acquisition channels:
Unit Economics — What does it cost to acquire, and what's the return?
Customer Quality — Do customers from this channel stick around and expand?
Scalability — Can this channel sustain growth at the volume you need?
Strategic Fit — Does this channel align with your go-to-market strategy?
| LTV:CAC | Payback | Customer Quality | Scalability | Decision |
|---|---|---|---|---|
| >3:1 | <12mo | Good retention | High volume | Scale aggressively |
| 2-3:1 | 12-18mo | Average retention | Medium volume | Test & optimize |
| <2:1 | >18mo | Poor retention | Low volume | Kill or fix |
Use this when:
Don't use this when:
Use workshop-facilitation as the default interaction protocol for this skill.
It defines:
Other (specify) when useful)This file defines the domain-specific assessment content. If there is a conflict, follow this file's domain logic.
This interactive skill asks up to 4 adaptive questions, offering 3-5 enumerated options at decision points.
Agent asks:
"Let's evaluate this acquisition channel. Please provide:
Channel details:
Customer acquisition:
Business context:
You can provide estimates if you don't have exact numbers."
Agent calculates (if not provided):
CAC = Monthly Spend / Customers Acquired per Month
Agent asks:
"Now let's compare this channel's unit economics to your blended metrics.
Channel Unit Economics:
Questions:
Do customers from this channel have similar LTV to other channels?
What's the payback period for this channel?
Based on answers, agent calculates:
Agent flags:
Agent asks:
"How do customers from this channel perform compared to other channels?
Retention & Expansion:
What's the churn rate for customers from this channel?
What's the NRR for customers from this channel?
What's the customer profile from this channel?
Based on answers, agent evaluates:
Agent flags:
Agent asks:
"Can this channel scale to meet your growth targets?
Efficiency & Volume:
What's the S&M efficiency for this channel (Magic Number)?
What's the addressable volume for this channel?
What's the CAC trend for this channel?
How much growth do you need from acquisition?
Based on answers, agent evaluates:
Agent synthesizes:
Agent offers 3-4 recommendations:
When:
Recommendation:
"Scale this channel aggressively — Excellent economics + scalability
Unit Economics:
Customer Quality:
Scalability:
Why this is a winner:
How to scale:
Expected impact:
Risk: Low. Strong unit economics support aggressive scaling."
When:
Recommendation:
"Test & optimize before scaling — Marginal economics, fixable
Current State:
Customer Quality:
Diagnosis: [One of these:]
How to optimize:
If CAC is the problem:
If LTV is the problem:
If targeting is the problem:
Timeline:
Don't scale yet: Current economics are break-even at best. Fix first, then scale."
When:
Recommendation:
"Kill this channel (or pause) — Economics don't support investment
Why:
Problem:
Customer Quality:
What's broken: [Specific diagnosis:]
Should you fix or kill?
Fix if:
Kill if:
Recommendation: Kill and reallocate budget
Reallocate to:
What to do with budget:
Exception: If this channel is <10% of total S&M spend, just pause it. Not worth fixing."
When:
Recommendation:
"Continue, but cap investment — Strategic value > short-term ROI
Financial Reality:
Why continue despite poor economics:
How to manage:
Timeline:
Risk: You're subsidizing growth. Make sure it's worth it."
If user has multiple channels, agent can generate:
| Channel | CAC | LTV | LTV:CAC | Payback | Magic Number | Quality | Recommendation |
|---|---|---|---|---|---|---|---|
| Google Ads | $500 | $2,000 | 4:1 | 8mo | 0.9 | High | Scale |
| Content | $200 | $1,500 | 7.5:1 | 4mo | 1.2 | High | Scale |
| Outbound | $10K | $50K | 5:1 | 18mo | 0.6 | Medium | Optimize |
| Events | $15K | $30K | 2:1 | 24mo | 0.3 | Low | Kill |
Budget allocation recommendation:
See examples/ folder for sample conversation flows. Mini examples below:
Channel: Organic content (blog, SEO)
Recommendation: Scale aggressively. Exceptional unit economics, fast payback, high-quality customers. Increase content spend 2-3x.
Channel: Google Ads
Recommendation: Test & optimize before scaling. CAC is high, onboarding is weak for this segment. Improve landing page, target higher-intent keywords, better onboarding for paid customers.
Channel: Industry events
Recommendation: Kill. CAC too high, payback too long, poor customer quality. Reallocate budget to content and paid search.
Symptom: "Let's 10x our Google Ads spend!" (LTV:CAC is 1.5:1)
Consequence: You accelerate cash burn without improving unit economics. Lose money faster.
Fix: Only scale channels with LTV:CAC >3:1 and payback <12 months. Fix broken channels before scaling.
Symptom: "CAC is only $100!" (but customers churn in 30 days)
Consequence: Low CAC means nothing if LTV is also low. You're acquiring churners, not customers.
Fix: Track cohort retention and NRR by channel. Low CAC + high churn = bad channel.
Symptom: "We got 10,000 signups from this campaign!" (5% convert to paid)
Consequence: Signups don't pay bills. CAC is calculated on paid customers, not signups.
Fix: Track CAC on paid customers only. Ignore vanity metrics like signups, impressions, clicks.
Symptom: "Blended CAC is $500" (but hiding that one channel is $10K CAC)
Consequence: Bad channels hide in blended metrics. You don't know which channels to kill.
Fix: Track CAC, LTV, payback by channel. Compare channels individually.
Symptom: "We reduced CAC 50%!" (by targeting low-intent, low-LTV customers)
Consequence: CAC dropped but so did LTV. Unit economics got worse, not better.
Fix: Optimize for LTV:CAC ratio, not CAC alone. Higher CAC with higher LTV is better.
Symptom: "LTV:CAC is 6:1, this channel is amazing!" (payback is 48 months)
Consequence: You run out of cash before recovering CAC. Great ratio, terrible cash flow.
Fix: Pair LTV:CAC with payback period. 3:1 with 8-month payback beats 6:1 with 36-month payback.
Symptom: "This channel didn't work after 2 weeks"
Consequence: Channels need time to optimize. Killing too early wastes learning.
Fix: Give channels 3-6 months and 100+ customers before evaluating. Track trends, not snapshots.
Prerequisites
Time Estimate
15-45 minutes depending on use case complexity
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
anthropics/claude-code
mblode/agent-skills
github/awesome-copilot
leonxlnx/taste-skill
sickn33/antigravity-awesome-skills
erichowens/some_claude_skills
acquisition-channel-advisor is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Keeps context tight: acquisition-channel-advisor is the kind of skill you can hand to a new teammate without a long onboarding doc.
Registry listing for acquisition-channel-advisor matched our evaluation — installs cleanly and behaves as described in the markdown.
Useful defaults in acquisition-channel-advisor — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
acquisition-channel-advisor has been reliable in day-to-day use. Documentation quality is above average for community skills.
acquisition-channel-advisor reduced setup friction for our internal harness; good balance of opinion and flexibility.
I recommend acquisition-channel-advisor for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
acquisition-channel-advisor is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Useful defaults in acquisition-channel-advisor — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Solid pick for teams standardizing on skills: acquisition-channel-advisor is focused, and the summary matches what you get after install.
showing 1-10 of 60