oss-strategy
Skill3 starsChanged 30 days agoMITView on GitHub
Evaluate an open-source business and community strategy. Triggers on "open source strategy", "OSS 策略".
In this repository49 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- brainstormSkill
- specSkill
- researchSkill
- api-designSkill
- architectureSkill
- codebase-designSkill
- design-researchSkill
- domain-modelingSkill
- frontend-designSkill
- imagegenSkill
- image-to-codeSkill
- prompt-engineeringSkill
- prototypeSkill
- schema-designSkill
- auth-implementationSkill
- breakdownSkill
- context-engineeringSkill
- error-handlingSkill
- i18nSkill
- implementSkill
- multi-agent-orchestrationSkill
- cost-optimizationSkill
- performanceSkill
- refactoringSkill
- simplifySkill
- api-testingSkill
- e2e-testingSkill
- load-testingSkill
- tddSkill
- test-generationSkill
- a11y-reviewSkill
- code-reviewSkill
- debuggingSkill
- lintingSkill
- security-reviewSkill
- ci-cdSkill
- deprecation-migrationSkill
- git-workflowSkill
- oss-polishSkill
- shippingSkill
- documentation-auditSkill
- handoffSkill
- incident-responseSkill
- observabilitySkill
- purity-auditSkill
- skill-authoringSkill
- using-skillsSkill
The file
Files
Open Source Strategy
When to use
- Evaluate an open-source business and community strategy.
Not for: oss-polish for repository presentation.
Steps
- Identify users, buyer, maintenance capacity and commercialization constraints.
- Compare suitable business models against current primary evidence; avoid universal revenue ratios or launch-time claims.
- Distinguish open-source licenses from source-available restrictions; verify obligations and leave adoption to the user.
- Propose a bounded distribution experiment with success and stop criteria, costs and uncertainties.
Output: Suggested paths, subject to human audit: docs/research/strategy.md when durable strategy is requested.
Verify
- Recommendation matches real resources; license and commercial claims are sourced and adoption is explicit.
References
- engineering-principles.md — shared decision boundaries, scope and verification.
- product-principles.md — product discipline (opportunity = demand × giant blind spot ÷ difficulty, the real competitor is the current workaround).
- human-audit.md — document consent, readability and human review.
- references/commercialization-models.md — general pricing (subscription/freemium/usage/per-seat), value-based pricing, AI-product pricing trap, GTM motions (PLG/sales-led/product-led sales), indie-developer revenue ladder.
- GitHub README/Topics/About beautification:
08-ship/oss-polish.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.