SkillsAdd

gingiris-1031/gingiris-skills

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.

First seen Jun 17, 2026

Installation

$ npx skills add gingiris-1031/gingiris-skills --skill developer-marketing-playbook
View on skills.sh ↗ GitHub repository ↗

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

stitch-design-taste Same topic
leonxlnx/taste-skill 287.7K installs
firecrawl-seo-audit Same topic
firecrawl/firecrawl-workflows

Audit a website's SEO with Firecrawl. Use when the user asks for an SEO audit, metadata and hea…

31.6K installs
taste-design Same topic
google-labs-code/stitch-skills 17.5K installs
apify-ultimate-scraper Same topic
apify/agent-skills

Universal AI-powered web scraper for any platform. Scrape data from Instagram, Facebook, TikTok…

15.2K installs
clerk-vue-patterns Same topic
clerk/skills

Vue 3 patterns with Clerk — composables (useAuth, useUser, useClerk, useOrganization), Vue Rout…

11.4K installs
email-best-practices Same topic
resend/resend-skills

Use when building email features, emails going to spam, high bounce rates, setting up SPF/DKIM/…

8.9K installs

Also in this package

Other skills from gingiris-1031/gingiris-skills · top by installs.

npx skills add gingiris-1031/gingiris-skills
gr 184 gr-backlinks 181 gr-blog-post 178 gingiris-seo-geo-agent 177 gr-aso 177 gr-seo-patrol 176 gr-geo-cite 176 gr-b2b-growth 176 gr-user-interview 176 gr-social-distill 175

Browse all from gingiris-1031/gingiris-skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 77
License LICENSE
Default branch main
Open issues 0
Status Active

Skill metadata

Parsed from SKILL.md frontmatter.

Declared agents claude-code

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 3,786 B
  • docs SUMMARY.md 271 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 147 installs

SKILL.md

Developer Marketing Playbook — DevRel, Docs & Community Funnels

🌍 Language / 语言: [中文](#中文版) | [English](references/en/README.md) | [日本語](references/ja/README.md) | [한국어](references/ko/README.md)

📦 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