Sync tested skill from gingiris-skills 9deb2a5

SKILL.md

@@ -0,0 +1,104 @@
+---
+name: devrel-playbook
+description: 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.
+---
+
+# 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:
+
+| Problem | Evidence | First intervention |
+|---|---|---|
+| Discovery | ICP developers do not know the project | technical content and ecosystem distribution |
+| Understanding | Docs traffic is high, quickstart completion is low | README/docs usability tests |
+| Activation | Keys/SDK installed, first successful call is low | sample app and error-path repair |
+| Retention | Developers try once and disappear | use-case education, office hours, lifecycle prompts |
+| Contribution | Users want changes but do not contribute | issue design, maintainer SLA, contributor onboarding |
+| Enterprise pull | Teams use product but procurement is invisible | usage-qualified account handoff to sales |
+
+## Developer journey instrumentation
+
+Track:
+
+```text
+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:
+
+```text
+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.