traction-channel-research
Research and shortlist startup traction channels before running Bullseye tests. Use when comparing acquisition channels, studying how similar companies grew, finding underused distribution strategies, or preparing the outer ring for a Traction-style growth process.
- License 许可
- MIT
- 最近更新
- 2026-11-11
- Stars
- ★ 1.6k
- Forks
- 474
01 前言 Front Matter
- name
- traction-channel-research
- license
- MIT
- metadata
- { "tags": "traction,growth,research,marketing,startups", "version": "0.1.0", "category": "Marketing", "displayName": "Traction Channel Research" }
- description
- Research and shortlist startup traction channels before running Bullseye tests. Use when comparing acquisition channels, studying how similar companies grew, finding underused distribution strategies, or preparing the outer ring for a Traction-style growth process.
- compatibility
- Codex, Claude Code, and other Agent Skills-compatible clients.
03 SKILL.md 正文
Traction Channel Research
Use this skill before traction-bullseye when the agent needs evidence about
which channels might work. The job is to replace founder guesses with grounded
channel ideas.
Source Traceability
Primary source: Traction, chapters 1, 3, and 5. Authoring notes: converted
lines 238-393, 555-674, and 787-902. The canonical channel list also appears
in ../traction-bullseye/references/source-map.md.
Research Workflow
- Define the product, target customer, business model, ACV or price point, and current growth stage.
- List all 19 channels, even if some look unlikely: targeting blogs, publicity, unconventional PR, search engine marketing, social and display ads, offline ads, search engine optimization, content marketing, email marketing, viral marketing, engineering as marketing, business development, sales, affiliate programs, existing platforms, trade shows, offline events, speaking engagements, and community building.
- For each channel, research comparable companies, adjacent markets, failed examples, and underused tactics.
- Separate channel from strategy. "SEO" is a channel; "comparison pages for high-intent alternatives" is a strategy.
- Estimate reach, cost, speed, confidence, and customer fit.
- Shortlist the top three to five strategies for Bullseye middle-ring tests.
Evidence To Look For
- Founder interviews, teardown posts, podcasts, and launch retrospectives.
- Competitor traffic sources, ad libraries, backlink patterns, and content footprints.
- Marketplaces, communities, events, newsletters, podcasts, and niche platforms where the customer already gathers.
- Signs of saturation: crowded ad auctions, copied content, high affiliate competition, or low response rates.
- Signs of underuse: unfashionable offline channels, narrow communities, ignored partners, or new platforms.
Output Format
# Traction Channel Research
## Context
- Product:
- Customer:
- Stage:
- Traction goal:
## Channel Scan
| Channel | Strategy Idea | Evidence | Reach | Cost | Speed | Fit | Confidence |
|---------|---------------|----------|-------|------|-------|-----|------------|
## Shortlist
1. [Channel + strategy] - [why test this]
2. [Channel + strategy] - [why test this]
3. [Channel + strategy] - [why test this]
4. [Optional channel + strategy] - [why test this]
5. [Optional channel + strategy] - [why test this]
## Bias Check
- Channels the team may be overvaluing:
- Channels the team may be ignoring:
## Recommended Next Tests
[Hand off to traction-test-planner.]
Quality Bar
- Prefer specific strategies over broad channel labels.
- Include at least one uncomfortable or underused channel.
- Distinguish evidence from guesses.
- Flag channels that cannot plausibly move the user's current traction goal.
04 同仓库更多 Skills
deja-search
deja-vu memory — search the user's past AI coding sessions with the deja CLI. Holds what they already settled and never wrote into the repo (naming rules, banned or already-tried tools, required checks before merge, preferred values, who owns what). Use before your first edit in a task, before you call a change done or ready to merge, before you recommend a tool, library, design or reviewer, before re-debugging an error that may already be solved, when they say 'didn't we fix this before', 'what did we decide about X' or 'I already have that', and before telling them something on this machine does not exist.
deja-reflect
End-of-session reflection and memory curation with deja-vu. Review what was decided, what commands broke and what repaired them, and record durable project rules or decisions with deja remember so the next session starts with them.
revid
Make, edit, export and post AI videos with Revid (revid.ai) through the Revid MCP server. Use whenever the user wants a short-form or long-form video made (from an idea, a script, a URL, an article, a PDF, a tweet, a product page, their own clips, or a song), wants to find what is going viral on TikTok, YouTube, Instagram or X before making something, wants to edit or re-export an existing Revid project, generate a standalone AI image or clip, make a series episode, or publish and schedule a finished video to connected social accounts. Covers setup (hosted MCP with OAuth, or an API key), the 36 tools, credits, polling and the rules for publishing. Routes to the more specific revid-* skills when one fits.
review-study
Review a QuestionPunk survey before launch for wording, answer choices, branching, and missing settings. Use for check my survey or review this draft before publishing.
manage-study
Find QuestionPunk studies, check status, publish an explicitly requested draft, or retrieve its participant link. Use for find my survey, publish this study, or how many people responded.
create-study
Create a saved QuestionPunk survey draft from a research brief or edit specified questions. Use for requests such as make a customer feedback survey or shorten my onboarding study.