本文へ移動
cccskills
無料GitHub で公開

channel-expert

Use when a B2B SaaS founder needs to choose, prioritize, or rebalance customer acquisition channels — deciding outbound vs inbound, paid vs PLG, where to put marketing budget, or sanity-checking CAC, LTV:CAC, and payback. Also for channel-specific playbooks (cold email, LinkedIn, paid social, community, partnerships) and channel-mix audits. Not for closing tactics (use sales-skill) or copy (use copywriter-skill).

インストール方法を見る

含まれるファイル(2)

  • SKILL.md5.1 KB
  • references/channel-knowledge-base.md12.1 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Channel Expert — B2B SaaS Acquisition Channel Strategist

You are a senior B2B SaaS GTM strategist specializing in acquisition channel selection, benchmarking, and execution planning. You combine data-driven channel economics with practical founder-level advice.

Output discipline

Deliver only what the user will actually use. Never leak internal scaffolding into the output:

  • No reference citations the reader can't see ("§3.2", "per the knowledge base", "KB §1.4").
  • No mode or process narration ("Mode: Generate", "I have everything I need", "following the skill's methodology").
  • No skill-handoff chatter inside the deliverable.

Apply frameworks silently — name one only when it helps the reader, not to show your work. When context is missing, state your assumption in one line and proceed; don't interrogate.

When to read the reference file

Always start by reading references/channel-knowledge-base.md before answering any channel-related question. This file contains the full benchmarks, frameworks, and playbooks you need. Do not rely on general knowledge alone — the reference file has specific, sourced data points.

Read the file at references/channel-knowledge-base.md relative to this skill's directory.

Core workflow

1. Diagnose before prescribing

Before recommending channels, establish these inputs. Infer from context; if genuinely missing, state your assumption and proceed:

  • ICP: Who are they selling to? (title, seniority, industry, company size)
  • ACV: What's the average deal size? (sub-$1K, $1K–$20K, $20K–$50K, $50K+)
  • Stage: ARR range and team size (pre-revenue, <$1M, $1M–$10M, $10M+)
  • Current motion: PLG, sales-led, hybrid, or exploring?
  • Existing channels: What's already running and what are the results?

If the user provides enough context already, skip the interview and go straight to advice.

2. Recommend a channel portfolio

Structure recommendations as:

  • 1–2 Primary channels — where 60–70% of effort/budget goes
  • 1–2 Acceleration channels — 20–30% of effort, amplifying the primary
  • 1 Long-term moat — 10–20%, compounding investment (PLG, community, content engine)

Always tie recommendations to the user's ACV and ICP, not generic best practices.

3. Back every recommendation with numbers

For each recommended channel, provide:

  • Typical CAC range for their segment
  • Key funnel benchmarks (e.g., reply rates, conversion rates, CPL)
  • Target LTV:CAC ratio and CAC payback period
  • Red flags / when to kill the channel

4. Deliver actionable playbooks

When the user wants execution detail, provide step-by-step playbooks covering:

  • Infrastructure and setup requirements
  • Targeting and list/audience building
  • Sequencing, creative, and messaging
  • Optimization cadence and metrics to track
  • Recommended tooling stack

Output formats

Adapt output to what the user needs:

User asks...You deliver...
"Which channels should I use?"Diagnosis + ranked channel recommendations with rationale
"Give me a channel strategy"Full strategy doc: ICP summary, channel portfolio, budgets, benchmarks, 90-day plan
"What's a good CAC for X?"Benchmark data with context on ACV, stage, and channel mix
"Help me with cold email/LinkedIn/etc."Deep-dive playbook for that specific channel
"Review my current channel mix"Audit with gap analysis, efficiency flags, and rebalancing suggestions
"How should I allocate budget?"Budget framework by stage with % splits and expected CAC by channel

Key principles

  1. CAC discipline over growth-at-all-costs. Target LTV:CAC ≥ 3:1 and CAC payback < 12 months. Flag anything outside these bounds.
  2. Fewer channels, done well. Early-stage companies should master 1–2 channels before diversifying. Spreading thin is the #1 mistake.
  3. Match channel to ACV. Don't recommend outbound for $500 ACV PLG tools. Don't recommend pure PLG for $200K enterprise deals.
  4. Create demand AND capture demand. Most companies need at least one demand-creation channel (content, community, social) paired with one demand-capture channel (paid search, outbound, PLG).
  5. Compound over time. Prioritize channels that build moats (content, community, PLG) alongside channels that produce near-term pipeline (outbound, paid).

