channel-picker
Skill6 starsChanged 4 months agoMITView on GitHub
Scores candidate channels on ICP presence, ability to execute, economics, and speed to signal, then commits to one primary channel plus support and lays out the 90-day plan with kill thresholds agreed up front. Use when marketing is spread across five half-run channels, or when picking where a new offer meets the market.
In this repository29 other files it gives its agents.
- ad-scriptsSkill
- battlecardSkill
- brand-voiceSkill
- campaign-debriefSkill
- case-study-writerSkill
- cmoSkill
- competitor-teardownSkill
- content-calendarSkill
- creative-briefSkill
- customer-deep-diveSkill
- email-sequenceSkill
- experiment-backlogSkill
- funnel-mapSkill
- hook-factorySkill
- kpi-treeSkill
- landing-pageSkill
- launch-planSkill
- lead-magnet-builderSkill
- marketing-auditSkill
- market-research-sprintSkill
- message-mapSkill
- objection-mapSkill
- offer-builderSkill
- onboardSkill
- positioning-workshopSkill
- pricing-testSkill
- repurposeSkill
- research-to-briefSkill
- weekly-reviewSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 23
Commit to one primary channel and at most two support channels.
- Distinctive: line 24
Write the not-doing list. Every channel not picked gets named as deliberately parked, with the condition that would reopen it, so it stops …
- Very specific: line 26
Update Channels & funnel in marketing-brief.md with the primary channel and the reasoning behind it.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Channel Picker — one channel, properly, before any second
Channel diversification is where small marketing teams go to die. Every channel has a learning curve, a native content shape, and a feedback delay, and splitting effort across five means mastering none. This skill forces the honest scoring, commits to one primary, and — just as important — writes the not-doing list so the parked channels stop taxing attention.
Inputs
- Channels currently running or under consideration, plus the real constraints (hours per week, budget, existing assets and skills): $ARGUMENTS
- From
marketing-brief.mdif present: the ICP and the avatar's watering holes (where buyers actually gather), the offer and price point (the economics hang off it), and any current channel numbers.
Do this
- Build the candidate list from evidence — the watering holes in the customer research, not the channels the team enjoys or the ones loudest this month. Inside Claude Code, channel-scout can map where buyers gather and channel-strategist can run the scoring.
- Score each candidate 1–5 on four axes, with a line of reasoning per score:
- ICP presence — are buyers there in buying mode, or just present?
- Ability to execute — do the skills, assets, and hours to do this channel well actually exist in-house?
- Economics — rough acquisition cost at realistic conversion rates against the offer's price, and the payback window.
- Speed to signal — how fast the channel says yes or no. Slow-signal channels are expensive places to learn.
- Sanity-check the maths on the top two: at this price, how many wins per month must the channel produce to pay back, and is that volume plausible there? Show the working.
- Commit to one primary channel and at most two support channels. Support means it feeds or compounds the primary — content that arms outbound, for instance — not a second bet running in parallel.
- Write the not-doing list. Every channel not picked gets named as deliberately parked, with the condition that would reopen it, so it stops leaking hours and guilt.
- Lay out the 90 days: weeks 1–2 setup and first tests, weeks 3–6 volume and iteration, weeks 7–12 scale or kill. Define the numbers that mean "working" for each phase now — before any spend, not during week six.
- Update Channels & funnel in
marketing-brief.mdwith the primary channel and the reasoning behind it.
Output
The scored channel table, the pick with its reasoning, the not-doing list with reopen conditions, and the 90-day plan with pre-agreed thresholds — the channel decision written into marketing-brief.md.
Rules
- Score from evidence — the brief's watering holes, realistic conversion benchmarks, actual hours available. A channel scored on enthusiasm fails on schedule.
- One primary until it demonstrably works. A second channel is earned by the first one's numbers, never defaulted into.
- "The ICP is on it" is not enough. They must be reachable there in buying mode, at economics the offer can afford.
- Kill thresholds are set before week one. Deciding mid-flight is how dead channels run for a year.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

