From builder-growth
Use before building any campaign, content plan, or outbound motion. Scores every candidate growth channel against eight criteria — audience presence, intent, cost to test, feedback speed, trust requirement, sales cycle fit, operational complexity, and measurement feasibility — before one is chosen. Blocks "let's try everything" and "we picked the channel everyone else uses" completions.
How this skill is triggered — by the user, by Claude, or both
Slash command
/builder-growth:channel-selection-auditThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
```
A CHANNEL CHOSEN BY DEFAULT IS A CHANNEL CHOSEN WRONG.
"Let's try everything" splits a limited budget across channels with no comparable signal, so nothing gets enough volume to learn anything before the budget runs out.
"Everyone else uses paid ads" describes a competitor's constraint, not yours.
Every candidate channel scored against the same eight criteria IS channel selection.
Trigger before:
growth-strategy-design produced a channel hypothesis that has not yet been validatedScore the channels that are realistically available given the strategy's segment, offer, and constraint. Not every channel applies to every project.
SEO · content · outbound · paid ads · partnerships · community ·
marketplaces · referrals · social · product-led growth · sales-led growth
Do not score channels with no plausible audience overlap with the target segment — note them as "not applicable" and move on.
Score each candidate channel 1–5 on every criterion. A channel that scores well on three criteria and poorly on the other five is not a strong channel — it is a channel with a narrow use case.
Is the target segment actually active on this channel, in measurable numbers? Presence without intent (browsing social media) scores lower than presence with intent (searching for a solution).
How close is the audience, on this channel, to actively looking for a solution to the problem the offer solves? Outbound and SEO often score high; awareness-stage social scores lower.
What does it cost — in budget and time — to get a directional read on whether this channel works? Paid ads can be tested cheaply and fast; partnerships and SEO are slow and compounding.
How long until the channel produces a usable signal (not final results — a directional signal)? Outbound and paid ads can signal in days. SEO and community can take months.
How much existing trust does this channel require before it converts? Cold outbound and paid ads require the offer to build trust in the moment. Referrals and community inherit trust from the referrer or group.
Does the channel's typical engagement window match the segment's actual decision timeline? A channel that delivers a lead in 2 minutes is wasted on a 6-month enterprise sales cycle if there is no nurture path.
What does running this channel well require — team skills, tooling, ongoing maintenance? Score lower for channels requiring capabilities the team does not have and cannot acquire within the strategy's timeframe.
Can this channel's contribution be isolated and measured, or does it only show up as unattributable lift? Channels that cannot be measured cannot be optimised — score them lower regardless of theoretical potential.
Pull the primary and secondary hypotheses from growth-strategy-design. Add any other channel with plausible audience overlap.
Score every candidate 1–5 against all eight criteria. Use real data where it exists; mark estimates explicitly as estimates.
| Channel | Audience | Intent | Cost | Speed | Trust | Sales fit | Complexity | Measurable | Total |
|------------|----------|--------|------|-------|-------|-----------|------------|------------|-------|
| [channel] | X | X | X | X | X | X | X | X | sum |
Re-weight the totals against the primary constraint from the strategy. A budget-constrained project weights "cost to test" higher; a trust-constrained project weights "trust requirement" higher.
Choose one primary channel (highest weighted score with sufficient audience presence) and 1–2 secondary channels to test next.
Name every channel considered and not chosen, with the specific criterion that ruled it out. This prevents the same channel from being re-proposed without new information.
Store at growth/channels/<project>-channel-audit-<date>.md.
These thoughts mean the audit was not done — stop:
When channel-selection-audit is satisfied, state it like this:
Channel selection audit complete.
File: growth/channels/<project>-channel-audit-<date>.md ✓
Candidate channels scored: <N>
Constraint weighting applied: [primary constraint from strategy] ✓
Scores (weighted):
| Channel | Total (weighted) |
| [ranked list] |
Primary channel selected: [channel] ✓
Strongest criteria: [top 2–3 scoring criteria]
Risk: [weakest criterion and mitigation]
Secondary channels: [1–2 channels] — queued for test after primary signal ✓
Rejected channels: <N> — each with the disqualifying criterion named ✓
Next step: campaign-brief-generator or launch-plan-design for [primary channel] ✓
A channel chosen without a documented score against all eight criteria fails this gate.
Channel choice made by habit or imitation puts a real budget behind an unvalidated assumption. The eight criteria force the same comparison every time, which means the choice can be defended, revisited, and learned from — instead of being a preference dressed up as a decision. Most channel failures are not channel failures; they are fit failures that a structured audit would have surfaced before the budget was spent.
npx claudepluginhub rbraga01/a-team --plugin builder-growthGuides completion of development work by verifying tests, detecting environment, and presenting structured options for merge, PR, or cleanup.
Enforces test-driven development: write failing test first, then minimal code to pass. Use when implementing features or bugfixes.
Guides creation and editing of skills using test-driven development with pressure scenarios and subagents to verify agent compliance.