samber/developer-relations-skills
open-source-company-strategy
Decides what a company open-sources and what stays proprietary, names the strategic motive for each side of the line, says who owns the decision, and states what the company commits never to close. Use whenever someone asks "should we open source this?", "what should we open source", "where do we draw the open-core line", "which features stay paid", "who signs off on open sourcing this", or wants a company-level open source strategy rather than a plan for one project - even if they frame it as a licensing question. Produces an asset-by-asset open/closed verdict, a value-capture and irreversibility check, a public non-reversal commitment and a re-evaluation trigger. Not license selection - use samber/developer-relations-skills@oss-license-strategy.
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.
Design test strategies and test plans. Trigger with "how should we test", "test strategy for", …
15 installsQuery decomposition and multi-source search orchestration. Breaks natural language questions in…
5.3K installsFind and own a defensible market position.
1.9K installsAnalyzes sales data from PayPal and QuickBooks to find top performers and slow movers, layers i…
1.7K installsAnalyze the interest rate swap curve by pricing swaps at multiple tenors, overlaying government…
1.6K installsWhen the user wants to plan a content strategy, decide what content to create, or figure out wh…
617 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.