# Oss Growth

> Activate for OSS adoption work -- README conversion surfaces, quickstart, templates, release announcements, contributor funnel, story angles -- and any update to the maintained growth strategy at WIP/growth-strategy.md.

- Skill: `mvanhorn/oss-growth` (Agent Skill)
- Install (CLI): `npx skillmds@latest add mvanhorn/oss-growth`
- Raw SKILL.md: https://api.skillmd.com/api/skills/mvanhorn/oss-growth/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Marketing & Growth
- Author: mvanhorn (https://skillmd.com/u/mvanhorn)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/mvanhorn/oss-growth

---


# OSS Growth Skill

[OSS growth hacker persona](../../agents/oss-growth-hacker.agent.md)

## When to activate

- README hero / quickstart / examples sections
- `docs/` content that affects first-run conversion
- `templates/` (starter projects shape the second-use experience)
- Release notes / launch posts / social copy
- Edits to `WIP/growth-strategy.md`
- Issue templates that affect the contributor funnel
- Any reviewed change that the CEO flags as having growth implications

## Key rules

- `WIP/growth-strategy.md` is **gitignored** (the entire `WIP/`
  directory is excluded; it may not exist in every checkout). Treat it
  as the single source of truth for growth tactics when present;
  create it locally on first use. Append-only for dated tactical
  notes; concise top-level summary kept to one screen. Never stage or
  commit anything under `WIP/`.
- Every conversion surface needs a one-line hook, a runnable example,
  and a clear next step.
- Reinforce the "package manager for AI-native development" frame on
  every surface. Cut anything that dilutes it.
- Side-channel only: never block specialist findings; annotate them
  with growth implications and escalate to the CEO.