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 analyze Google Search Console data, use the GSC API, or interpret search performance. Also use when the user mentions "GSC," "Search Console," "indexing report," "Core Web Vitals," "Enhancements," "Insights report," "search performance," "search queries," "search performance report," "URL inspection," "impressions," "CTR," "average position," "index coverage," "GSC data analysis," "Search Console API," or "searchanalytics.query." When the user wants to rewrite title tags (not only report on them), use title-tag. For meta description rewrites, use meta-description.
When the user wants to build an SEO data analysis system, monitor indexing/traffic/keywords/backlinks, or set up benchmarks. Also use when the user mentions "SEO data analysis," "SEO monitoring," "article database," "traffic benchmark," "penalty recovery," "SEO work document," "SEO dashboard," "keyword tracking," "ranking monitoring," "indexing report," or "backlink monitoring." For GSC API, use google-search-console.
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 analyze website traffic sources, attribution, or dark traffic. Also use when the user mentions "traffic sources," "dark traffic," "direct traffic," "UTM parameters," "traffic attribution," "channel attribution," "attribution optimization," "channel analysis," "traffic analysis," "traffic diversification," "natural traffic benchmark," or "organic vs paid traffic." For GA4 setup, use analytics-tracking.
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 promote via forums, communities, or invite users to join a community. Also use when the user mentions "forum promotion," "Indie Hacker," "Hacker News," "community growth," "Discord promotion," "vertical community," "brand encyclopedia," "Wikipedia," "Quora," "Reddit community," "community building," "forum marketing," or "community invite." For Reddit copy, use reddit-posts. For strategy, use integrated-marketing.
When the user wants to submit a product or app to directories, curated lists, launch platforms, or app stores—and needs ready-to-paste copy per platform. Reads project-context.md when present. Also use when the user mentions "directory submission," "get listed," "app store listing," "submit to directories," "curated list," "best tools list," "Taaft," "Product Hunt," "directory ads," "newsletter feature," "directory campaign," "tailor description per platform," "Shopify App Store," "Chrome Web Store," "navigation site," or "product directory." For Product Hunt launch day tactics (hunter, first comment, timing), use product-hunt-launch. For full 0→1 channel planning, use cold-start-strategy.
When the user wants to launch on Product Hunt, prepare a PH submission, or plan launch day (hunter, first comment, timing, upvotes). Also use when the user mentions "Product Hunt," "launch on Product Hunt," "PH launch," "Product Hunt submission," "hunter," "Product of the Day," "upvotes," or "Product Hunt first comment." For multi-platform directory listings and paste-ready copy beyond PH, use directory-submission.