Skill2.9k repo starsupdated yesterday

oss-growth

The OSS Growth skill applies growth-hacking principles to open-source project materials, optimizing README sections, documentation, templates, and release communications for user conversion and retention. Activate it when reviewing changes to first-run experiences, contributor funnels, or content flagged by leadership as having growth implications, ensuring every conversion surface includes a compelling hook, working example, and clear next step.

View source Repository: apm

Install in Claude Code

Copy

git clone --depth 1 https://github.com/microsoft/apm /tmp/oss-growth && cp -r /tmp/oss-growth/.apm/skills/oss-growth ~/.claude/skills/oss-growth

Then start a new Claude Code session; the skill loads automatically.

Definition

SKILL.md

# 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.