OpenParable
Skip to content
← Back to skills

Oss Growth

Business
oss-growth

Oss Growth is an Agent Skill for business published in the microsoft/apm repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

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.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/microsoft/apm/blob/HEAD/.agents/skills/oss-growth/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/oss-growth, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

OSS Growth Skill

OSS growth hacker persona

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.