Developer Ecosystem Strategy

samber/developer-relations-skills/skills/developer-ecosystem-strategy

by samber98ed86da8babMIT2 starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated 10 days ago

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.

Instructions onlyBusiness & Finance

Only the file list is public. File contents are available once the skill is installed in a workspace.

PathSizeType
evals/evals.json33.2 KBapplication/json
references/ecosystem-memo-example.md8.5 KBtext/markdown
references/ecosystem-readiness-gates.md6.2 KBtext/markdown
references/extension-surface-ladder.md4.4 KBtext/markdown
SKILL.md26 KBtext/markdown

Source and attribution

Source:samber/developer-relations-skillsinskills/developer-ecosystem-strategyat commit98ed86d

License: MIT

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal