| name | open-source-marketing |
| description | When the user wants to market an open source project authentically. Trigger phrases include "open source marketing," "OSS marketing," "GitHub marketing," "promote my library," "grow stars," "launch open source," "open source growth," or "contributor marketing." |
| risk | unknown |
| source | https://github.com/jonathimer/devmarketing-skills/tree/main/skills/open-source-marketing |
| source_repo | jonathimer/devmarketing-skills |
| source_type | community |
| date_added | 2026-07-01T00:00:00.000Z |
| license | MIT |
| license_source | https://github.com/jonathimer/devmarketing-skills/blob/main/LICENSE |
Open Source Marketing
When to Use
Use this skill when you need when the user wants to market an open source project authentically. Trigger phrases include "open source marketing," "OSS marketing," "GitHub marketing," "promote my library," "grow stars," "launch open source," "open source growth," or "contributor marketing.".
This skill helps you market open source projects without being cringe. Covers GitHub optimization, community building, contributor experience, launch strategies, and sustainable growth.
Before You Start
Load your audience context first. Read .agents/developer-audience-context.md to understand:
- Who would use this project (role, tech stack, problem)
- Where they discover tools (communities, social, search)
- What alternatives exist (why would they switch?)
- How they evaluate OSS (stars, activity, docs, community)
If the context file doesn't exist, run the developer-audience-context skill first.
The OSS Marketing Mindset
What Works vs. What Doesn't
| Works | Doesn't Work |
|---|
| Building in public | Spamming "check out my project" |
| Solving real problems | Building solutions seeking problems |
| Genuine community engagement | Transactional follows/unfollows |
| Great docs and DX | "The code is self-documenting" |
| Celebrating contributors | Taking sole credit |
| Consistent presence | Launch and disappear |
The Growth Equation
Growth = (Real value) × (Discoverability) × (First-use experience)
If any factor is zero, growth is zero.
GitHub Optimization
README Excellence
Your README is your landing page. Optimize it.
Structure:
# Project Name
[One-line description that explains what it does]
[Badges: build status, version, license, downloads]
[Screenshot or GIF showing it in action]
## Why [Project Name]?
- ✅ [Benefit 1 - specific, not fluffy]
- ✅ [Benefit 2]
- ✅ [Benefit 3]
\\`bash
npm install project-name
\\`
\\`javascript
// 5 lines that show immediate value
\\`
[Detailed installation for all platforms]
[Core usage patterns with examples]
[Link to full docs]
We love contributions! See []().
[] - see []()
