What it does
Build and scale developer-led adoption through ecosystem programs
Skills ZICQ category:Design 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.
Official URL:skills.sh
Intro in this page language first. The official description stays in its original wording; we do not rewrite SKILL.md.
Build and scale developer-led adoption through ecosystem programs
**Triggers:**
Per Agent Skills progressive disclosure: name and description load at startup (~100 tokens); the full SKILL.md body loads when the skill activates; scripts/, references/, and assets/ load only as needed. This file's sections: Developer Ecosystem; 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).
File analysis: instruction-only skill (SKILL.md). The agent loads the full body when activated.
Developer EcosystemWhen to UseCore Frameworks1. Open vs Curated Ecosystem (The Marketplace Decision)2. The Three-Year Student Program Arc3. Developer Journey (Awareness → Integration → Advocacy)4. Documentation Hierarchy5. Community vs Support (When to Use Which)6. Partner Tiering for Developer EcosystemsDecision TreesOpen or Curated Ecosystem?Community or Support?
· License:MIT
Source category:skills.sh agent-skill
namegtm-developer-ecosystemdescriptionInvocation syntax and available tools depend on your Agent client. Client integration guide ↗
Choose the target agent and installation scope, keep referenced package files, then verify the skill appears in the client's catalog.
Copy these instructions to a compatible agent and confirm the target directory matches your client.
Install the agent skill "gtm-developer-ecosystem" into my project. The full SKILL.md and official description are at https://zicq.com/en/skills/skl-b6be537f2fa86bcf-Gtm-Developer-Ecosystem.html Save it as .cursor/skills/gtm-developer-ecosystem/SKILL.md or .claude/skills/gtm-developer-ecosystem/SKILL.md and keep the frontmatter name and description exactly as-is.
Requires Node.js and npx. First inspect the repository's skill list to confirm the name.
npx skills add 'https://github.com/github/awesome-copilot' --list
npx skills add 'https://github.com/github/awesome-copilot' --skill 'gtm-developer-ecosystem'
The CLI lets you choose the agent interactively. The default scope is the project; use -g for user scope. Confirm package availability with the discovery command, then use npx skills list to inspect installed skills.
Build and scale developer-led adoption through ecosystem programs, community, and partnerships. Focus on what actually drives adoption, not vanity metrics.
Triggers:
Context:
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:
Result: Network effects won. Thousands of integrations published. Quality surfaced through usage, not through us deciding upfront.
Decision Framework:
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.
The Pattern:
Most developer programs optimize for quick wins. Better approach: Build long-term talent pipeline.
Year 1: University Partnerships
Year 2: Student Community & Certification
Year 3: Career Bridge
Why This Works:
Students become enterprise buyers 5-10 years later. You're building brand loyalty before they have purchasing power.
Common Mistake:
Treating students as immediate revenue. They're not. They're future enterprise decision-makers.
Stage 1: Awareness
Stage 2: Onboarding
Stage 3: Integration
Stage 4: Production
Stage 5: Advocacy
Metrics That Matter:
Common Mistake:
Measuring vanity metrics (sign-ups, downloads) instead of real engagement (API calls, production deployments).
Tier 1: Quick Starts (Get to Value Fast)
Tier 2: Guides (Solve Real Problems)
Tier 3: Reference (Complete API Docs)
Tier 4: Conceptual (Understand the System)
Most developers need: Tier 1 first, then Tier 2. Very few read Tier 4.
Common Mistake:
Starting with Tier 3 (comprehensive API reference). Developers want quick wins first.
Community (Async, Scalable):
Support (Sync, Expensive):
How to Route:
Community first:
Escalate to support when:
Common Mistake:
Providing white-glove support to everyone. Doesn't scale. Build community that helps itself.
Tier 1: Integration Partners (Self-Serve)
Tier 2: Strategic Partners (Co-Development)
Don't over-tier. 2 tiers is enough. More creates confusion.
Is brand damage risk high if low-quality partners join?
├─ Yes (regulated, security) → Curated
└─ No → Continue...
│
Can you scale human review?
├─ No (hundreds/thousands) → Open + discovery systems
└─ Yes (dozens) → Curated
Is this a common question?
├─ Yes → Community (forum, Slack, docs)
└─ No → Continue...
│
Is requester paying customer?
├─ Yes → Support (email, dedicated)
└─ No → Community (with escalation path)
1. Building ecosystem before product-market fit
2. No developer success team
3. Poor documentation
4. Treating all developers equally
5. No integration quality standards
6. Measuring only vanity metrics
7. Developer advocates with no technical depth
Open ecosystem checklist:
Developer journey metrics:
Documentation hierarchy:
Partner tiers:
Student program timeline:
Based on building developer ecosystems at multiple platform companies, including the open vs curated marketplace decision, student program development (3-year arc building talent pipeline), and partner ecosystem growth. Not theory — patterns from building developer ecosystems that actually drove platform adoption and multi-year brand loyalty.
Design
Design and implement automation workflows to save time and scale operations as a solopreneur. Use when identifying repetitive tasks to autom…
Design
UI/UX design intelligence and implementation guidance for building polished interfaces. Use when the user asks for UI design, UX flows, info…
Design
Expert frontend design guidelines for creating beautiful, modern UIs. Use when building landing pages, dashboards, or any user interface.
Design
Designs and outputs n8n workflow JSON with robust triggers, idempotency, error handling, logging, retries, and human-in-the-loop review queu…