$ loading_
Improve OSS growth strategy, conversion docs, and contributor acquisition workflows.
Copy the install command and let the AI configure it · recommended for beginners
Please install the "oss-growth" skill from askskill: 1. Download https://raw.githubusercontent.com/microsoft/apm/main/.apm/skills/oss-growth/SKILL.md 2. Save it as ~/.claude/skills/oss-growth/SKILL.md 3. Reload skills and tell me it's ready
Please review this open-source project's README and optimize it for first-visit conversion. Rewrite the project intro, value proposition, quickstart, feature highlights, and call to action, and identify anything currently blocking installation or trial. Provide both recommendations and replacement-ready README copy.
A higher-converting README rewrite with diagnosis and ready-to-use copy.
Design a contributor growth funnel for this open-source project, from visitor to star, install, issue filing, PR submission, and long-term contributor. List goals, touchpoints, blockers, improvement actions, and any templates or documents needed for each stage.
A staged contributor growth strategy with concrete actions and supporting documentation.
We are preparing a new release. Based on the changes, generate announcement materials for GitHub, a blog post, and social media. Highlight user value, key updates, and reasons to upgrade, and provide three story angles suitable for promotion.
Multi-channel release copy plus story angles for broader promotion.
OSS growth hacker persona
docs/ content that affects first-run conversiontemplates/ (starter projects shape the second-use experience)WIP/growth-strategy.mdWIP/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/.Guide APM positioning, release communication, and breaking-change strategy decisions.
Audit an entire docs corpus against code and propose precise fixes.
Improve CLI output, logs, errors, and terminal diagnostic user experience.
Triages bug batches and drives related PRs to a mergeable state.
Plan doc TOC changes and outline stubs when PRs require structural updates.
Triage APM issues in batches and drive approved ones to mergeable PRs.
Helps teams handle APM positioning, release communication, and breaking-change decisions.
Initialize projects or verify and generate up-to-date SDD documentation templates.
Verify and create standard community and governance files for new projects.
Guide users to co-author docs, proposals, and specs through iterative refinement.
Initialize and verify SDD project config files and keep instructions up to date.
Write and maintain technical docs, from READMEs to API and runbook guides.