Market open source projects authentically and grow contributors

Open Source Marketing helps a maintainer promote a software project with useful information and community practices. It frames growth as the product of real value, discoverability, and first-use experience, and treats each factor as necessary. The skill covers repository presentation, contribution paths, community spaces, launch planning, content, and signals that reflect participation. It also separates attention measures such as stars from measures such as active issues, pull requests, and returning contributors.

The repository guidance treats the README as a landing page. It recommends a clear one-line description, useful badges, a visual demonstration, a quick start, installation instructions, examples, documentation, and contribution guidance. Repository metadata can include a concise description, relevant topics, a documentation or landing page, releases, issue templates, discussions, and sponsorship information where appropriate.

Use this skill when planning how to introduce an open source project to likely users, improve its first-use experience, invite contributions, or build an ongoing community. It can help a maintainer audit a README, set up contribution instructions, choose community spaces, prepare a launch checklist, and decide what engagement to track. It is also relevant when a project needs a sustainable publishing rhythm or clearer expectations for maintainer response.

authentic participation: solve real problems, respond to community context, and share useful details. It warns against spam, transactional follow patterns, asking for upvotes, and treating a launch as a one-day event. It is not a substitute for knowing the project's audience, checking community rules, or confirming that installation and examples work.

Start with audience context: the users' roles and technology, discovery channels, alternatives, and evaluation criteria. Use reading .agents/developer-audience-context.md; when that file is absent, it recommends running the developer-audience-context skill first. Useful project inputs include its README, release history, issue and pull request process, documentation, existing community channels, and current maintenance capacity.

The resulting plan can include README changes, repository metadata, contribution steps, issue templates, launch activities, follow-up content, and a small set of meaningful measures. Suggested measures include active issues and pull requests, returning contributors, weekly active users, and issue response time. GitHub Insights and Traffic track repository activity, while npm-stat is listed for package downloads. The skill does not prescribe one universal target for these measures.

Before launch, check that installation, examples, documentation, and contribution instructions work for a new user. Prepare a concise announcement and identify relevant communities whose rules permit project sharing. On launch day, answer questions and acknowledge feedback; afterward, turn recurring questions into documentation, fixes, or follow-up posts. The guide treats launch as the start of ongoing communication rather than a single event.

Community spaces can include GitHub Discussions, Discord, Slack, or Discourse. Choose channels the maintainers can actually support, publish participation principles, and explain where users should ask questions or report problems. A contributor path should make development setup, code style, commit expectations, pull-request steps, and beginner-friendly issues clear. Issue and pull-request templates help collect problem details and proposed changes in a consistent form.

For sustainable growth, share useful technical content at a cadence the team can maintain, invite co-maintainers, and set realistic response boundaries. Track signals tied to project health-active issues and pull requests, returning contributors, weekly active users, and response time-alongside discovery data such as repository traffic and package downloads. Stars can show attention but do not by themselves demonstrate adoption or healthy participation.

This skill is for open source maintainers and project teams that want to make a project easier to discover, evaluate, try, and contribute to. It fits teams that can answer questions, maintain documentation, and set realistic expectations for support. Start community activity at a manageable scale and add channels as participation grows.

A practical review can begin with the README and quick start, then check whether issue templates and contribution instructions explain the path from first interest to a useful pull request. For launch planning, prepare materials before launch, post in relevant spaces, respond to feedback, and continue updates afterward. For sustainability, set response expectations, publish a roadmap or RFC process, recruit co-maintainers, and set boundaries around availability.

npm install project-name