How to install distribution-channels
npx skills add https://github.com/kostja94/marketing-skills --skill distribution-channelsFull instructions (SKILL.md)
Source of truth, from kostja94/marketing-skills.
name: distribution-channels description: When the user wants to plan product distribution via marketplaces, app stores, or third-party platforms. Also use when the user mentions "distribution channels," "marketplace listing," "app store listing," "Figma plugin," "Chrome extension marketplace," "AWS Marketplace," "Shopify app," "GPTs store," "app distribution," or "third-party marketplace." For channel mix, use integrated-marketing. metadata: version: 1.1.1
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
Related skills
More from kostja94/marketing-skills and the wider catalog.
docs-page-generator
When the user wants to create, optimize, or structure a documentation site. Also use when the user mentions "docs," "documentation site," "docs subdomain," "docs.yourdomain.com," "help center," "knowledge base," "Getting Started," "API Reference," "user guides," or "tutorials." For API marketing landing, use api-page-generator.
domain-architecture
When the user wants to decide domain structure for multiple products or brands—subfolder vs subdomain vs independent domain. Also use when the user mentions "subfolder vs subdomain," "subdirectory vs subdomain," "multiple products domain," "multiple websites," "brand architecture," "branded house," "house of brands," "where to host product," "domain structure," or "hub-spoke domain." For brand SERP, use multi-domain-brand-seo.
domain-selection
When the user wants to choose an SEO-friendly domain for a new site—brand vs keyword domain, TLD selection, or domain best practices. Also use when the user mentions "domain choice," "pick domain," "SEO-friendly domain," "brand domain," "EMD," "PMD," "exact match domain," "partial match domain," "TLD," ".ai domain," ".com vs .io," "domain length," "domain history," or "defensive domain registration." For migration, use rebranding-strategy.
download-page-generator
When the user wants to create, optimize, or audit a download page for desktop or mobile app. Also use when the user mentions "download page," "app download," "desktop download," "mobile app download," "App Store," "Play Store," "get the app," "install app," or "download CTA." For app install ads, use app-ads.
education-program
When the user wants to plan, implement, or optimize student and education discount programs. Also use when the user mentions "student discount," "education discount," "student plan," "for students," ".edu discount," "academic pricing," "student verification," "SheerID," "UNiDAYS," or "education program." For startup pricing page, use startups-page-generator.
eeat-signals
When the user wants to improve E-E-A-T, add trust signals, or optimize for expertise and authority. Also use when the user mentions "E-E-A-T," "E-E-A-T signals," "experience expertise authority trust," "author bio," "YMYL," "trust signals," "expertise signals," "authority signals," "citations," "references," or "credibility." For headings, use heading-structure.