Agent skill · marketing growth · github
gtm-developer-ecosystem
Build and scale developer-led adoption through ecosystem programs. Use when deciding open vs curated ecosystems, building developer programs, scaling platform adoption, or designing student program pipelines.
Why this skill is useful
Provides a structured framework for building developer ecosystems that includes niche strategies and decision-making processes not commonly found in public resources.
What it needs
About 5k tokens when loaded. Last updated 2026-08-07. 37,534 stars on the source repository.
What this skill does
Developer Ecosystem Build and scale developer-led adoption through ecosystem programs, community, and partnerships. Focus on what actually drives adoption, not vanity metrics. When to Use Triggers: "How do we build a developer ecosystem?" "Should we curate quality or go open?" "Developer community isn't growing" "Nobody's building on our API" "How do we compete with larger platforms?" Context: API platforms and developer tools Products with extensibility (plugins, integrations) Developer-first GTM motion Platform business models --- Core Frameworks 1. Open vs Curated Ecosystem (The Marketplace Decision) The Pattern: Running ecosystem at a developer platform. Leadership debate: Open the marketplace to anyone, or curate for quality? Quality control camp: "We need gatekeeping. Otherwise we'll get SEO spam, low-quality integrations, brand damage." Open camp: "Developers route around gatekeepers. Network effects matter more than quality control." The decision: Went open. Quality concerns were real, but we made a bet: control comes from discovery and trust layers, not submission gatekeeping. What We Built Instead of Gatekeeping: 1. Search and discovery — Surface high-quality integrations through algorithms, not human curation 2. Trust signals — Verified badges, usage stats, health scores 3. Community curation — User ratings, collections, recommendations 4. Moderation — Remove spam after publication, not block before Result: Network effects won. Thousands of integrations published. Quality surfaced through usage, not through us deciding upfront. Decision Framework: Curated works when: Brand risk high, dozens of partners, can scale human review Open works when: Hundreds/thousands of potential partners, network effects matter more than quality control Common Mistake: Defaulting to curated because "we need quality control." This works when you have 10 partners. At 100+, you become the bottleneck. Build discovery and trust systems instead. --- 2. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills github/gtm-developer-ecosystem