distribution-channels
The distribution-channels skill guides strategies for selling products through third-party marketplaces and app stores such as AWS Marketplace, the Chrome Web Store, Shopify App Store, and GPTs, distinguishing them from curated directories. Use this skill when planning marketplace listings, optimizing product discoverability, or reducing procurement friction for enterprise customers across cloud platforms, mobile stores, design tools, and vertical-specific storefronts.
git clone --depth 1 https://github.com/kostja94/marketing-skills /tmp/distribution-channels && cp -r /tmp/distribution-channels/skills/channels/distribution/distribution-channels ~/.claude/skills/distribution-channelsSKILL.md
# Channels: Distribution Channels Guides product distribution via third-party marketplaces and app stores. Distinct from **directory-submission** (curated lists, Product Hunt, Taaft)—marketplaces are storefronts where customers discover and purchase apps, plugins, or integrations. Hyperscaler marketplaces (AWS, Azure, GCP) alone are projected to process $85B+ in software sales by 2028. **When invoking**: On **first use**, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output. ## Channel Types | Type | Definition | Examples | |------|------------|----------| | **Direct** | Company sells via own assets | Website, eCommerce, sales team | | **Indirect** | Third parties sell on your behalf | Marketplaces, app stores, resellers | **Marketplaces** = Digital storefronts where customers discover and buy; often pre-approved budgets (cloud spend), consolidated billing, faster procurement. ## Marketplace Categories | Category | Platforms | Product fit | |----------|-----------|-------------| | **Design & collaboration** | Figma Community, Canva Apps, Adobe Exchange | Design tools, templates | | **Browser extensions** | Chrome Web Store, Firefox Add-ons | Extensions, dev tools | | **Cloud & enterprise** | AWS Marketplace, Google Cloud Marketplace, Azure Marketplace | SaaS, data, infra | | **Mobile** | App Store, Google Play, Microsoft Store | Mobile apps, cross-platform | | **Vertical** | Shopify App Store, Slack App Directory, Salesforce AppExchange, Zoom Marketplace | E-commerce, collaboration, CRM | | **Developer** | GitHub Marketplace, WordPress Plugins | Dev tools, integrations | | **AI** | GPTs (OpenAI), emerging AI app stores | AI apps, agents | | **Social commerce** | Pinterest Product Pins | E-commerce, design tools, templates; Product Schema or Pinterest Catalog | **Pinterest Product Pins**: Configure product links; shopping tags; link to site. Requires Product Schema or Pinterest Catalog. See **pinterest-posts**. ## Listing Optimization | Practice | Guideline | |----------|-----------| | **Reduce procurement friction** | Vendor Insights, standard contracts; streamline enterprise buying | | **Pricing models** | Free trials, pay-as-you-go, private offers for enterprise | | **Trust signals** | Verified reviews, partner badges, clear taxonomy | | **Discoverability** | Optimize for marketplace search; clear descriptions, tags | | **Co-sell** | Partner with platform field teams when available | **Listing as asset**: Your marketplace page is both storefront and onboarding tool; prospects validate, customers discover integrations. ## Platform Selection by Product Type | Product type | Prioritize | |--------------|------------| | Design / collaboration | Figma, Canva, Adobe | | Browser extension | Chrome, Firefox | | Cloud / enterprise SaaS | AWS, GCP, Azure | | Mobile app | App Store, Google Play, Microsoft Store | | E-commerce | Shopify | | Collaboration | Slack, Zoom | | Developer tools | GitHub, WordPress | | AI application | GPTs, emerging AI stores | | E-commerce / templates | Pinterest Product Pins | ## Related Skills - **directory-submission**: Curated lists (Taaft, Product Hunt, G2)—different from marketplaces; both are distribution - **integrations-page-generator**: Integrations page content; marketplace listing drives discovery - **cold-start-strategy**: Distribution as cold-start channel - **localization-strategy**: Regional marketplaces by locale
When the user wants to create, optimize, or audit About page content. Also use when the user mentions "about page," "about us," "company story," "our team," "about section," "company overview," "brand story," "team page," or "who we are." For sitewide page planning, use website-structure.
When the user wants to plan, implement, or optimize affiliate marketing strategy. Also use when the user mentions "affiliate marketing," "affiliate program strategy," "CPS model," "affiliate recruitment," "commission structure," "affiliate partners," "affiliate network," "affiliate tracking," "affiliate commission," or "partner marketing." For affiliate page, use affiliate-page-generator.
When the user wants to create, optimize, or audit affiliate program page content. Also use when the user mentions "affiliate program," "affiliate page," "partner program," "referral program page," "affiliate landing," "partner landing," "commission page," or "affiliate signup." For affiliate program strategy, use affiliate-marketing.
When the user wants to track AI search traffic in GA4 or GSC. Also use when the user mentions "AI traffic," "ChatGPT referral," "Perplexity traffic," "AI Overviews," "GA4 AI sources," "AI search analytics," "track AI referrals," "AI search traffic," "Claude traffic," or "how to track AI traffic." For AI SEO strategy, use generative-engine-optimization.
When the user wants to create, optimize, or audit alternatives or comparison content (page or blog article). Also use when the user mentions "alternatives page," "alternatives listicle," "X alternatives," "competitor comparison," "vs page," "compare page," "best alternatives to X," "switch from X," "competitor brand traffic," "brand keyword ads," or "intercept competitor search." For competitor research, use competitor-research.
When the user wants to set up, audit, or optimize analytics tracking (GA4, events, conversions). Also use when the user mentions "Google Analytics," "GA4," "event tracking," "conversions," "attribution model," "gtag," "data layer," "GA4 setup," "conversion tracking," "event setup," "User ID tracking," or "CTA attribution." For traffic insights, use traffic-analysis.
When the user wants to create, optimize, or audit the API introduction/overview page. Also use when the user mentions "API page," "API landing page," "/api page," "API overview," "developer landing," "API marketing," or "API for developers." Note: API documentation (endpoint reference) lives in docs; use docs-page-generator.
When the user wants to write, generate, or create article body content—blog post body, long-form content, how-to guide, listicle. Also use when the user mentions "write article," "article content," "blog post content," "article body," "long-form content creation," "generate article," "article draft," "how-to guide content," "listicle content," "information gain," or "content density." For single post page structure, schema, and SEO metadata, use article-page-generator. For blog index/listing page, use blog-page-generator. For short ad, landing, or email copy, use copywriting.