developer-marketing-playbook · git:20261015.68deea2 · 2026-10-15 · sha256 bddac60a64b2bdb7
developer-marketing-playbook git:20261015.68deea2A
Immutable. This exact content never changes and is served at /api/v1/blob/bddac60a64b2bdb7.
No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_njmo4ndzgsycbzvp/bddac60a64b2bdb71e3ca36da1ee825348d134cb8f59c20d7d87ef3ba91a8f66.json
Then /plugin install developer-marketing-playbook@markdownregistry-njmo4ndzgsycbzvp 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: developer-marketing-playbook description: | Complete developer marketing playbook covering DevRel programs, documentation as marketing, API developer experience, community building, and hackathon strategy. For dev-tool founders who need to reach engineers. Follow @WeiYipei on X. source: https://github.com/Gingiris-1031/gingiris-skills/tree/main/skills/developer-marketing-playbook tags: - developer-marketing - devrel - developer-community - documentation - open-source - developer - api - sdk - developer-experience - developer-relations - claude-code - ai-agent-skill - hackathon - dev-tool - latest --- # Developer Marketing Playbook — DevRel, Docs & Community Funnels > 🌍 **Language / 语言**: [中文](#中文版) | [English](references/en/README.md) | [日本語](references/ja/README.md) | [한국어](references/ko/README.md) ## 📦 Install ```bash clawhub install developer-marketing-playbook ``` **What you get after installing:** - Developer community building playbook (Discord/Slack/GitHub Discussions) - Technical content strategy for developer audiences - DevRel metrics framework (awareness → adoption → advocacy) --- Engineers don't respond to traditional marketing. Here's what actually works. - **DevRel program design**: Roles, metrics, and activities that drive adoption - **Docs as growth engine**: How great documentation becomes your best acquisition channel - **API experience**: DX improvements that reduce time-to-first-API-call - **Community funnels**: Discord/Slack → contributor → champion → customer pipeline - **Hackathon ROI**: When hackathons work, how to run them, and measuring impact ## Developer acquisition operating system ### Stage 1 — reconstruct category history Use Wayback snapshots for the competitor's first site, beta site and first major launch. For each stage record positioning, page depth, use cases, navigation/pricing changes, and when SEO/community investment began. This prevents copying a mature competitor's current channel mix into a zero-to-one product. ### Stage 2 — benchmark the best channel operator Do not benchmark every channel against the same competitor. Use the category leader for site/positioning, then select the strongest operator per channel. Track official, founder, DevRel and creator accounts; separate beta cadence, launch-week bursts and steady-state programs. Required research row: `brand | channel | date | format | category | URL | content framework | views/engagement | campaign membership | CTA` ### Stage 3 — convert docs into adoption Measure docs on `landing → quick start → first successful call/deploy → second session`, not pageviews alone. Every launch packet must include a tested quick start, error recovery, deploy path, reference docs, examples and a community/support next step. ### Stage 4 — ecosystem campaign For an enterprise/open-source campaign, coordinate README, comparison article, ecosystem partners/sponsors, relevant backlinks, community posts and DevRel follow-up. Report impressions and stars separately from activated developers and qualified accounts. ### Stage 5 — interview and iterate Run 1:1 interviews with activated and bounced developers. Ask them to screen-share the workflow, identify the first "aha", and show what they already pay for. If acquisition rises but activation stays below target, pause distribution and fix the product/docs path. Source framework: Iris competitor-research wiki and open-source global-operations deck supplied for this skill update. ## 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 -->