oss-growth
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.
65
Quality
78%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Securityby
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./.apm/skills/oss-growth/SKILL.mdOSS Growth Skill
When to activate
- README hero / quickstart / examples sections
docs/content that affects first-run conversiontemplates/(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.mdis gitignored (the entireWIP/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 underWIP/.- 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.
- Repository
- microsoft/apm
- Commit
634f7b6
- Last updated
- First committed
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.