Developer Marketing Playbook — DevRel, Docs & Community Funnels
Complete developer marketing playbook covering DevRel programs, documentation as marketing, API developer experience, community building, and hackathon strategy.
How to use it
Claude Code
- Run the line below. It pulls the whole folder into
~/.claude/skills/developer-marketing-playbook. - Describe your job in plain words. Claude Code follows the skill from there.
Claude Code — installs the whole folder, not just SKILL.md
npx degit Gingiris-1031/gingiris-skills/skills/developer-marketing-playbook#main ~/.claude/skills/developer-marketing-playbookFor one project only, change the path to .claude/skills/developer-marketing-playbook.
Claude (web or desktop app)
- On this page open ⋯ → Download .md.
- Save it as SKILL.md in a folder, zip the folder, then Customize → Skills → + → Create skill → Upload a skill.
- Pick the file and Save. Claude shows the name and description and runs a security scan.
- Check the skill is switched on.
- Start a new chat and describe your job in plain words. The AI follows the skill from there.
ChatGPT or another app
- ChatGPT: make a Project and paste it into Instructions.
- Neither? Paste it at the top of a new chat — it works for that chat.
Not working?
- Check which app you pasted it into — the steps above name the right one.
- Some skills need the paid tier of Claude or ChatGPT.
Paste into Claude, ChatGPT or Cursor.
Source of Developer Marketing Playbook — DevRel, Docs & Community Funnels
Show the full text80 lines
| name | description | source | tags |
|---|---|---|---|
| developer-marketing-playbook | | 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. | https://github.com/Gingiris-1031/gingiris-skills/tree/main/skills/developer-marketing-playbook | - 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
📦 Install
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
| 1 | |
| 2 | name developer-marketing-playbook |
| 3 | description | |
| 4 | 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. |
| 5 | source https://github.com/Gingiris-1031/gingiris-skills/tree/main/skills/developer-marketing-playbook |
| 6 | tags |
| 7 | - developer-marketing |
| 8 | - devrel |
| 9 | - developer-community |
| 10 | - documentation |
| 11 | - open-source |
| 12 | - developer |
| 13 | - api |
| 14 | - sdk |
| 15 | - developer-experience |
| 16 | - developer-relations |
| 17 | - claude-code |
| 18 | - ai-agent-skill |
| 19 | - hackathon |
| 20 | - dev-tool |
| 21 | - latest |
| 22 | |
| 23 | # Developer Marketing Playbook — DevRel, Docs & Community Funnels |
| 24 | |
| 25 | > 🌍 **Language / 语言**: [中文] | [English] | [日本語] | [한국어] |
| 26 | |
| 27 | ## 📦 Install |
| 28 | |
| 29 | |
| 30 | clawhub install developer-marketing-playbook |
| 31 | |
| 32 | |
| 33 | **What you get after installing:** |
| 34 | Developer community building playbook (Discord/Slack/GitHub Discussions) |
| 35 | Technical content strategy for developer audiences |
| 36 | DevRel metrics framework (awareness → adoption → advocacy) |
| 37 | |
| 38 | |
| 39 | |
| 40 | Engineers don't respond to traditional marketing. Here's what actually works. |
| 41 | |
| 42 | **DevRel program design**: Roles, metrics, and activities that drive adoption |
| 43 | **Docs as growth engine**: How great documentation becomes your best acquisition channel |
| 44 | **API experience**: DX improvements that reduce time-to-first-API-call |
| 45 | **Community funnels**: Discord/Slack → contributor → champion → customer pipeline |
| 46 | **Hackathon ROI**: When hackathons work, how to run them, and measuring impact |
| 47 | |
| 48 | ## Developer acquisition operating system |
| 49 | |
| 50 | ### Stage 1 — reconstruct category history |
| 51 | |
| 52 | 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. |
| 53 | |
| 54 | ### Stage 2 — benchmark the best channel operator |
| 55 | |
| 56 | 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. |
| 57 | |
| 58 | Required research row: |
| 59 | |
| 60 | `brand | channel | date | format | category | URL | content framework | views/engagement | campaign membership | CTA` |
| 61 | |
| 62 | ### Stage 3 — convert docs into adoption |
| 63 | |
| 64 | 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. |
| 65 | |
| 66 | ### Stage 4 — ecosystem campaign |
| 67 | |
| 68 | 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. |
| 69 | |
| 70 | ### Stage 5 — interview and iterate |
| 71 | |
| 72 | 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. |
| 73 | |
| 74 | Source framework: Iris competitor-research wiki and open-source global-operations deck supplied for this skill update. |
| 75 | |
| 76 | ## Related Gingiris Skills |
| 77 | Full version: https://clawhub.ai/gingiris-1031/skills/gingiris-opensource |
| 78 | All skills: https://clawhub.ai/gingiris-1031 |
| 79 | Follow: [@WeiYipei on X] |
| 80 |
Discussion
Discord Skill (Read-Only)Read Discord for financial research using opencli (read-only). Use this skill whenever the user wants to read Discord channels, search for messages in trading servers, view guild/channel info, monitor crypto or market discussion groups, or gather financial sentiment from Discord. Triggers include: "check my Discord", "search Discord for", "read Discord messages", what's happening in the trading Discord", "show Discord channels", "list my servers", Discord sentiment on BTC", "what are people saying in Discord about AAPL", monitor crypto Discord", any mention of Discord in context of reading financial news, market research, or trading community discussions. This skill is READ-ONLY — it does NOT support sending messages, reacting, or any write operations.YouTube Audience InsightsRead your YouTube audience from the comments: pull commenters and top comments on any video, surface recurring questions and themes (content ideas), repeat commenters (superfans), sentiment, and which comments to reply to or pin. Also channel stats and niche trending, via the free official YouTube Data API. Triggers on "who commented on my video", "analyze my comments", "audience insights", "trending on YouTube". Not for writing a community post (use yt-community-post-writer).YouTube Community Post WriterWrite YouTube community-tab posts: text updates, polls, image-caption posts, and questions that drive comments and bring subscribers back between video uploads. Tuned to the community tab's role as a low-friction touchpoint that keeps a channel warm and feeds session signals. Returns a copy-paste block (community posts have no publishing API, so this is always manual by design). Use to write a community post or poll. Not for video titles or descriptions (use yt-title-optimizer and yt-description-writer).Reddit Community BuilderExpert Reddit marketing specialist focused on authentic community engagement, value-driven content creation, and long-term relationship building. Masters Reddit culture navigation.
Browse more free Claude skills or everything in Marketing.