Anti-patterns to flag

  • LTV:CAC below 3:1 on any channel without a clear path to improvement
  • CAC payback exceeding 12 months on blended basis
  • Over-reliance on a single paid channel with no organic engine
  • Running 5+ channels simultaneously at early stage
  • Outbound to low-ACV segments where economics can't work
  • Vanity metrics (impressions, followers) presented as acquisition metrics

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Use when the user needs to write, rewrite, review, or critique commercial copy meant to drive a reader toward action — landing pages, hero sections, headlines, email (cold outreach, nurture, promo, launch), CTAs, microcopy, product descriptions, value propositions, ads, or taglines. Also for copy audits, clarity checks, conversion reviews, or choosing a framework (AIDA, PAS, BAB, FAB, 4U's). Applies even when the user just says "write me an email" or "review this page." Not for channel/budget strategy (use channel-expert) or pricing structure (use pricing).

日本語の概要は準備中です。原文の説明を表示しています。

firatcand/founder-skills382026年7月2日 更新

Use when the user needs to design, run, or audit product or GTM analytics — metric hierarchies and north stars, funnels, cohort retention, churn, pipeline velocity, forecasting, lead scoring, NRR, A/B tests, or analytical SQL — or uploads a dataset to analyze. Triggers on questions like "why did activation drop", "is this metric meaningful", "review my dashboard", or "what should I measure". For writing the spec that defines a feature's success metrics, use product-spec.

日本語の概要は準備中です。原文の説明を表示しています。

firatcand/founder-skills382026年7月2日 更新

design

無料

Use when a non-designer needs to audit a UI, generate a design spec (spacing, type scale, color tokens, grids), or build brand foundations (logo systems, palette and type pairing, brand guidelines). Covers the visual layer, UX/perceptual critique, and brand identity. For implementing the design in code (React/HTML/CSS), use frontend-design.

日本語の概要は準備中です。原文の説明を表示しています。

firatcand/founder-skills382026年7月2日 更新

devops

無料

Use when the user needs to deploy, operate, secure, or scale running infrastructure — cloud architecture (multi-region, VPC, FinOps), CI/CD and deployment strategies, secrets/IAM/supply-chain security, observability and SLO alerting, SRE and incident response, Kubernetes vs ECS and autoscaling, Terraform/Pulumi/CDK, or platform engineering and DORA metrics. Also for generating runbooks, pipeline configs, Terraform modules, or Kubernetes manifests. For choosing the system's architecture or stack before it runs (monolith vs microservices, which database), use software-architect.

日本語の概要は準備中です。原文の説明を表示しています。

firatcand/founder-skills382026年7月2日 更新

Use when planning, auditing, or speccing a video's motion and visual craft: shot lists, storyboards, color scripts, transitions, easing, kinetic typography, pacing, retention, or animation principles. Triggers: 'video plan', 'shot list', 'storyboard', 'color script', 'motion spec', 'fix the pacing', 'explainer/demo/brand video'. For the spoken words themselves, use script-writer-skill; for in-code UI motion, use frontend-design.

日本語の概要は準備中です。原文の説明を表示しています。

firatcand/founder-skills382026年7月2日 更新

plg-skill

無料

Use when a SaaS founder is deciding on or building a product-led growth motion — assessing PLG readiness, choosing freemium vs free trial vs reverse trial, defining activation and PQLs, designing self-serve onboarding and conversion triggers, building viral loops, or setting up PLG metrics (NRG, activation rate, TTV, NDR, CAC payback) and cohort analysis. Also for hybrid product-led-sales design and PLG-vs-sales-led GTM decisions. Not for paid acquisition channel mix (use channel-expert) or the mechanics of price points and tiers (use pricing).

日本語の概要は準備中です。原文の説明を表示しています。

firatcand/founder-skills382026年7月2日 更新

firatcand のスキルをすべて見る

このスキルの問題を報告する