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.
Profile →npx skills add github/awesome-copilot --skill gtm-developer-ecosystem --agent copilot
Same command for any agent — swap --agent for claude-code, codex, cursor.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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
- When to Use
- Core Frameworks
- 1. Open vs Curated Ecosystem (The Marketplace Decision)
- 2. The Three-Year Student Program Arc
- 3. Developer Journey (Awareness → Integration → Advocacy)
- 4. Documentation Hierarchy
- 5. Community vs Support (When to Use Which)
- 6. Partner Tiering for Developer Ecosystems
- Decision Trees
- Open or Curated Ecosystem?
- Community or Support?
- Common Mistakes
- Quick Reference
- Related Skills
What does the gtm-developer-ecosystem skill do?
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.
How do I install it?
Run `npx skills add github/awesome-copilot --skill gtm-developer-ecosystem --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From github/awesome-copilot, a repository with 37,432 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.