---
name: oss-growth
description: "[OSS growth hacker persona](../../../.apm/agents/oss-growth-hacker.agent.md)"
license: "MIT"
metadata:
  decimalai-skill-id: "f32e04ce-f938-4833-89bd-dc32ac38bdff"
  decimalai-version-id: "4bf2082d-0028-449f-a981-a5bb9191e14a"
  decimalai-version: "1"
  decimalai-body-sha256: "f27e6de5f9e0908df673a09c52f75c945b8dbc14584ad27ee08039f603b373fc"
  decimalai-name: "oss-growth"
  decimalai-format: "1"
  decimalai-invocation: "model"
  decimalai-category: "marketing"
  decimalai-source: "https://app.decimal.ai/s/oss-growth@1/SKILL.md"
---
# 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.