agentleFS
Gingiris-1031Gingiris-1031/gingiris-skills/skills/devrel-playbook/SKILL.md

devrel-playbook

Skill89 starsChanged 32 days agoMITView on GitHub

Build and measure Developer Relations programs across documentation, community, technical content, integrations, events and developer advocacy. Use when designing DevRel strategy, improving developer activation, launching an API/SDK, evaluating sponsorships, or connecting community activity to product adoption and revenue.

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:

    Run five-developer task tests quarterly.

    line 42
  2. Distinctive:

    Before: define build prompt, sample app, mentor coverage, attribution and success event.

    line 70
  3. Distinctive:

    After: route viable projects to showcase, contributor or customer tracks and measure D7/D30 continuation.

    line 72
  4. Distinctive:

    Use sponsor/newsletter placements only with source-tagged links and a relevant developer offer.

    line 84
  5. Distinctive:

    Never buy stars, fake community activity, conceal sponsorship, scrape private member data or manufacture benchmarks.

    line 104
  6. Distinctive:

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

    line 112
  7. Distinctive:

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

    line 113

≈ “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

DevRel Playbook — Developer Activation, Community and Revenue

DevRel exists to reduce the distance between a developer's first exposure and sustained product value. Do not optimize only for members, event attendance or impressions.

Diagnose the bottleneck

Choose one primary problem:

ProblemEvidenceFirst intervention
DiscoveryICP developers do not know the projecttechnical content and ecosystem distribution
UnderstandingDocs traffic is high, quickstart completion is lowREADME/docs usability tests
ActivationKeys/SDK installed, first successful call is lowsample app and error-path repair
RetentionDevelopers try once and disappearuse-case education, office hours, lifecycle prompts
ContributionUsers want changes but do not contributeissue design, maintainer SLA, contributor onboarding
Enterprise pullTeams use product but procurement is invisibleusage-qualified account handoff to sales

Developer journey instrumentation

Track:

source → docs/README visit → quickstart start → first success → second session → production use → contribution/qualified account

Define each event and cohort window. Separate employees, bots, test accounts and event attendees who never touched the product.

Documentation system

Maintain four layers:

  1. README: outcome, demo, quickstart, license and support path;
  2. Tutorial: one job completed end to end;
  3. How-to: focused operational tasks and integrations;
  4. Reference: complete APIs, errors, limits and versions.

Run five-developer task tests quarterly. Record completion time, failure step, search terms and recovery success. Documentation is a product surface, not a publishing queue.

Community operating model

  • Assign owner and response SLA for support, bugs and feature discussions.
  • Separate announcements, help, showcase and contributor channels.
  • Turn repeated questions into docs; turn reproducible bugs into issues.
  • Recognize substantive help, not message volume.
  • Publish moderation and escalation rules before growth.

Weekly review: unanswered questions, median time to useful answer, activated community members, recurring friction and contributions merged.

Technical content and comparison assets

Prioritize content a developer can verify:

  • reproducible benchmark with methodology;
  • architecture/deep-dive explaining tradeoffs;
  • migration or integration tutorial;
  • honest comparison page stating where each option wins;
  • user build story with repo or demo.

The anonymized Apache-ecosystem campaign in the Gingiris case library combined README repair, comparison content and backlinks/sponsor distribution; it reported 200K impressions and +401 stars in 10 days. Treat this as historical evidence, not guaranteed lift.

Events, hackathons and sponsorships

Approve only when the event reaches the target developer and has a post-event activation path.

Before: define build prompt, sample app, mentor coverage, attribution and success event. During: measure builders who reach first success, not registrations. After: route viable projects to showcase, contributor or customer tracks and measure D7/D30 continuation.

Event scorecard:

qualified registrants | builders started | first success | demos completed | D7 active | contributions | opportunities | total cost

Ecosystem and backlink program

  • Maintain official integration pages and reciprocal technical documentation.
  • Contribute useful examples to ecosystem repositories before requesting promotion.
  • Use sponsor/newsletter placements only with source-tagged links and a relevant developer offer.
  • Reject paid link schemes and irrelevant directory volume.

DevRel-to-sales boundary

DevRel educates and earns trust; it does not disguise sales outreach as community help. Hand off an account only when product usage, team expansion, security/procurement questions or explicit intent creates a qualified signal. Tell the developer when a commercial teammate is joining.

30-day operating plan

  • Week 1: baseline journey, interview five developers, identify one bottleneck.
  • Week 2: repair the highest-frequency docs/product failure and ship one proof asset.
  • Week 3: distribute through two relevant communities or ecosystem partners.
  • Week 4: compare activation/retention against baseline and decide keep, change or stop.

Required output

Return a developer journey, bottleneck diagnosis, 30-day plan, channel owners, measurement schema, community escalation rules and a monthly executive report connecting activity to activated/retained developers.

Compliance

Never buy stars, fake community activity, conceal sponsorship, scrape private member data or manufacture benchmarks. Obtain consent before using developer stories or code.

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