open-source-marketing-playbook · git:20261015.68deea2 · 2026-10-15 · sha256 9caf0c6af6e3f100
open-source-marketing-playbook git:20261015.68deea2A
Immutable. This exact content never changes and is served at /api/v1/blob/9caf0c6af6e3f100.
No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_36lidk3xfoum5cfq/9caf0c6af6e3f100caee0777b27007ea63a7d7c28ec649a0e1590fb40d13c806.json
Then /plugin install open-source-marketing-playbook@markdownregistry-36lidk3xfoum5cfq in Claude Code. It installs this exact version, the one graded A here, pinned to the commit it was graded at, and leaves it there.
--- name: open-source-marketing-playbook description: | Marketing playbook for open-source projects led by non-technical founders. Covers README optimization, community building, contributor attraction, and translating OSS traction into revenue. By @WeiYipei. source: https://github.com/Gingiris-1031/gingiris-skills/tree/main/skills/open-source-marketing-playbook tags: - open-source-marketing - github-stars - oss - developer-marketing - community-building - readme - product-hunt - cold-start - hacker-news - claude-code - ai-agent-skill - agent-skill - latest --- # Open Source Marketing for Non-Technical Founders > 🌍 **Language / 语言**: [中文](#中文版) | [English](references/en/README.md) | [日本語](references/ja/README.md) | [한국어](references/ko/README.md) ## 📦 Install ```bash clawhub install open-source-marketing-playbook ``` **What you get after installing:** - README-as-landing-page structure with badges and social proof - Community-first growth strategy (Discord/Slack without writing code) - Star momentum tactics and contributor funnel design --- You don't need to be a developer to market an open-source project. This playbook bridges the gap and produces an executable launch packet. - **README as landing page**: Structure, badges, and social proof that convert visitors - **Community-first growth**: Discord/Slack strategy without writing code - **Star momentum**: How to trigger GitHub Trending without gaming the system - **Contributor funnel**: Attract and retain open-source contributors - **Monetization bridge**: From stars to sponsors to paid tiers ## 0. Open-source readiness gate Before planning distribution, answer four questions: 1. Is this for enterprises, developers, or both? 2. Are API/SDK, self-hosting and documentation usable enough for a stranger to reach first value? 3. Is the goal influence, commercial leads, recruiting, fundraising, or a defined mix? 4. Can the team maintain issues, releases and community after launch—and capture qualified SMB/enterprise demand? If any answer is unclear, return a readiness-gap table before proposing launch channels. Score the result as `Go`, `Fix`, or `No-Go` for positioning, clean-machine quickstart, reproducible proof, license/security/privacy, launch-week ownership, and post-star conversion. A `No-Go` blocks concentrated distribution. ## 1. Required launch packet Produce these assets together: - Positioning: `[known closed-source comparator] alternative for [audience], differentiated by [verifiable benefit]`. - README: first-screen tagline, demo, working quick start, docs, deployment, community and contribution paths. - PR/article: comparative advantage, why now, proof, use cases and reusable excerpts for secondary distribution. - Developer docs: fastest path to first value, one-click deploy where possible, troubleshooting and next-step links. - Community operating map: Reddit for discovery, X for 1:1 feedback/news, Discord/Telegram for retention and contributor coordination. ## 2. Launch-week execution - Complete the concentrated announcement cycle within 24 hours, while preserving authentic channel-native posts. - Hold 1:1 conversations with early users and relevant community operators; do not mass-post identical copy. - Publish where the comparator/category is already discussed, including relevant news communities. - Track `source → repo visit → star/install → activated user → qualified lead → paid`. - Route non-code contributors to translation, documentation, community moderation and global operations instead of losing them. Use one row per channel: ```text channel | ICP | channel-native angle | CTA | UTM/source | owner | local time + timezone | success threshold | stop condition | evidence URL ``` Review at 2h (operations only), 24h (continue/change/pause), 72h (second wave), and 7d (reuse/budget). Mark unavailable native metrics as `data unavailable`. Never buy stars or accounts, coordinate fake/incentivized votes, conceal sponsorships, bulk-scrape and spam users, or use AI to impersonate authentic participation. Re-check current community rules, creator metrics, rates and contacts before use. ## 3. Post-launch operating loop `exposure → early users → qualified customers → needs → product iteration → monetization` Run at least 30 early interviews before treating stars as PMF. Let the user speak most of the session; verify existing paid behavior and request a screen-share of the workflow. Start monetization experiments early and balance refactoring with user-visible improvements. Full evidence map and output template: `references/iris-oss-field-notes.md`. ## Related Gingiris Skills - Full version: https://clawhub.ai/gingiris-1031/skills/gingiris-opensource - All skills: https://clawhub.ai/gingiris-1031 - Follow: [@WeiYipei on X](https://x.com/WeiYipei) <!-- gingiris-community-cta:start --> ## 加入出海社群与购买资料包 · Community & Resources - **加入出海社群:** 微信添加 **staywildgrow**,留言「**加入社群**」即可。 - **购买资料包:** 微信添加 **staywildgrow**,咨询购买 Gingiris 出海资料包,价格 **599 元人民币**。 - **Join the global growth community:** Add **staywildgrow** on WeChat and send **“加入社群”** (join the community). - **Get the resource pack:** Add **staywildgrow** on WeChat to purchase the Gingiris global growth resource pack for **CNY 599**. 社群与资料包为可选入口,不影响本开源 Skill 的安装和使用。 The community and paid resource pack are optional; neither is required to install or use this open-source skill. <!-- gingiris-community-cta:end -->