Market open source projects authentically and grow contributors

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

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]

### Quick Start

\`\`\`bash
npm install project-name
\`\`\`

\`\`\`javascript
// 5 lines that show immediate value
\`\`\`

### Installation

[Detailed installation for all platforms]

### Usage

[Core usage patterns with examples]

### Documentation

[Link to full docs]

### README Checklist

| Element | Why It Matters |
|---------|---------------|
| **Clear name** | Memorable, searchable, spellable |
| **One-liner** | "A [type] for [audience] that [does what]" |
| **Badges** | Social proof, health signals |
| **Visual** | GIF > Screenshot > Nothing |
| **Quick start** | <5 lines to first value |
| **Why this?** | Differentiation from alternatives |
| **Installation** | All platforms, copy-paste |
| **Examples** | Real use cases, not contrived |
| **Docs link** | More detail available |
| **Contributing** | Community welcome |

### Repository Optimization

| Element | Best Practice |
|---------|--------------|
| **Description** | 100 chars max, keyword-rich |
| **Topics** | 5-10 relevant tags for discoverability |
| **Website** | Link to docs or landing page |
| **Releases** | Semantic versioning, changelogs |
| **Issues** | Templates for bugs/features |
| **Discussions** | Enable for community Q&A |
| **Sponsors** | Enable if you want funding |

### Issue & PR Templates

**Bug report template:**

```markdown
---
name: Bug Report
about: Report a bug to help us improve
---

#### Bug Description
[Clear description]

#### Steps to Reproduce
1.
2.
3.

#### Expected Behavior
[What should happen]

#### Actual Behavior
[What actually happens]

#### Environment
- OS:
- Node version:
- Package version:

#### Additional Context
[Screenshots, logs, etc.]

Feature request template:

---
name: Feature Request
about: Suggest an idea for this project
---

#### Problem
[What problem does this solve?]

#### Proposed Solution
[How would you like it to work?]

#### Alternatives Considered
[Other approaches you've thought about]

#### Additional Context
[Examples, mockups, etc.]

Community Building

Community Spaces

Start with GitHub Discussions. Add Discord when you have 50+ active users.

Community Principles

Contributor Funnel

User → Star → Issue → PR → Regular Contributor → Maintainer

Optimize each transition:

Contributor Experience

CONTRIBUTING.md Essentials

#### Quick Start

1. Fork the repo
2. Clone your fork
3. Install dependencies: `npm install`
4. Create a branch: `git checkout -b my-feature`
5. Make your changes
6. Run tests: `npm test`
7. Commit: `git commit -m "Add my feature"`
8. Push: `git push origin my-feature`
9. Open a Pull Request

#### Development Setup

[Detailed setup instructions]

#### Code Style

- We use [Prettier/ESLint config]
- Run `npm run lint` before committing
- [Other conventions]

#### Commit Messages

We follow [Conventional Commits](https://conventionalcommits.org/):
- `feat: add new feature`
- `fix: resolve bug`
- `docs: update readme`
- `chore: update dependencies`

#### Pull Request Process

1. Update docs if needed
2. Add tests for new features
3. Ensure CI passes
4. Get one approval

#### Good First Issues

Look for issues labeled `good first issue` - these are great starting points!

#### Questions?

Open a Discussion or reach out on Discord.

"Good First Issue" Strategy

Create genuinely approachable issues:

For each good first issue:

• Explain context and why it matters
• Link to relevant code files
• Describe expected outcome
• Offer to help in comments

Launch Strategies

Pre-Launch Checklist

Launch Day Playbook

Timeline:

Platform-Specific Tactics

Hacker News:

• Title: Descriptive, no hype ("Show HN: X - a Y for Z")
• First comment: Explain motivation, tech decisions
• Be available to respond for hours
• Don't ask for upvotes (instant death)

Reddit:

• Find 2-3 relevant subreddits (not just r/programming)
• Read the rules first
• Be a community member, not a marketer
• Share genuinely useful context

Twitter/X:

• Thread format: Problem → Solution → Demo → Link
• Include GIF/video
• Tag relevant accounts (framework authors, etc.)
• Share builds-in-public journey

Dev.to / Hashnode:

• Write a "Why I Built This" article
• Technical depth, personal story
• Cross-post from your blog

Post-Launch

Sustainable Growth

Growth Tactics

Content Strategy for OSS

Avoiding Burnout

Metrics That Matter

Vanity vs. Value

What to Track

Tools

Related Skills

• developer-audience-context - Know who your users are
• community-building - Build Discord/Slack community
• devrel-content - Create supporting content
• developer-advocacy - Conference talks, podcasts
• hacker-news-strategy - Launch and engage on HN

Limitations

• Use this skill only when the task clearly matches its upstream source and local project context.
• Verify commands, generated code, dependencies, credentials, and external service behavior before applying changes.
• Do not treat examples as a substitute for environment-specific tests, security review, or user approval for destructive or costly actions.