---
name: OSS Growth
slug: oss-growth
category: Writing
description: OSS Growth improves open source project adoption by refining README conversion surfaces, quickstarts, templates, release announcements, and contributor funnels. Use it when working on OSS adoption and growth tactics.
github: "https://github.com/microsoft/apm/tree/main/.agents/skills/oss-growth"
language: Python
stars: 3544
forks: 324
install: "npx degit https://github.com/microsoft/apm/tree/main/.agents/skills/oss-growth ~/.claude/skills/oss-growth"
installs_to: ~/.claude/skills/oss-growth
source_path: .agents/skills/oss-growth/SKILL.md
collection_size: 21
category_size: 1012
collection_url: "https://dirskills.com/collections/microsoft/apm"
added: 2026-08-16T07:02:26.851Z
last_synced: 2026-08-16T07:02:26.851Z
canonical_url: "https://dirskills.com/skills/oss-growth"
---

# OSS Growth

OSS Growth improves open source project adoption by refining README conversion surfaces, quickstarts, templates, release announcements, and contributor funnels. Use it when working on OSS adoption and growth tactics.

**Install:**

```bash
npx degit https://github.com/microsoft/apm/tree/main/.agents/skills/oss-growth ~/.claude/skills/oss-growth
```

## README

# OSS Growth Skill

[OSS growth hacker persona](../../../.apm/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.