{"id":"f3400171-f4e2-4bf9-af63-a571d733a792","shortId":"xVxY7J","kind":"skill","title":"developer-ecosystem","tagline":"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.","description":"# Developer Ecosystem\n\nBuild and scale developer-led adoption through ecosystem programs, community, and partnerships. Focus on what actually drives adoption, not vanity metrics.\n\n## When to Use\n\n**Triggers:**\n- \"How do we build a developer ecosystem?\"\n- \"Should we curate quality or go open?\"\n- \"Developer community isn't growing\"\n- \"Nobody's building on our API\"\n- \"How do we compete with larger platforms?\"\n\n**Context:**\n- API platforms and developer tools\n- Products with extensibility (plugins, integrations)\n- Developer-first GTM motion\n- Platform business models\n\n---\n\n## Core Frameworks\n\n### 1. Open vs Curated Ecosystem (The Marketplace Decision)\n\n**The Pattern:**\n\nRunning ecosystem at a developer platform. Leadership debate: Open the marketplace to anyone, or curate for quality?\n\n**Quality control camp:** \"We need gatekeeping. Otherwise we'll get SEO spam, low-quality integrations, brand damage.\"\n\n**Open camp:** \"Developers route around gatekeepers. Network effects matter more than quality control.\"\n\n**The decision:** Went open. Quality concerns were real, but we made a bet: control comes from discovery and trust layers, not submission gatekeeping.\n\n**What We Built Instead of Gatekeeping:**\n\n1. **Search and discovery** — Surface high-quality integrations through algorithms, not human curation\n2. **Trust signals** — Verified badges, usage stats, health scores\n3. **Community curation** — User ratings, collections, recommendations\n4. **Moderation** — Remove spam after publication, not block before\n\n**Result:** Network effects won. Thousands of integrations published. Quality surfaced through usage, not through us deciding upfront.\n\n**Decision Framework:**\n- **Curated** works when: Brand risk high, dozens of partners, can scale human review\n- **Open** works when: Hundreds/thousands of potential partners, network effects matter more than quality control\n\n**Common Mistake:**\n\nDefaulting 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.\n\n---\n\n### 2. The Three-Year Student Program Arc\n\n**The Pattern:**\n\nMost developer programs optimize for quick wins. Better approach: Build long-term talent pipeline.\n\n**Year 1: University Partnerships**\n- Partner with CS departments\n- Curriculum integration (hackathons, coursework)\n- Student licenses (free or heavily discounted)\n- Metrics: # universities, # students activated\n\n**Year 2: Student Community & Certification**\n- Student expert certification program\n- Student-led workshops and events\n- Campus ambassadors\n- Metrics: # certified, # student-led events\n\n**Year 3: Career Bridge**\n- Job board connecting students → companies\n- Enterprise partnerships (hire certified students)\n- Alumni network\n- Metrics: # hired, company partnerships\n\n**Why This Works:**\n\nStudents become enterprise buyers 5-10 years later. You're building brand loyalty before they have purchasing power.\n\n**Common Mistake:**\n\nTreating students as immediate revenue. They're not. They're future enterprise decision-makers.\n\n---\n\n### 3. Developer Journey (Awareness → Integration → Advocacy)\n\n**Stage 1: Awareness**\n- How do they discover you?\n- Content, search, word-of-mouth, events\n\n**Stage 2: Onboarding**\n- First API call in <10 minutes\n- Quick-start guides\n- Sample code in popular languages\n\n**Stage 3: Integration**\n- Building real use cases\n- Integration guides\n- Support when stuck\n\n**Stage 4: Production**\n- Deployed and generating value\n- Monitoring usage\n- Enterprise upgrade path\n\n**Stage 5: Advocacy**\n- Sharing publicly\n- Recommending to others\n- Contributing back (docs, code, community)\n\n**Metrics That Matter:**\n- Time to first API call (onboarding)\n- % reaching production (integration success)\n- Monthly active developers (engagement)\n- Developer NPS (advocacy)\n\n**Common Mistake:**\n\nMeasuring vanity metrics (sign-ups, downloads) instead of real engagement (API calls, production deployments).\n\n---\n\n### 4. Documentation Hierarchy\n\n**Tier 1: Quick Starts (Get to Value Fast)**\n- \"Hello World\" in 5 minutes\n- Common use case examples\n- Copy-paste code that works\n\n**Tier 2: Guides (Solve Real Problems)**\n- Use case-specific tutorials\n- Integration patterns\n- Best practices\n\n**Tier 3: Reference (Complete API Docs)**\n- Every endpoint documented\n- Request/response examples\n- Error codes and handling\n\n**Tier 4: Conceptual (Understand the System)**\n- Architecture overviews\n- Design philosophy\n- Advanced patterns\n\n**Most developers need:** Tier 1 first, then Tier 2. Very few read Tier 4.\n\n**Common Mistake:**\n\nStarting with Tier 3 (comprehensive API reference). Developers want quick wins first.\n\n---\n\n### 5. Community vs Support (When to Use Which)\n\n**Community (Async, Scalable):**\n- Slack/Discord for real-time help\n- Forum for searchable Q&A\n- GitHub discussions for feature requests\n- Best for: Common questions, peer-to-peer help\n\n**Support (Sync, Expensive):**\n- Email support for enterprise\n- Dedicated Slack channels for partners\n- Video calls for complex integrations\n- Best for: Paying customers, strategic partners\n\n**How to Route:**\n\n**Community first:**\n- Developer asks question\n- Community member answers\n- You validate and upvote\n- Searchable for future developers\n\n**Escalate to support when:**\n- No community answer in 24 hours\n- Enterprise/paying customer\n- Security or compliance issue\n- Complex integration requiring custom work\n\n**Common Mistake:**\n\nProviding white-glove support to everyone. Doesn't scale. Build community that helps itself.\n\n---\n\n### 6. Partner Tiering for Developer Ecosystems\n\n**Tier 1: Integration Partners (Self-Serve)**\n- Build with public API\n- You provide: docs, Slack channel, office hours\n- They drive their own marketing\n- Best for: Ambitious partners with resources\n\n**Tier 2: Strategic Partners (Co-Development)**\n- Co-developed integration\n- You provide: dedicated channel, co-marketing\n- Joint case studies\n- Best for: High-impact integrations\n\n**Don't over-tier.** 2 tiers is enough. More creates confusion.\n\n---\n\n## Decision Trees\n\n### Open or Curated Ecosystem?\n\n```\nIs brand damage risk high if low-quality partners join?\n├─ Yes (regulated, security) → Curated\n└─ No → Continue...\n    │\n    Can you scale human review?\n    ├─ No (hundreds/thousands) → Open + discovery systems\n    └─ Yes (dozens) → Curated\n```\n\n### Community or Support?\n\n```\nIs this a common question?\n├─ Yes → Community (forum, Slack, docs)\n└─ No → Continue...\n    │\n    Is requester paying customer?\n    ├─ Yes → Support (email, dedicated)\n    └─ No → Community (with escalation path)\n```\n\n---\n\n## Common Mistakes\n\n**1. Building ecosystem before product-market fit**\n   - Fix core product first, then build ecosystem\n\n**2. No developer success team**\n   - Developers need help to succeed beyond docs\n\n**3. Poor documentation**\n   - Foundation of ecosystem, non-negotiable\n\n**4. Treating all developers equally**\n   - Tier support by strategic value (paying > free, partners > hobbyists)\n\n**5. No integration quality standards**\n   - Low-quality integrations hurt your brand\n\n**6. Measuring only vanity metrics**\n   - Track activation and production usage, not just sign-ups\n\n**7. Developer advocates with no technical depth**\n   - Hire developers who can code and teach\n\n---\n\n## Quick Reference\n\n**Open ecosystem checklist:**\n- [ ] Search and discovery (surface quality algorithmically)\n- [ ] Trust signals (verified badges, usage stats, ratings)\n- [ ] Community curation (user recommendations, collections)\n- [ ] Moderation (remove spam after publication)\n\n**Developer journey metrics:**\n- Awareness: Traffic, sign-ups\n- Onboarding: Time to first API call (<10 min target)\n- Integration: % reaching production deployment\n- Advocacy: Developer NPS, public sharing\n\n**Documentation hierarchy:**\n1. Quick starts (5-min \"Hello World\")\n2. Use case guides (solve real problems)\n3. API reference (complete documentation)\n4. Conceptual (architecture, philosophy)\n\n**Partner tiers:**\n- Tier 1: Self-serve (public API, docs, community)\n- Tier 2: Strategic (co-development, co-marketing)\n\n**Student program timeline:**\n- Year 1: University partnerships, activation\n- Year 2: Certification, student community\n- Year 3: Job board, enterprise hiring bridge\n\n---\n\n## Related Skills\n\n- **partnership-architecture**: Partner deal structures and co-marketing\n- **product-led-growth**: Self-serve activation funnels for developer products\n- **0-to-1-launch**: Launching developer products\n\n---\n\n*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.*","tags":["developer","ecosystem","technical","product","gtm","beingsmit","agent-skills","ai-founders","ai-gtm","claude-code","claude-plugin","claude-skills"],"capabilities":["skill","source-beingsmit","skill-developer-ecosystem","topic-agent-skills","topic-ai-founders","topic-ai-gtm","topic-claude-code","topic-claude-plugin","topic-claude-skills","topic-developer-relations","topic-devrel","topic-ecosystems","topic-enterprise-ai","topic-enterprise-sales","topic-founder-tools"],"categories":["technical-product-gtm"],"synonyms":[],"warnings":[],"endpointUrl":"https://skills.sh/beingsmit/technical-product-gtm/developer-ecosystem","protocol":"skill","transport":"skills-sh","auth":{"type":"none","details":{"cli":"npx skills add beingsmit/technical-product-gtm","source_repo":"https://github.com/beingsmit/technical-product-gtm","install_from":"skills.sh"}},"qualityScore":"0.466","qualityRationale":"deterministic score 0.47 from registry signals: · indexed on github topic:agent-skills · 32 github stars · SKILL.md body (8,835 chars)","verified":false,"liveness":"unknown","lastLivenessCheck":null,"agentReviews":{"count":0,"score_avg":null,"cost_usd_avg":null,"success_rate":null,"latency_p50_ms":null,"narrative_summary":null,"summary_updated_at":null},"enrichmentModel":"deterministic:skill-github:v1","enrichmentVersion":1,"enrichedAt":"2026-05-01T12:57:22.575Z","embedding":null,"createdAt":"2026-04-18T22:22:15.295Z","updatedAt":"2026-05-01T12:57:22.575Z","lastSeenAt":"2026-05-01T12:57:22.575Z","tsv":"'-1':1143 '-10':412 '0':1141 '1':113,200,340,449,559,627,774,907,1054,1080,1101 '10':300,470,1040 '100':303 '2':214,314,362,464,582,631,803,834,922,1061,1089,1106 '24':737 '3':223,385,442,482,597,642,934,1068,1111,1167 '4':230,494,555,612,636,943,1073 '5':411,506,569,651,957,1057 '6':767,969 '7':984 'activ':360,532,975,1104,1136 'actual':50,1185 'adopt':10,26,40,52,1188 'advanc':621 'advoc':986 'advocaci':447,507,537,1047 'algorithm':210,1008 'alumni':398 'ambassador':377 'ambiti':798 'answer':720,735 'anyon':135 'api':84,93,467,524,551,600,644,783,1038,1069,1085 'approach':332 'arc':321,1169 'architectur':617,1075,1121 'around':162 'ask':716 'async':660 'awar':445,450,1029 'back':514 'badg':218,1012 'base':1148 'becom':305,408 'best':594,678,704,796,823 'bet':183 'better':331 'beyond':932 'block':237 'board':389,1113 'bottleneck':307 'brand':156,261,418,848,968,1193 'bridg':387,1116 'build':4,21,34,63,81,308,333,417,484,762,780,908,920,1150,1170,1181 'built':196 'busi':109 'buyer':410 'call':468,525,552,700,1039 'camp':142,159 'campus':376 'career':386 'case':487,573,589,821,1063 'case-specif':588 'certif':365,368,1107 'certifi':379,396 'channel':696,788,816 'checklist':1002 'co':807,810,818,1092,1095,1127 'co-develop':806,809,1091 'co-market':817,1094,1126 'code':477,516,578,608,995 'collect':228,1020 'come':185 'common':285,425,538,571,637,680,750,883,905 'communiti':44,75,224,364,517,652,659,713,718,734,763,877,886,901,1016,1087,1109 'compani':392,402,1156 'compet':88 'complet':599,1071 'complex':702,745 'complianc':743 'comprehens':643 'conceptu':613,1074 'concern':176 'confus':840 'connect':390 'content':456 'context':92 'continu':863,891 'contribut':513 'control':141,170,184,284,294 'copi':576 'copy-past':575 'core':111,916 'coursework':350 'creat':839 'cs':345 'curat':19,69,116,137,213,225,258,289,845,861,876,1017,1161 'curriculum':347 'custom':707,740,748,895 'damag':157,849 'deal':1123 'debat':130 'decid':16,254 'decis':120,172,256,440,841,1163 'decision-mak':439 'dedic':694,815,899 'default':287 'depart':346 'deploy':496,554,1046 'depth':990 'design':28,619 'develop':2,8,22,32,38,65,74,96,104,127,160,325,443,533,535,624,646,715,728,771,808,811,924,927,946,985,992,1026,1048,1093,1139,1146,1151,1166,1182 'developer-ecosystem':1 'developer-first':103 'developer-l':7,37 'discount':356 'discov':454 'discoveri':187,203,309,872,1005 'discuss':674 'doc':515,601,786,889,933,1086 'document':556,604,936,1052,1072 'doesn':759 'download':546 'dozen':264,875 'drive':51,792 'drove':1186 'ecosystem':3,12,20,33,42,66,117,124,772,846,909,921,939,1001,1152,1175,1183 'effect':165,241,279 'email':690,898 'endpoint':603 'engag':534,550 'enough':837 'enterpris':393,409,438,502,693,1114 'enterprise/paying':739 'equal':947 'error':607 'escal':729,903 'event':375,383,462 'everi':602 'everyon':758 'exampl':574,606 'expens':689 'expert':367 'extens':100 'fast':565 'featur':676 'first':105,466,523,628,650,714,918,1037 'fit':914 'fix':915 'focus':47 'forum':668,887 'foundat':937 'framework':112,257 'free':353,954 'funnel':1137 'futur':437,727 'gatekeep':145,163,193,199 'generat':498 'get':149,562 'github':673 'glove':755 'go':72 'grow':78 'growth':1132,1176 'gtm':106 'guid':475,489,583,1064 'hackathon':349 'handl':610 'health':221 'heavili':355 'hello':566,1059 'help':667,686,765,929 'hierarchi':557,1053 'high':206,263,826,851 'high-impact':825 'high-qual':205 'hire':395,401,991,1115 'hobbyist':956 'hour':738,790 'human':212,269,867 'hundreds/thousands':274,870 'hurt':966 'immedi':430 'impact':827 'includ':1157 'instead':197,313,547 'integr':102,155,208,245,348,446,483,488,529,592,703,746,775,812,828,959,965,1043 'isn':76 'issu':744 'job':388,1112 'join':857 'joint':820 'journey':444,1027 'languag':480 'larger':90 'later':414 'launch':1144,1145 'layer':190 'leadership':129 'led':9,39,372,382,1131 'licens':352 'll':148 'long':335 'long-term':334 'low':153,854,963 'low-qual':152,853,962 'loyalti':419,1194 'made':181 'maker':441 'market':795,819,913,1096,1128 'marketplac':119,133,1162 'matter':166,280,520 'measur':540,970 'member':719 'metric':55,357,378,400,518,542,973,1028 'min':1041,1058 'minut':471,570 'mistak':286,426,539,638,751,906 'model':110 'moder':231,1021 'monitor':500 'month':531 'motion':107 'mouth':461 'multi':1191 'multi-year':1190 'multipl':1154 'need':144,292,625,928 'negoti':942 'network':164,240,278,399 'nobodi':79 'non':941 'non-negoti':940 'nps':536,1049 'offic':789 'onboard':465,526,1034 'open':17,73,114,131,158,174,271,843,871,1000,1159 'optim':327 'other':512 'otherwis':146 'over-ti':831 'overview':618 'partner':266,277,301,343,698,709,768,776,799,805,856,955,1077,1122,1174 'partnership':46,342,394,403,1103,1120 'partnership-architectur':1119 'past':577 'path':504,904 'pattern':122,323,593,622,1179 'pay':706,894,953 'peer':683,685 'peer-to-p':682 'philosophi':620,1076 'pipelin':31,338,1172 'platform':25,91,94,108,128,1155,1187 'plugin':101 'poor':935 'popular':479 'potenti':276 'power':424 'practic':595 'problem':586,1067 'product':98,495,528,553,912,917,977,1045,1130,1140,1147 'product-led-growth':1129 'product-market':911 'program':13,23,30,43,320,326,369,1098,1165 'provid':752,785,814 'public':235,509,782,1025,1050,1084 'publish':246 'purchas':423 'q':671 'qualiti':70,139,140,154,169,175,207,247,283,293,855,960,964,1007 'question':681,717,884 'quick':329,473,560,648,998,1055 'quick-start':472 'rate':227,1015 're':416,433,436 'reach':527,1044 'read':634 'real':178,485,549,585,665,1066 'real-tim':664 'recommend':229,510,1019 'refer':598,645,999,1070 'regul':859 'relat':1117 'remov':232,1022 'request':677,893 'request/response':605 'requir':747 'resourc':801 'result':239 'revenu':431 'review':270,868 'risk':262,850 'rout':161,712 'run':123 'sampl':476 'scalabl':661 'scale':6,24,36,268,761,866 'score':222 'search':201,457,1003 'searchabl':670,725 'secur':741,860 'self':778,1082,1134 'self-serv':777,1081,1133 'seo':150 'serv':779,1083,1135 'share':508,1051 'sign':544,982,1032 'sign-up':543,981,1031 'signal':216,1010 'skill':1118 'skill-developer-ecosystem' 'slack':695,787,888 'slack/discord':662 'solv':584,1065 'source-beingsmit' 'spam':151,233,1023 'specif':590 'stage':448,463,481,493,505 'standard':961 'start':474,561,639,1056 'stat':220,1014 'strateg':708,804,951,1090 'structur':1124 'stuck':492 'student':29,319,351,359,363,366,371,381,391,397,407,428,1097,1108,1164 'student-l':370,380 'studi':822 'submiss':192 'succeed':931 'success':530,925 'support':490,654,687,691,731,756,879,897,949 'surfac':204,248,1006 'sync':688 'system':312,616,873 'talent':337,1171 'target':1042 'teach':997 'team':926 'technic':989 'term':336 'theori':1178 'thousand':243 'three':317 'three-year':316 'tier':558,581,596,611,626,630,635,641,769,773,802,833,835,948,1078,1079,1088 'time':521,666,1035 'timelin':1099 'tool':97 'topic-agent-skills' 'topic-ai-founders' 'topic-ai-gtm' 'topic-claude-code' 'topic-claude-plugin' 'topic-claude-skills' 'topic-developer-relations' 'topic-devrel' 'topic-ecosystems' 'topic-enterprise-ai' 'topic-enterprise-sales' 'topic-founder-tools' 'track':974 'traffic':1030 'treat':427,944 'tree':842 'trigger':59 'trust':189,215,311,1009 'tutori':591 'understand':614 'univers':341,358,1102 'up':545,983,1033 'upfront':255 'upgrad':503 'upvot':724 'us':253 'usag':219,250,501,978,1013 'use':14,58,486,572,587,657,1062 'user':226,1018 'valid':722 'valu':499,564,952 'vaniti':54,541,972 'verifi':217,1011 'video':699 'vs':18,115,653,1160 'want':647 'went':173 'white':754 'white-glov':753 'win':330,649 'won':242 'word':459 'word-of-mouth':458 'work':259,272,296,406,580,749 'workshop':373 'world':567,1060 'year':318,339,361,384,413,1100,1105,1110,1168,1192 'yes':858,874,885,896","prices":[{"id":"3905f2a0-289a-4e3a-8102-badc9d96de25","listingId":"f3400171-f4e2-4bf9-af63-a571d733a792","amountUsd":"0","unit":"free","nativeCurrency":null,"nativeAmount":null,"chain":null,"payTo":null,"paymentMethod":"skill-free","isPrimary":true,"details":{"org":"beingsmit","category":"technical-product-gtm","install_from":"skills.sh"},"createdAt":"2026-04-18T22:22:15.295Z"}],"sources":[{"listingId":"f3400171-f4e2-4bf9-af63-a571d733a792","source":"github","sourceId":"beingsmit/technical-product-gtm/developer-ecosystem","sourceUrl":"https://github.com/beingsmit/technical-product-gtm/tree/main/skills/developer-ecosystem","isPrimary":false,"firstSeenAt":"2026-04-18T22:22:15.295Z","lastSeenAt":"2026-05-01T12:57:22.575Z"}],"details":{"listingId":"f3400171-f4e2-4bf9-af63-a571d733a792","quickStartSnippet":null,"exampleRequest":null,"exampleResponse":null,"schema":null,"openapiUrl":null,"agentsTxtUrl":null,"citations":[],"useCases":[],"bestFor":[],"notFor":[],"kindDetails":{"org":"beingsmit","slug":"developer-ecosystem","github":{"repo":"beingsmit/technical-product-gtm","stars":32,"topics":["agent-skills","ai-founders","ai-gtm","claude-code","claude-plugin","claude-skills","developer-relations","devrel","ecosystems","enterprise-ai","enterprise-sales","founder-tools","go-to-market","gtm","gtmai-developers","operators","partnerships","pricing-strategy","product-led-growth","startups"],"license":"mit","html_url":"https://github.com/beingsmit/technical-product-gtm","pushed_at":"2026-03-20T11:25:13Z","description":"11 go-to-market skills for AI and technical founders — positioning, pricing, partnerships, enterprise sales, PLG, AI GTM, and board communication.","skill_md_sha":"fc40e76236a801f8accd031a7b1a66f2e12b4759","skill_md_path":"skills/developer-ecosystem/SKILL.md","default_branch":"main","skill_tree_url":"https://github.com/beingsmit/technical-product-gtm/tree/main/skills/developer-ecosystem"},"layout":"multi","source":"github","category":"technical-product-gtm","frontmatter":{"name":"developer-ecosystem","license":"MIT","description":"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."},"skills_sh_url":"https://skills.sh/beingsmit/technical-product-gtm/developer-ecosystem"},"updatedAt":"2026-05-01T12:57:22.575Z"}}