developer-marketing-playbook
A guide for dev-tool founders to build DevRel, improve API developer experience, and drive community engagement.
Install
mkdir -p .claude/skills/developer-marketing-playbook && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/19462" && unzip -o skill.zip -d .claude/skills/developer-marketing-playbook && rm skill.zipInstalls to .claude/skills/developer-marketing-playbook
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
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.Key capabilities
- →Design DevRel programs
- →Improve API developer experience
- →Build community funnels
- →Plan hackathon strategies
- →Develop technical content strategies
How it works
The playbook provides a structured framework for DevRel, documentation, and community engagement to drive developer adoption. It focuses on metrics-driven activities that move users from awareness to advocacy.
Inputs & outputs
When to use developer-marketing-playbook
- →Designing DevRel programs
- →Improving API documentation
- →Setting up community funnels
- →Planning hackathons
About this skill
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
How it compares
Unlike traditional marketing, this approach focuses on technical content and developer-specific funnels to reach engineers.
Compared to similar skills
developer-marketing-playbook side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| developer-marketing-playbook (this skill) | 0 | 2mo | Review | Intermediate |
| seo-optimizer | 33 | 8mo | No flags | Intermediate |
| seo-content-writer | 24 | 4mo | No flags | Beginner |
| content-creation | 22 | 6mo | No flags | Beginner |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
seo-optimizer
davila7
Search Engine Optimization specialist for content strategy, technical SEO, keyword research, and ranking improvements. Use when optimizing website content, improving search rankings, conducting keyword analysis, or implementing SEO best practices. Expert in on-page SEO, meta tags, schema markup, and Core Web Vitals.
seo-content-writer
sickn33
Writes SEO-optimized content based on provided keywords and topic briefs. Creates engaging, comprehensive content following best practices. Use PROACTIVELY for content creation tasks.
content-creation
anthropics
Draft marketing content across channels — blog posts, social media, email newsletters, landing pages, press releases, and case studies. Use when writing any marketing content, when you need channel-specific formatting, SEO-optimized copy, headline options, or calls to action.
content-marketer
sickn33
Elite content marketing strategist specializing in AI-powered content creation, omnichannel distribution, SEO optimization, and data-driven performance marketing. Masters modern content tools, social media automation, and conversion optimization with 2024/2025 best practices. Use PROACTIVELY for comprehensive content marketing.
competitor-alternatives
davila7
When the user wants to create competitor comparison or alternative pages for SEO and sales enablement. Also use when the user mentions 'alternative page,' 'vs page,' 'competitor comparison,' 'comparison page,' '[Product] vs [Product],' '[Product] alternative,' or 'competitive landing pages.' Covers four formats: singular alternative, plural alternatives, you vs competitor, and competitor vs competitor. Emphasizes deep research, modular content architecture, and varied section types beyond feature tables.
web-content
alinaqi
SEO and AI discovery (GEO) - schema, ChatGPT/Perplexity optimization