agentleFS
Gingiris-1031Gingiris-1031/gingiris-skills/skills/developer-marketing-playbook/SKILL.md

developer-marketing-playbook

Skill89 starsChanged 32 days agoMITView on GitHub

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.

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 7 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Hackathon ROI: When hackathons work, how to run them, and measuring impact

    line 46
  2. Distinctive:

    Do not benchmark every channel against the same competitor.

    line 56
  3. Distinctive:

    Run 1:1 interviews with activated and bounced developers.

    line 72
  4. Distinctive:

    All skills: https://clawhub.ai/gingiris-1031

    line 78
  5. Distinctive:

    Follow: @WeiYipei on X

    line 79
  6. Distinctive:

    Join the global growth community: Add staywildgrow on WeChat and send “加入社群” (join the community).

    line 87
  7. Distinctive:

    Get the resource pack: Add staywildgrow on WeChat to purchase the Gingiris global growth resource pack for CNY 599.

    line 88

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Developer Marketing Playbook — DevRel, Docs & Community Funnels

🌍 Language / 语言: 中文 | English | 日本語 | 한국어

📦 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

<!-- 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 -->

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.