samber/developer-relations-skills
developer-ecosystem-strategy
Decides whether, when and how far a developer product should open into a platform other companies build on - extension points, partner-built integrations, third-party apps, a complement ecosystem - and what that permanently obliges you to. Use whenever someone asks if the product should become a platform, whether to open extension points or an app model to third parties, how to start an integration ecosystem, why nobody builds on the API, whether partners should build the connectors, or how much value complementors must keep - even if they only say "we want an integrations story". Not marketplace operations or API design. Do NOT use for the revenue model - use samber/developer-relations-skills@devtools-business-model.
Installation
npx skills add https://github.com/samber/developer-relations-skills
Similar popular skills
Related neighbors and high-traction skills in the same topics — useful to compare before installing.
Search issues, merged pull requests, READMEs, and documentation. Use when the question is how a…
105 installsDevelop, debug, and manage Temporal applications across Python, TypeScript, Go, Java, .NET, Rub…
35 installsModify, build, test, debug, and contribute to NVIDIA cuOpt (C++/CUDA, Python, server, CI). Use …
2.7K installsSearch issues, merged pull requests, READMEs, and documentation. Use when the question is how a…
26 installsBuild and scale developer-led adoption through ecosystem programs. Use when deciding open vs cu…
1.5K installsGenerates Angular code and provides architectural guidance. Trigger when creating projects, com…
266 installsAlso in this package
Other skills from samber/developer-relations-skills · top by installs.
npx skills add samber/developer-relations-skills
More details
Agent compatibility
Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.