[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CTCA98EX33ADE91MPDGDXK":3,"skill-same:01M7CTCA98EX33ADE91MPDGDXK":94},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":40,"commitSha":41,"skillDirectory":42,"forksCount":14,"repositoryHtmlUrl":43,"repositoryHomepageUrl":6,"ownerHtmlUrl":44,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":45,"install":46,"resources":59},"01M7CTCA98EX33ADE91MPDGDXK","channel-economics",null,"Use when reviewing or rebalancing direct vs. partner-led channel economics — computing fully-loaded cost-to-serve per channel, channel ROI with cash \u002F LTV \u002F marginal lenses, and optimal channel mix subject to constraints. For Head of Commercial, RevOps, and VP Sales doing quarterly channel review when pipeline is mixed (e.g., 60% direct + 40% partner-led) and nobody actually knows which channel makes money after CAC, support load, partner discount, deal-velocity differences, retention differential, and overhead allocation are all loaded in. Outputs cost to serve, channel ROI verdicts (DOUBLE-DOWN \u002F MAINTAIN \u002F DEFUND \u002F EXIT), a sensitivity-tested channel-mix recommendation, and the diminishing-returns inflection (e.g., 'which channel actually makes money — direct or partner?').","azhri1990\u002Fjarvis-mega-repo","azhri1990","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F281207543?v=4","01M7BMC0WHXB2ZA9SH1PFJDYNS","Nashriq Mokhtar","01M7C4WMQVQ450E0NA99BG7BHA",0,"MIT","https:\u002F\u002Fgithub.com\u002Fazhri1990\u002Fjarvis-mega-repo\u002Fblob\u002Fmain\u002Frepos\u002Fproject-genesis\u002Fclaude-skills\u002F.vibe\u002Fskills\u002Fclaude-skills\u002Fcommercial\u002Fchannel-economics\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: channel-economics\ndescription: \"Use when reviewing or rebalancing direct vs. partner-led channel economics — computing fully-loaded cost-to-serve per channel, channel ROI with cash \u002F LTV \u002F marginal lenses, and optimal channel mix subject to constraints. For Head of Commercial, RevOps, and VP Sales doing quarterly channel review when pipeline is mixed (e.g., 60% direct + 40% partner-led) and nobody actually knows which channel makes money after CAC, support load, partner discount, deal-velocity differences, retention differential, and overhead allocation are all loaded in. Outputs cost to serve, channel ROI verdicts (DOUBLE-DOWN \u002F MAINTAIN \u002F DEFUND \u002F EXIT), a sensitivity-tested channel-mix recommendation, and the diminishing-returns inflection (e.g., 'which channel actually makes money — direct or partner?').\"\nversion: 2.8.0\nauthor: claude-code-skills\nlicense: MIT\ntags: [commercial, channel-economics, cost-to-serve, channel-mix, channel-roi, direct-vs-partner, unit-economics]\ncompatible_tools: [claude-code, codex-cli, cursor, antigravity, opencode, gemini-cli]\n---\n\n# channel-economics\n\n## Purpose\n\nHelp Head of Commercial \u002F RevOps \u002F VP Sales answer three questions at the quarterly channel review:\n\n1. **What does each channel actually cost to serve, fully loaded?** (direct headcount, channel manager attribution, partner discount, MDF, enablement time, support load, allocated overhead)\n2. **What is the ROI of each channel under three lenses?** (cash ROI year-1, LTV-adjusted ROI, marginal ROI — next dollar of investment)\n3. **What is the optimal channel mix subject to our strategic constraints?** (minimum direct floor, maximum partner concentration ceiling, sensitivity to CAC shifts)\n\nThe skill emits **per-channel verdicts** (DOUBLE-DOWN \u002F MAINTAIN \u002F DEFUND \u002F EXIT), a **sensitivity-tested mix recommendation**, and **the diminishing-returns inflection point**. It does not pick the strategy — humans do, with the numbers loaded honestly for the first time.\n\n## When to use\n\n- Quarterly channel review: pipeline is 60\u002F40 or 50\u002F50 direct vs partner and you don't actually know which one is profitable\n- Considering hiring a channel manager — need to know if the channel can clear the loaded-cost bar\n- Partner program ROI question from the board (\"we spent $X on MDF — what did we get?\")\n- A segment is over-indexed to one channel and you suspect mix dogma is blocking the other\n- About to expand into a new region and need to decide direct-first vs partner-first\n- M&A diligence: target company claims \"partner-led at 70% gross margin\" — need to validate after loading\n\n**Do not use for:**\n- Designing partner tiers, joint GTM motion, revshare splits → `partnerships-architect`\n- SDR-to-AE routing, lead scoring, MQL definitions → `business-growth\u002Frevenue-operations`\n- Strategic CRO decisions (\"should we hire a VP Sales?\", comp plan design) → `c-level-advisor\u002Fcro-advisor`\n- Quarterly close, GAAP revenue recognition, channel-level P&L for historical reporting → `finance\u002Ffinancial-analysis`\n- Per-deal discount approval → `deal-desk`\n- Pricing model design → `pricing-strategist`\n\n## Workflow\n\n### Step 1 — Intake channel data\n\nFill `assets\u002Fchannel_data_template.md` (≈ 20 min). Capture per channel: deal count TTM, ARR TTM, avg deal size, gross margin %, CAC, sales-cycle days, retention rate, expansion rate, partner discount %, all attributable costs (SDR \u002F AE \u002F SE \u002F channel manager \u002F CS \u002F support \u002F marketing \u002F partner MDF \u002F tooling \u002F overhead allocation %).\n\nThe template surfaces the costs teams most often forget: partner enablement time, certification investment, channel-conflict resolution overhead, channel-manager headcount cost.\n\n### Step 2 — Compute cost-to-serve per channel\n\nRun `scripts\u002Fcost_to_serve_calculator.py --input channel.json --output markdown`.\n\nOutput: fully-loaded cost-to-serve **per deal** AND **per dollar of ARR**, with direct costs broken out from allocated overhead, and a \"true gross margin\" line after channel-specific load. Flags double-counting and surfaces hidden costs.\n\nRun once per channel. The \"true gross margin\" line is the input the next two scripts care about.\n\n### Step 3 — Compute ROI per channel under three lenses\n\nRun `scripts\u002Fchannel_roi_analyzer.py --input roi.json --profile saas --output markdown`.\n\nOutput: per channel, three ROI numbers (Cash year-1, LTV-adjusted, Marginal), the diminishing-returns inflection point, and a verdict: DOUBLE-DOWN \u002F MAINTAIN \u002F DEFUND \u002F EXIT.\n\nVerdict logic is deterministic and surfaced in the report. Humans can override; the skill won't.\n\n### Step 4 — Optimize channel mix subject to constraints\n\nRun `scripts\u002Fchannel_mix_optimizer.py --input mix.json --profile saas --output markdown`.\n\nOutput: recommended mix that maximizes effective ARR subject to constraints (min direct %, max partner concentration), plus a sensitivity table (what if direct CAC rises 20%? what if partner discount widens 5 points?).\n\n### Step 5 — Decide\n\nTake the three reports into the quarterly channel review. The skill recommends; the human commits.\n\n## Scripts\n\n- `scripts\u002Fcost_to_serve_calculator.py` — fully-loaded cost-to-serve per deal AND per $ ARR, with hidden-cost surfacing\n- `scripts\u002Fchannel_roi_analyzer.py` — 3-lens ROI (Cash \u002F LTV \u002F Marginal) with verdicts and diminishing-returns inflection\n- `scripts\u002Fchannel_mix_optimizer.py` — constrained mix optimizer with sensitivity scenarios\n\nAll scripts: stdlib only. `--help`, `--sample`, `--input`, `--output` work on all three. Industry tuning via `--profile {saas,api,enterprise-software,marketplace,hardware}` on the two analyzers.\n\n## Quick example\n\n```bash\n# Emits fully-loaded cost-to-serve per channel (direct vs partner-led) for the built-in sample channel data\ncd commercial\u002Fskills\u002Fchannel-economics && python3 scripts\u002Fcost_to_serve_calculator.py --sample\n```\n\n## References\n\n- `references\u002Fchannel_economics_canon.md` — Skok, Bessemer State of the Cloud, Tunguz, Pacific Crest \u002F KeyBanc SaaS Survey, Ramanujam, Jay McBain (Canalys)\n- `references\u002Fcost_to_serve_canon.md` — Kaplan & Cooper (ABC), Horngren, Jeremy Hope, IBM CTS case studies, McKinsey, Gartner, BCG\n- `references\u002Fchannel_anti_patterns.md` — Forrester, Tunguz, Hessling, HBR, SiriusDecisions, MIT Sloan, Gartner\n\n## Assumptions\n\n- Channel economics is a **forward-looking** question. Historical channel P&L is finance's job; this skill loads forward economics for a decision.\n- \"Channel\" means a coherent go-to-market motion (direct outbound, partner-led, marketplace, reseller, OEM). It does not mean a marketing source.\n- Cost-to-serve requires **honest overhead allocation**. The script validates that overhead % is consistent across channels — false partner-margin lift from inconsistent allocation is the #1 anti-pattern.\n- LTV inputs (retention, expansion) are per-channel, not pooled. Partner-sourced customers often retain differently than direct-sourced — this difference is usually the largest economic variable and the most ignored.\n- Industry profiles (`--profile`) tune defaults for benchmarks (e.g., SaaS direct CAC payback target ~12mo, enterprise ~18mo) — they don't override your numbers.\n- This is a decision-support skill. Output is verdicts and a recommended mix, never an automatic resource reallocation.\n\n## Anti-patterns\n\n- **Treating \"influenced\" deals as \"sourced\" deals.** A partner that touched a deal your AE already had is not channel-sourced revenue. Loading this as partner revenue inflates partner ROI and inflates direct CAC simultaneously.\n- **Inconsistent overhead allocation.** Allocating 25% overhead to direct deals and 5% to partner deals because \"the partner handles the overhead\" is false. The partner manager, partner program, MDF, certification, and conflict-resolution all live in your P&L.\n- **Ignoring enablement time as a cost.** Every hour your AE spends co-selling with a partner is a direct cost charged to the partner channel — most teams forget to load it.\n- **MDF without ROI tracking.** Market Development Funds disbursed without an attributable pipeline ROI are just a partner-discount extension. The skill flags MDF with no return.\n- **Channel-mix dogma.** \"We're a partner-first company\" \u002F \"we don't sell direct\" blocks profitable segments. Mix should follow the math, not the slogan.\n- **Computing channel ROI without retention differential.** If partner-sourced customers churn 5 points higher than direct, ignoring it overstates partner LTV by 30-50%. Per-channel retention is mandatory input.\n- **No cost-attribution for channel-manager headcount.** A $200k channel manager managing $4M of partner ARR is $50 of channel-manager cost per $1k ARR — material to the verdict.\n- **Confusing this skill with partnerships-architect.** That skill designs the partner program. This skill tells you whether the program pays for itself.\n\n## Distinct from\n\n- **commercial\u002Fpartnerships-architect** — partner tier design, joint GTM motion, revshare splits, partner enablement. Partner program *structure*, not partner program *economics*. This skill consumes the program structure as input and emits the economic verdict.\n- **business-growth\u002Frevenue-operations** — lead routing, SDR motion, MQL definition, pipeline operations. RevOps owns the funnel mechanics; this skill loads the channel-level economic outcome.\n- **c-level-advisor\u002Fcro-advisor** — strategic CRO judgment: when to hire a VP Sales, comp plan philosophy, territory design, multi-year revenue strategy. CRO advisor consumes channel-economics output as one input among many.\n- **finance\u002Ffinancial-analysis** — close-and-report on historical channel P&L per GAAP. This skill is forward-looking decision support; finance is historical record. Different time horizon, different audience, different output.\n- **commercial\u002Fdeal-desk** — per-deal discount approval. Operates daily; this skill operates quarterly.\n- **commercial\u002Fpricing-strategist** — pricing model and tier design. Pricing is input; channel economics is what happens at that pricing across channels.\n\n## Forcing-question library (Matt Pocock grill discipline)\n\nWalked one at a time by `\u002Fcs:grill-commercial` or the orchestrator. Recommended answer + canon citation per question. Never bundled.\n\n1. **\"What's your fully-loaded cost-to-serve per channel — including channel-manager headcount, MDF, partner enablement time, and overhead allocation?\"**\n   Recommended: load all four. Most teams load partner discount but forget the channel-manager headcount and the enablement time, inflating partner margin by 8-15 points.\n   Canon: Kaplan & Cooper (HBR 1988) — *Measure Costs Right: Make the Right Decisions*. Activity-Based Costing was invented precisely because channel costs hide in overhead and distort margin comparisons.\n\n2. **\"What is the retention differential between direct-sourced and partner-sourced customers?\"**\n   Recommended: instrument per-channel retention BEFORE running channel ROI. A 5-point retention gap moves LTV by 30-50%.\n   Canon: David Skok (*For Entrepreneurs* — SaaS Metrics 2.0). LTV = (ARPA × Gross Margin) \u002F Churn. Channel-blind churn is the most common source of false channel ROI.\n\n3. **\"What share of 'channel-sourced' pipeline did your team actually originate?\"**\n   Recommended: if your AE already had the account, it's not channel-sourced — it's channel-influenced. Influence and source are different economic lines.\n   Canon: SiriusDecisions \u002F Forrester channel attribution research — confused source vs. influence is the #1 reason partner ROI is overstated industry-wide.\n\n4. **\"What is the marginal ROI of the next dollar invested in partner program vs. direct sales?\"**\n   Recommended: compute the diminishing-returns curve on both. Average ROI hides the fact that the next dollar might earn 0.3x while the average earns 2.1x.\n   Canon: Tomasz Tunguz (*Tomasz Tunguz blog* — channel CAC analyses). Average ROI is a vanity metric; marginal ROI drives investment decisions.\n\n5. **\"What's your MDF-to-attributable-pipeline ratio in the last 4 quarters?\"**\n   Recommended: \u003C 5:1 (every $1 of MDF should generate ≥ $5 of attributable pipeline within 2 quarters). Anything looser is partner-discount theatre.\n   Canon: Jay McBain (Canalys) — *State of the Channel* research. MDF without attribution discipline is the most expensive form of channel subsidy.\n\n6. **\"Is your channel-mix dogma blocking a profitable segment?\"**\n   Recommended: surface the dogma (\"we're partner-first\", \"we don't sell direct in SMB\") explicitly. Mix should follow the segment math.\n   Canon: MIT Sloan Management Review — *When Channel Conflict Means Growth*. Dogmatic single-channel strategies forfeit 15-25% of TAM in mid-market specifically.\n\n7. **\"What overhead-allocation methodology are you applying — and is it consistent across direct and partner?\"**\n   Recommended: same methodology, same denominator, both channels. Inconsistent allocation is the silent killer of channel-economics analysis.\n   Canon: Charles Horngren (*Cost Accounting: A Managerial Emphasis*) — allocation consistency is the precondition for cross-segment margin comparison. Without it, every conclusion is contaminated.\n\nWalk depth-first. Lock 1-3 before opening 4-7. After all 7 are answered, invoke `cost_to_serve_calculator.py` → `channel_roi_analyzer.py` → `channel_mix_optimizer.py` in sequence.\n","# channel-economics\n\n## Purpose\n\nHelp Head of Commercial \u002F RevOps \u002F VP Sales answer three questions at the quarterly channel review:\n\n1. **What does each channel actually cost to serve, fully loaded?** (direct headcount, channel manager attribution, partner discount, MDF, enablement time, support load, allocated overhead)\n2. **What is the ROI of each channel under three lenses?** (cash ROI year-1, LTV-adjusted ROI, marginal ROI — next dollar of investment)\n3. **What is the optimal channel mix subject to our strategic constraints?** (minimum direct floor, maximum partner concentration ceiling, sensitivity to CAC shifts)\n\nThe skill emits **per-channel verdicts** (DOUBLE-DOWN \u002F MAINTAIN \u002F DEFUND \u002F EXIT), a **sensitivity-tested mix recommendation**, and **the diminishing-returns inflection point**. It does not pick the strategy — humans do, with the numbers loaded honestly for the first time.\n\n## When to use\n\n- Quarterly channel review: pipeline is 60\u002F40 or 50\u002F50 direct vs partner and you don't actually know which one is profitable\n- Considering hiring a channel manager — need to know if the channel can clear the loaded-cost bar\n- Partner program ROI question from the board (\"we spent $X on MDF — what did we get?\")\n- A segment is over-indexed to one channel and you suspect mix dogma is blocking the other\n- About to expand into a new region and need to decide direct-first vs partner-first\n- M&A diligence: target company claims \"partner-led at 70% gross margin\" — need to validate after loading\n\n**Do not use for:**\n- Designing partner tiers, joint GTM motion, revshare splits → `partnerships-architect`\n- SDR-to-AE routing, lead scoring, MQL definitions → `business-growth\u002Frevenue-operations`\n- Strategic CRO decisions (\"should we hire a VP Sales?\", comp plan design) → `c-level-advisor\u002Fcro-advisor`\n- Quarterly close, GAAP revenue recognition, channel-level P&L for historical reporting → `finance\u002Ffinancial-analysis`\n- Per-deal discount approval → `deal-desk`\n- Pricing model design → `pricing-strategist`\n\n## Workflow\n\n### Step 1 — Intake channel data\n\nFill `assets\u002Fchannel_data_template.md` (≈ 20 min). Capture per channel: deal count TTM, ARR TTM, avg deal size, gross margin %, CAC, sales-cycle days, retention rate, expansion rate, partner discount %, all attributable costs (SDR \u002F AE \u002F SE \u002F channel manager \u002F CS \u002F support \u002F marketing \u002F partner MDF \u002F tooling \u002F overhead allocation %).\n\nThe template surfaces the costs teams most often forget: partner enablement time, certification investment, channel-conflict resolution overhead, channel-manager headcount cost.\n\n### Step 2 — Compute cost-to-serve per channel\n\nRun `scripts\u002Fcost_to_serve_calculator.py --input channel.json --output markdown`.\n\nOutput: fully-loaded cost-to-serve **per deal** AND **per dollar of ARR**, with direct costs broken out from allocated overhead, and a \"true gross margin\" line after channel-specific load. Flags double-counting and surfaces hidden costs.\n\nRun once per channel. The \"true gross margin\" line is the input the next two scripts care about.\n\n### Step 3 — Compute ROI per channel under three lenses\n\nRun `scripts\u002Fchannel_roi_analyzer.py --input roi.json --profile saas --output markdown`.\n\nOutput: per channel, three ROI numbers (Cash year-1, LTV-adjusted, Marginal), the diminishing-returns inflection point, and a verdict: DOUBLE-DOWN \u002F MAINTAIN \u002F DEFUND \u002F EXIT.\n\nVerdict logic is deterministic and surfaced in the report. Humans can override; the skill won't.\n\n### Step 4 — Optimize channel mix subject to constraints\n\nRun `scripts\u002Fchannel_mix_optimizer.py --input mix.json --profile saas --output markdown`.\n\nOutput: recommended mix that maximizes effective ARR subject to constraints (min direct %, max partner concentration), plus a sensitivity table (what if direct CAC rises 20%? what if partner discount widens 5 points?).\n\n### Step 5 — Decide\n\nTake the three reports into the quarterly channel review. The skill recommends; the human commits.\n\n## Scripts\n\n- `scripts\u002Fcost_to_serve_calculator.py` — fully-loaded cost-to-serve per deal AND per $ ARR, with hidden-cost surfacing\n- `scripts\u002Fchannel_roi_analyzer.py` — 3-lens ROI (Cash \u002F LTV \u002F Marginal) with verdicts and diminishing-returns inflection\n- `scripts\u002Fchannel_mix_optimizer.py` — constrained mix optimizer with sensitivity scenarios\n\nAll scripts: stdlib only. `--help`, `--sample`, `--input`, `--output` work on all three. Industry tuning via `--profile {saas,api,enterprise-software,marketplace,hardware}` on the two analyzers.\n\n## Quick example\n\n```bash\n# Emits fully-loaded cost-to-serve per channel (direct vs partner-led) for the built-in sample channel data\ncd commercial\u002Fskills\u002Fchannel-economics && python3 scripts\u002Fcost_to_serve_calculator.py --sample\n```\n\n## References\n\n- `references\u002Fchannel_economics_canon.md` — Skok, Bessemer State of the Cloud, Tunguz, Pacific Crest \u002F KeyBanc SaaS Survey, Ramanujam, Jay McBain (Canalys)\n- `references\u002Fcost_to_serve_canon.md` — Kaplan & Cooper (ABC), Horngren, Jeremy Hope, IBM CTS case studies, McKinsey, Gartner, BCG\n- `references\u002Fchannel_anti_patterns.md` — Forrester, Tunguz, Hessling, HBR, SiriusDecisions, MIT Sloan, Gartner\n\n## Assumptions\n\n- Channel economics is a **forward-looking** question. Historical channel P&L is finance's job; this skill loads forward economics for a decision.\n- \"Channel\" means a coherent go-to-market motion (direct outbound, partner-led, marketplace, reseller, OEM). It does not mean a marketing source.\n- Cost-to-serve requires **honest overhead allocation**. The script validates that overhead % is consistent across channels — false partner-margin lift from inconsistent allocation is the #1 anti-pattern.\n- LTV inputs (retention, expansion) are per-channel, not pooled. Partner-sourced customers often retain differently than direct-sourced — this difference is usually the largest economic variable and the most ignored.\n- Industry profiles (`--profile`) tune defaults for benchmarks (e.g., SaaS direct CAC payback target ~12mo, enterprise ~18mo) — they don't override your numbers.\n- This is a decision-support skill. Output is verdicts and a recommended mix, never an automatic resource reallocation.\n\n## Anti-patterns\n\n- **Treating \"influenced\" deals as \"sourced\" deals.** A partner that touched a deal your AE already had is not channel-sourced revenue. Loading this as partner revenue inflates partner ROI and inflates direct CAC simultaneously.\n- **Inconsistent overhead allocation.** Allocating 25% overhead to direct deals and 5% to partner deals because \"the partner handles the overhead\" is false. The partner manager, partner program, MDF, certification, and conflict-resolution all live in your P&L.\n- **Ignoring enablement time as a cost.** Every hour your AE spends co-selling with a partner is a direct cost charged to the partner channel — most teams forget to load it.\n- **MDF without ROI tracking.** Market Development Funds disbursed without an attributable pipeline ROI are just a partner-discount extension. The skill flags MDF with no return.\n- **Channel-mix dogma.** \"We're a partner-first company\" \u002F \"we don't sell direct\" blocks profitable segments. Mix should follow the math, not the slogan.\n- **Computing channel ROI without retention differential.** If partner-sourced customers churn 5 points higher than direct, ignoring it overstates partner LTV by 30-50%. Per-channel retention is mandatory input.\n- **No cost-attribution for channel-manager headcount.** A $200k channel manager managing $4M of partner ARR is $50 of channel-manager cost per $1k ARR — material to the verdict.\n- **Confusing this skill with partnerships-architect.** That skill designs the partner program. This skill tells you whether the program pays for itself.\n\n## Distinct from\n\n- **commercial\u002Fpartnerships-architect** — partner tier design, joint GTM motion, revshare splits, partner enablement. Partner program *structure*, not partner program *economics*. This skill consumes the program structure as input and emits the economic verdict.\n- **business-growth\u002Frevenue-operations** — lead routing, SDR motion, MQL definition, pipeline operations. RevOps owns the funnel mechanics; this skill loads the channel-level economic outcome.\n- **c-level-advisor\u002Fcro-advisor** — strategic CRO judgment: when to hire a VP Sales, comp plan philosophy, territory design, multi-year revenue strategy. CRO advisor consumes channel-economics output as one input among many.\n- **finance\u002Ffinancial-analysis** — close-and-report on historical channel P&L per GAAP. This skill is forward-looking decision support; finance is historical record. Different time horizon, different audience, different output.\n- **commercial\u002Fdeal-desk** — per-deal discount approval. Operates daily; this skill operates quarterly.\n- **commercial\u002Fpricing-strategist** — pricing model and tier design. Pricing is input; channel economics is what happens at that pricing across channels.\n\n## Forcing-question library (Matt Pocock grill discipline)\n\nWalked one at a time by `\u002Fcs:grill-commercial` or the orchestrator. Recommended answer + canon citation per question. Never bundled.\n\n1. **\"What's your fully-loaded cost-to-serve per channel — including channel-manager headcount, MDF, partner enablement time, and overhead allocation?\"**\n   Recommended: load all four. Most teams load partner discount but forget the channel-manager headcount and the enablement time, inflating partner margin by 8-15 points.\n   Canon: Kaplan & Cooper (HBR 1988) — *Measure Costs Right: Make the Right Decisions*. Activity-Based Costing was invented precisely because channel costs hide in overhead and distort margin comparisons.\n\n2. **\"What is the retention differential between direct-sourced and partner-sourced customers?\"**\n   Recommended: instrument per-channel retention BEFORE running channel ROI. A 5-point retention gap moves LTV by 30-50%.\n   Canon: David Skok (*For Entrepreneurs* — SaaS Metrics 2.0). LTV = (ARPA × Gross Margin) \u002F Churn. Channel-blind churn is the most common source of false channel ROI.\n\n3. **\"What share of 'channel-sourced' pipeline did your team actually originate?\"**\n   Recommended: if your AE already had the account, it's not channel-sourced — it's channel-influenced. Influence and source are different economic lines.\n   Canon: SiriusDecisions \u002F Forrester channel attribution research — confused source vs. influence is the #1 reason partner ROI is overstated industry-wide.\n\n4. **\"What is the marginal ROI of the next dollar invested in partner program vs. direct sales?\"**\n   Recommended: compute the diminishing-returns curve on both. Average ROI hides the fact that the next dollar might earn 0.3x while the average earns 2.1x.\n   Canon: Tomasz Tunguz (*Tomasz Tunguz blog* — channel CAC analyses). Average ROI is a vanity metric; marginal ROI drives investment decisions.\n\n5. **\"What's your MDF-to-attributable-pipeline ratio in the last 4 quarters?\"**\n   Recommended: \u003C 5:1 (every $1 of MDF should generate ≥ $5 of attributable pipeline within 2 quarters). Anything looser is partner-discount theatre.\n   Canon: Jay McBain (Canalys) — *State of the Channel* research. MDF without attribution discipline is the most expensive form of channel subsidy.\n\n6. **\"Is your channel-mix dogma blocking a profitable segment?\"**\n   Recommended: surface the dogma (\"we're partner-first\", \"we don't sell direct in SMB\") explicitly. Mix should follow the segment math.\n   Canon: MIT Sloan Management Review — *When Channel Conflict Means Growth*. Dogmatic single-channel strategies forfeit 15-25% of TAM in mid-market specifically.\n\n7. **\"What overhead-allocation methodology are you applying — and is it consistent across direct and partner?\"**\n   Recommended: same methodology, same denominator, both channels. Inconsistent allocation is the silent killer of channel-economics analysis.\n   Canon: Charles Horngren (*Cost Accounting: A Managerial Emphasis*) — allocation consistency is the precondition for cross-segment margin comparison. Without it, every conclusion is contaminated.\n\nWalk depth-first. Lock 1-3 before opening 4-7. After all 7 are answered, invoke `cost_to_serve_calculator.py` → `channel_roi_analyzer.py` → `channel_mix_optimizer.py` in sequence.\n",{"name":5,"tags":24,"author":31,"license":15,"version":32,"description":7,"compatible_tools":33},[25,5,26,27,28,29,30],"commercial","cost-to-serve","channel-mix","channel-roi","direct-vs-partner","unit-economics","claude-code-skills","2.8.0",[34,35,36,37,38,39],"claude-code","codex-cli","cursor","antigravity","opencode","gemini-cli","main","46d43f3edecde97283ac410e9051444d90120cfb","repos\u002Fproject-genesis\u002Fclaude-skills\u002F.vibe\u002Fskills\u002Fclaude-skills\u002Fcommercial\u002Fchannel-economics","https:\u002F\u002Fgithub.com\u002Fazhri1990\u002Fjarvis-mega-repo","https:\u002F\u002Fgithub.com\u002Fazhri1990","2026-10-10 07:58:58",{"source":8,"skillName":5,"commands":47,"prompt":57,"zipAvailable":58},[48,51,54],{"tool":49,"command":50},"npx","npx skills add azhri1990\u002Fjarvis-mega-repo --skill channel-economics",{"tool":52,"command":53},"bunx","bunx skills add azhri1990\u002Fjarvis-mega-repo --skill channel-economics",{"tool":55,"command":56},"pnpm","pnpm dlx skills add azhri1990\u002Fjarvis-mega-repo --skill channel-economics","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fazhri1990\u002Fjarvis-mega-repo\u002Fblob\u002Fmain\u002Frepos\u002Fproject-genesis\u002Fclaude-skills\u002F.vibe\u002Fskills\u002Fclaude-skills\u002Fcommercial\u002Fchannel-economics\u002FSKILL.md",true,[60,66,72,76,80,86,90],{"path":61,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":64,"sourceHtmlUrl":65},"assets\u002Fchannel_data_template.md","ASSET","资产文件",8041,"https:\u002F\u002Fgithub.com\u002Fazhri1990\u002Fjarvis-mega-repo\u002Fblob\u002Fmain\u002Frepos\u002Fproject-genesis\u002Fclaude-skills\u002F.vibe\u002Fskills\u002Fclaude-skills\u002Fcommercial\u002Fchannel-economics\u002Fassets\u002Fchannel_data_template.md",{"path":67,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":70,"sourceHtmlUrl":71},"references\u002Fchannel_anti_patterns.md","REFERENCE","参考文档",7847,"https:\u002F\u002Fgithub.com\u002Fazhri1990\u002Fjarvis-mega-repo\u002Fblob\u002Fmain\u002Frepos\u002Fproject-genesis\u002Fclaude-skills\u002F.vibe\u002Fskills\u002Fclaude-skills\u002Fcommercial\u002Fchannel-economics\u002Freferences\u002Fchannel_anti_patterns.md",{"path":73,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":74,"sourceHtmlUrl":75},"references\u002Fchannel_economics_canon.md",5753,"https:\u002F\u002Fgithub.com\u002Fazhri1990\u002Fjarvis-mega-repo\u002Fblob\u002Fmain\u002Frepos\u002Fproject-genesis\u002Fclaude-skills\u002F.vibe\u002Fskills\u002Fclaude-skills\u002Fcommercial\u002Fchannel-economics\u002Freferences\u002Fchannel_economics_canon.md",{"path":77,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":78,"sourceHtmlUrl":79},"references\u002Fcost_to_serve_canon.md",6696,"https:\u002F\u002Fgithub.com\u002Fazhri1990\u002Fjarvis-mega-repo\u002Fblob\u002Fmain\u002Frepos\u002Fproject-genesis\u002Fclaude-skills\u002F.vibe\u002Fskills\u002Fclaude-skills\u002Fcommercial\u002Fchannel-economics\u002Freferences\u002Fcost_to_serve_canon.md",{"path":81,"resourceType":82,"resourceTypeDesc":83,"sizeBytes":84,"sourceHtmlUrl":85},"scripts\u002Fchannel_mix_optimizer.py","SCRIPT","脚本",12018,"https:\u002F\u002Fgithub.com\u002Fazhri1990\u002Fjarvis-mega-repo\u002Fblob\u002Fmain\u002Frepos\u002Fproject-genesis\u002Fclaude-skills\u002F.vibe\u002Fskills\u002Fclaude-skills\u002Fcommercial\u002Fchannel-economics\u002Fscripts\u002Fchannel_mix_optimizer.py",{"path":87,"resourceType":82,"resourceTypeDesc":83,"sizeBytes":88,"sourceHtmlUrl":89},"scripts\u002Fchannel_roi_analyzer.py",9468,"https:\u002F\u002Fgithub.com\u002Fazhri1990\u002Fjarvis-mega-repo\u002Fblob\u002Fmain\u002Frepos\u002Fproject-genesis\u002Fclaude-skills\u002F.vibe\u002Fskills\u002Fclaude-skills\u002Fcommercial\u002Fchannel-economics\u002Fscripts\u002Fchannel_roi_analyzer.py",{"path":91,"resourceType":82,"resourceTypeDesc":83,"sizeBytes":92,"sourceHtmlUrl":93},"scripts\u002Fcost_to_serve_calculator.py",7935,"https:\u002F\u002Fgithub.com\u002Fazhri1990\u002Fjarvis-mega-repo\u002Fblob\u002Fmain\u002Frepos\u002Fproject-genesis\u002Fclaude-skills\u002F.vibe\u002Fskills\u002Fclaude-skills\u002Fcommercial\u002Fchannel-economics\u002Fscripts\u002Fcost_to_serve_calculator.py",[95,102,109,116,123,130],{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":19},"01M7CYPF9V9EMA4ZXS1TTCMBFH","syllabus","Generates a curated supplementary reading list from any course syllabus using Consensus academic search. Grill-me intake (syllabus input format + course audience + year range) plus a grouping forcing-options checkpoint before any search runs — so the reading list matches the course's level and recency need. Parses the syllabus to extract topics and learning outcomes, searches Consensus for recent peer-reviewed papers per topic, and produces a professionally formatted .docx with clickable Consensus links, plain-language summaries calibrated to audience level, and Bloom-higher-order discussion questions tied to course learning goals. Use when the user uploads a syllabus, course outline, or curriculum document and wants supplementary readings (e.g., 'create a reading list from this syllabus', 'find recent papers for my course') — even casual mentions with a syllabus attached should trigger this skill.","https:\u002F\u002Fgithub.com\u002Fazhri1990\u002Fjarvis-mega-repo\u002Fblob\u002Fmain\u002Frepos\u002Fproject-genesis\u002Fclaude-skills\u002Fresearch\u002Fsyllabus\u002Fskills\u002Fsyllabus\u002FSKILL.md",[],[],{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":19},"01M7CYNRJDTQCRF5KGPMBMSB1S","pulse","Multi-source recency research skill that takes the pulse of any topic across Reddit, Hacker News, the open web, and optionally X\u002FTwitter within a configurable recent window (default 30 days). Forcing intake clarifies topic specificity, angle (trend\u002Fsentiment\u002Fproblems\u002Fopportunities\u002Fcomparison), time window, and platform scope before searching. Returns a synthesized briefing with citations, engagement metrics, and cross-platform pattern analysis. Use when the user requests multi-source recency intelligence on a topic (e.g., 'pulse on [topic]', 'what's happening with [topic]', 'what are people saying about [topic]', 'current conversation about [topic]', 'take the pulse of [topic]', 'trending: [topic]', 'find me info on [topic]'), and for competitor research, trend discovery, tool comparisons, and audience sentiment analysis.","https:\u002F\u002Fgithub.com\u002Fazhri1990\u002Fjarvis-mega-repo\u002Fblob\u002Fmain\u002Frepos\u002Fproject-genesis\u002Fclaude-skills\u002Fresearch\u002Fpulse\u002Fskills\u002Fpulse\u002FSKILL.md",[],[],{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":115,"publishedAt":19},"01M7CYNAVSE84QD7HAWZWTY2FS","patent","Patent prior-art and landscape intelligence skill — not generic patent help. Commits to one of five sub-use-cases via forcing intake (novelty search \u002F freedom-to-operate \u002F competitive landscape \u002F acquisition diligence \u002F litigation prior-art) before any search runs. Searches Google Patents, Espacenet, USPTO, and optionally Lens.org for citation-graph signals. Output is an editable Word document (.docx) with verdict, ranked closest art (claim-text extracted), CPC-class-aware landscape, family-resolved hits, geographic coverage, FTO flags where applicable, strategy recommendations, and full audit log. Use when the user asks for patent searching or analysis (e.g., 'prior art search for [invention]', 'freedom to operate analysis for [product]'). Produces search signal, not legal advice — always recommends consulting a patent attorney before filing or licensing decisions. Trademark, copyright, and trade-secret questions are out of scope.","https:\u002F\u002Fgithub.com\u002Fazhri1990\u002Fjarvis-mega-repo\u002Fblob\u002Fmain\u002Frepos\u002Fproject-genesis\u002Fclaude-skills\u002Fresearch\u002Fpatent\u002Fskills\u002Fpatent\u002FSKILL.md",[],[],{"skillNo":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":120,"categories":121,"keywords":122,"publishedAt":19},"01M7CYN0CE8P5ZN7WV2X06HKPC","notebooklm","Browser automation skill for controlling Google's NotebookLM. Use when the user wants anything done in NotebookLM (e.g., 'open NotebookLM', 'check my [name] notebook', 'ask my notebook about X', 'add [source] to NotebookLM', 'generate a Video Overview from my notebook', 'use NotebookLM Studio'). Handles reading and querying notebooks, adding sources (URLs, text, files, YouTube links, synthesized content), generating Studio outputs (Audio\u002FVideo Overviews, Mind Maps, Reports incl. Briefing Doc\u002FStudy Guide\u002FFAQ, Flashcards, Quiz, slide decks, infographics — discover the exact set from the live Studio panel; the UI evolves fast), and creating new notebooks. Requires browser automation environment — fails gracefully when unavailable.","https:\u002F\u002Fgithub.com\u002Fazhri1990\u002Fjarvis-mega-repo\u002Fblob\u002Fmain\u002Frepos\u002Fproject-genesis\u002Fclaude-skills\u002Fresearch\u002Fnotebooklm\u002Fskills\u002Fnotebooklm\u002FSKILL.md",[],[],{"skillNo":124,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":127,"categories":128,"keywords":129,"publishedAt":19},"01M7CYMHZ3QRJ9BKRB859KW8TQ","litreview","Academic literature orientation skill that searches papers via free keyless APIs (PubMed E-utilities + OpenAlex) by default — with the Consensus MCP as an optional enhancement lane when connected — builds a strategic search plan using PICO (default) or SPIDER \u002F Decomposition \u002F hybrid as fallbacks, and synthesizes findings into a formatted Word (.docx) research guide. Grill-me intake (research question specificity + framework hint + tentative depth) before the recon search; a second forcing checkpoint after Phase 2 confirms framework + sub-areas + depth before searches consume budget. Configurable depth (5\u002F10\u002F20 queries) controls coverage vs. speed. Output is a 'launching pad' — an orientation guide that lets a researcher dive in confidently, not a finished review. Use when the user starts literature-oriented research (e.g., 'litreview on [topic]', 'literature review on [topic]', 'I'm starting a literature review on X', 'I'm writing a paper on X', 'help me research X', 'I'm doing research on X', 'can you help me research X'). Do NOT use for single one-off paper searches wanting a quick list — that's a plain PubMed\u002FOpenAlex (or Consensus) query.","https:\u002F\u002Fgithub.com\u002Fazhri1990\u002Fjarvis-mega-repo\u002Fblob\u002Fmain\u002Frepos\u002Fproject-genesis\u002Fclaude-skills\u002Fresearch\u002Flitreview\u002Fskills\u002Flitreview\u002FSKILL.md",[],[],{"skillNo":131,"name":132,"nameZh":6,"description":133,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":134,"categories":135,"keywords":136,"publishedAt":19},"01M7CYM3D8YKV7R6DT4RNJSF0A","grants","NIH grant research skill for clinical researchers. Grill-me intake (research idea + career stage + preliminary data + environment + submission posture + known institute targets) locks down the funding strategy before any search runs. Runs a 5-facet Consensus positioning analysis (with draft Significance\u002FInnovation language), maps the research to the right NIH institutes and study sections via RePORTER, finds NOSIs and funded overlap, and produces an editable Word document (.docx) with budget\u002Fscope-aware mechanism recommendations, submission timelines, and a mandatory program officer recommendation. Use when the user asks about research funding or makes any grant-related request (e.g., 'grants for [topic]', 'find grants for my research idea', 'what grants match my research', 'help me find NIH funding', 'grant opportunities for my research'). NIH-only scope — non-NIH funders (PCORI, DOD CDMRP, VA, foundations) are out of scope and flagged at intake.","https:\u002F\u002Fgithub.com\u002Fazhri1990\u002Fjarvis-mega-repo\u002Fblob\u002Fmain\u002Frepos\u002Fproject-genesis\u002Fclaude-skills\u002Fresearch\u002Fgrants\u002Fskills\u002Fgrants\u002FSKILL.md",[],[]]