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-06-26
- Stars
- ★ 0
- Forks
- 0
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
android-emulator-qa
Use when validating Android feature flows in an emulator with adb-driven launch, input, UI-tree inspection, screenshots, and logcat capture.
supabase-postgres-best-practices
Postgres performance optimization and best practices from Supabase. Use this skill when writing, reviewing, or optimizing Postgres queries, schema designs, or database configurations.
sentry
Use when the user asks to inspect Sentry issues or events, summarize recent production errors, or pull basic Sentry health data via the Sentry API; perform read-only queries with the bundled script and require `SENTRY_AUTH_TOKEN`.
render-workflows
Sets up, develops, tests, and deploys Render Workflows. Covers first-time scaffolding (via CLI or manual), SDK installation (Python or TypeScript), task patterns (retries, subtasks, fan-out), local development, Dashboard deployment, and troubleshooting. Use when a user wants to set up Render Workflows for the first time, scaffold a workflow service, add or modify workflow tasks, test workflows locally, or deploy workflows to Render.
render-web-services
Configures Render web services—port binding, TLS, health checks, custom domains, auto-deploy, PR previews, persistent disks, and deploy lifecycle. Use when the user needs to set up a web service, fix health check failures, add a custom domain, configure zero-downtime deploys, or troubleshoot port binding issues.
render-static-sites
Deploys and configures static sites on Render's global CDN—build commands, publish paths, SPA routing, redirects, custom headers, and PR previews. Use when the user needs to deploy a static site, set up a React/Vue/Hugo/Gatsby frontend, configure SPA fallback routing, add redirect rules, customize response headers, or choose between a static site and a web service for their frontend. Trigger terms: static site, CDN, SPA, single-page app, React deploy, Vue deploy, Hugo, Gatsby, Docusaurus, Jekyll, staticPublishPath.