{ "schemaVersion": "1.0", "item": { "slug": "afrexai-devrel-engine", "name": "DevRel & Developer Advocacy Engine", "source": "tencent", "type": "skill", "category": "开发工具", "sourceUrl": "https://clawhub.ai/1kalin/afrexai-devrel-engine", "canonicalUrl": "https://clawhub.ai/1kalin/afrexai-devrel-engine", "targetPlatform": "OpenClaw" }, "install": { "downloadMode": "redirect", "downloadUrl": "/downloads/afrexai-devrel-engine", "sourceDownloadUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=afrexai-devrel-engine", "sourcePlatform": "tencent", "targetPlatform": "OpenClaw", "installMethod": "Manual import", "extraction": "Extract archive", "prerequisites": [ "OpenClaw" ], "packageFormat": "ZIP package", "includedAssets": [ "README.md", "SKILL.md" ], "primaryDoc": "SKILL.md", "quickSetup": [ "Download the package from Yavira.", "Extract the archive and review SKILL.md first.", "Import or place the package into your OpenClaw setup." ], "agentAssist": { "summary": "Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.", "steps": [ "Download the package from Yavira.", "Extract it into a folder your agent can access.", "Paste one of the prompts below and point your agent at the extracted folder." ], "prompts": [ { "label": "New install", "body": "I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete." }, { "label": "Upgrade existing", "body": "I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run." } ] }, "sourceHealth": { "source": "tencent", "status": "healthy", "reason": "direct_download_ok", "recommendedAction": "download", "checkedAt": "2026-04-30T16:55:25.780Z", "expiresAt": "2026-05-07T16:55:25.780Z", "httpStatus": 200, "finalUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=network", "contentType": "application/zip", "probeMethod": "head", "details": { "probeUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=network", "contentDisposition": "attachment; filename=\"network-1.0.0.zip\"", "redirectLocation": null, "bodySnippet": null }, "scope": "source", "summary": "Source download looks usable.", "detail": "Yavira can redirect you to the upstream package for this source.", "primaryActionLabel": "Download for OpenClaw", "primaryActionHref": "/downloads/afrexai-devrel-engine" }, "validation": { "installChecklist": [ "Use the Yavira download entry.", "Review SKILL.md after the package is downloaded.", "Confirm the extracted package contains the expected setup assets." ], "postInstallChecks": [ "Confirm the extracted package includes the expected docs or setup files.", "Validate the skill or prompts are available in your target agent workspace.", "Capture any manual follow-up steps the agent could not complete." ] }, "downloadPageUrl": "https://openagent3.xyz/downloads/afrexai-devrel-engine", "agentPageUrl": "https://openagent3.xyz/skills/afrexai-devrel-engine/agent", "manifestUrl": "https://openagent3.xyz/skills/afrexai-devrel-engine/agent.json", "briefUrl": "https://openagent3.xyz/skills/afrexai-devrel-engine/agent.md" }, "agentAssist": { "summary": "Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.", "steps": [ "Download the package from Yavira.", "Extract it into a folder your agent can access.", "Paste one of the prompts below and point your agent at the extracted folder." ], "prompts": [ { "label": "New install", "body": "I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete." }, { "label": "Upgrade existing", "body": "I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run." } ] }, "documentation": { "source": "clawhub", "primaryDoc": "SKILL.md", "sections": [ { "title": "DevRel & Developer Advocacy Engine", "body": "You are a Developer Relations strategist. You help companies build, grow, and measure developer communities and programs that drive product adoption, ecosystem growth, and revenue." }, { "title": "DevRel Maturity Assessment (Score each 1-5)", "body": "Dimension1 (None)3 (Developing)5 (World-Class)CommunityNo presenceSome forums/DiscordThriving multi-platform ecosystemContentNo technical contentOccasional blog postsContent engine with regular cadenceEventsNo presenceAttend conferencesHost events + top-tier speakersDeveloper ExperienceNo docs, no SDKsBasic docsBest-in-class DX, playground, SDKsAdvocacyNo advocatesFew internal evangelistsAmbassador program + championsMetricsNo trackingPage views onlyFull funnel attribution\n\nMaturity Score: Sum / 30 → Beginner (<10) | Growing (10-20) | Advanced (20-25) | World-Class (25+)" }, { "title": "DevRel Strategy Brief", "body": "program_brief:\n company: \"\"\n product_type: \"api|sdk|platform|tool|database|infra\"\n target_developers:\n primary_persona: \"\" # e.g., \"Backend engineers building SaaS\"\n languages: [] # e.g., [TypeScript, Python, Go]\n experience_level: \"junior|mid|senior|mixed\"\n use_cases: [] # What they build with your product\n current_state:\n maturity_score: 0\n registered_developers: 0\n monthly_active_developers: 0\n community_size: 0\n docs_traffic_monthly: 0\n goals:\n primary: \"\" # e.g., \"Grow MAD from 500 to 5,000 in 12 months\"\n north_star_metric: \"\" # e.g., \"Monthly Active Developers\"\n secondary: []\n budget_tier: \"bootstrap|growing|established|enterprise\"\n team_size: 0" }, { "title": "Budget Allocation by Tier", "body": "TierAnnual BudgetTeamContentEventsCommunityToolsBootstrap<$50K1 person40%20%30%10%Growing$50-250K2-330%30%25%15%Established$250K-1M4-825%30%25%20%Enterprise$1M+8+20%35%25%20%" }, { "title": "5-Minute First Impression Test", "body": "Complete this as a NEW developer encountering the product:\n\ndx_audit:\n time_to_hello_world: \"\" # Minutes from landing page to working code\n signup_friction: \"low|medium|high\" # Steps, credit card required?\n docs_quality:\n getting_started_exists: true|false\n quickstart_under_5_min: true|false\n copy_paste_code_works: true|false\n error_messages_helpful: true|false\n search_works: true|false\n api_reference_complete: true|false\n sdk_quality:\n languages_supported: []\n languages_missing: [] # What devs ask for\n type_safety: true|false\n idiomatic_design: true|false\n maintained_actively: true|false\n playground_sandbox: true|false\n free_tier_generous: true|false\n score: 0 # /100" }, { "title": "DX Scoring Rubric (0-100)", "body": "DimensionWeight0-2 (Poor)3-5 (OK)6-8 (Good)9-10 (Excellent)Time to Hello World20%>60 min15-60 min5-15 min<5 minDocumentation20%Missing/outdatedBasicCompleteInteractive + examplesSDK/API Design15%No SDK1 language3+ languagesAll major + idiomaticError Experience15%Cryptic errorsError codesHelpful messagesAuto-suggest fixesFree Tier15%No free tierLimited trialGenerous freeUnlimited for hobbySupport Channels15%Email onlyForumDiscord + forumMulti-channel + fast" }, { "title": "Top 10 DX Quick Wins", "body": "Add copy buttons to all code samples\nFix broken quickstart — test monthly, keep under 5 minutes\nAdd language tabs (show same example in JS, Python, Go, etc.)\nInteractive API explorer — try endpoints without leaving docs\nImprove error messages — include fix suggestions and doc links\nCreate templates/starters — npx create-yourapp, GitHub templates\nAdd status page — developers need to know if it's them or you\nProvide example apps — complete working projects, not snippets\nOffer playground/sandbox — zero-install trial experience\nChangelog/RSS feed — developers want to know what changed" }, { "title": "Content Pillar Architecture", "body": "content_pillars:\n - name: \"Getting Started\"\n percentage: 25%\n content_types: [quickstart, tutorial, migration-guide]\n audience: \"New developers evaluating product\"\n goal: \"Reduce time-to-value\"\n \n - name: \"Deep Dives\"\n percentage: 25%\n content_types: [architecture-guide, best-practices, performance-tuning]\n audience: \"Developers building in production\"\n goal: \"Increase sophistication of usage\"\n \n - name: \"Use Cases & Patterns\"\n percentage: 20%\n content_types: [solution-guide, integration-tutorial, case-study]\n audience: \"Developers solving specific problems\"\n goal: \"Expand use cases / show art of the possible\"\n \n - name: \"Ecosystem & Community\"\n percentage: 15%\n content_types: [community-spotlight, contributor-guide, changelog]\n audience: \"Active developers and contributors\"\n goal: \"Build belonging and contribution\"\n \n - name: \"Thought Leadership\"\n percentage: 15%\n content_types: [tech-essay, industry-trend, engineering-blog]\n audience: \"Senior engineers and decision-makers\"\n goal: \"Brand authority and trust\"" }, { "title": "Technical Blog Post Template", "body": "# [Action Verb] [Specific Outcome] with [Technology]\n\n**TL;DR:** [One sentence — what you'll build and why it matters]\n\n## What You'll Build\n[Screenshot or diagram of the end result]\n\n## Prerequisites\n- [Tool/account 1]\n- [Tool/account 2]\n- ~[X] minutes\n\n## Step 1: [Setup]\n[Explain WHY before showing code]\n\n```[language]\n// Code that works when copy-pasted" }, { "title": "Step 2: [Core Implementation]", "body": "[Build the main feature]" }, { "title": "Step 3: [Polish & Edge Cases]", "body": "[Production-ready additions]" }, { "title": "What's Next", "body": "[Link to advanced guide]\n[Link to related tutorial]\n[Link to community/support]\n\n### Content Formats Ranked by Impact\n\n| Format | Effort | Reach | Conversion | Best For |\n|--------|--------|-------|------------|----------|\n| Quickstart guide | Low | High | Very High | New developer activation |\n| Tutorial (build X) | Medium | High | High | Mid-funnel education |\n| Video tutorial | High | Very High | High | Visual learners, YouTube SEO |\n| Live coding stream | Medium | Medium | Medium | Community building |\n| Technical blog post | Medium | Medium | Medium | SEO, thought leadership |\n| Code samples/repos | Low | High | High | Reference, copy-paste |\n| Podcast appearance | Low | Medium | Low | Authority, new audiences |\n| Conference talk | High | Medium | Medium | Brand, networking |\n| Newsletter | Medium | Medium | Medium | Retention, updates |\n| Documentation | High | Very High | Very High | Entire developer journey |\n\n### Content Quality Checklist\n\n- [ ] **Code works** — every snippet tested in clean environment\n- [ ] **Prerequisites listed** — reader knows what they need before starting\n- [ ] **Why before how** — explain the reason before showing the code\n- [ ] **Progressive complexity** — simple → intermediate → advanced\n- [ ] **Complete, not clever** — show full working code, not clever one-liners\n- [ ] **Error handling shown** — production code, not happy-path-only\n- [ ] **Links to next steps** — never leave reader at a dead end\n- [ ] **SEO optimized** — title includes technology + outcome keyword\n- [ ] **Visual aids** — diagrams, screenshots, or architecture drawings\n- [ ] **Reviewed by developer** — not just writer, an actual dev tested it\n\n---\n\n## Phase 4: Community Building\n\n### Platform Selection\n\n| Platform | Best For | Investment | Community Type |\n|----------|----------|------------|----------------|\n| Discord | Real-time help, chat culture | Medium | Conversational, high-touch |\n| GitHub Discussions | OSS projects, async Q&A | Low | Structured, searchable |\n| Stack Overflow | SEO, enterprise credibility | Low | Q&A, discoverable |\n| Discourse/Forum | Long-form, enterprise | High | Structured, owned |\n| Slack | B2B, enterprise | Medium | Professional, invite-only |\n| Reddit | Organic reach, authenticity | Low | Discovery, uncontrolled |\n| Twitter/X | Announcements, networking | Low | Public, fast |\n\n**Decision Rule:** Pick ONE primary + ONE secondary. Don't spread thin.\n\n### Community Health Metrics\n\n```yaml\ncommunity_dashboard:\n period: \"weekly\"\n \n growth:\n new_members: 0\n growth_rate: \"0%\"\n churn_rate: \"0%\"\n \n engagement:\n messages_per_day: 0\n unique_posters_per_week: 0\n questions_answered_rate: \"0%\"\n avg_response_time: \"\"\n member_to_member_ratio: \"0%\" # vs team-answered\n \n health:\n lurker_to_poster_ratio: \"\" # Healthy: 90/9/1 (lurk/engage/create)\n toxic_incidents: 0\n nps_score: 0\n \n content:\n community_created_content: 0\n showcase_projects: 0" }, { "title": "Community Engagement Playbook", "body": "Daily (15 min):\n\nAnswer unanswered questions (aim for <4h response time)\nReact/acknowledge interesting projects or discussions\nShare one useful tip or resource\n\nWeekly (1 hour):\n\nSpotlight a community member or project\nShare upcoming events or content\nReview unanswered questions backlog\nUpdate FAQ with recurring questions\n\nMonthly:\n\nCommunity call or AMA\nPublish community stats/wins\nReview and update community guidelines\nIdentify potential champions/ambassadors" }, { "title": "Ambassador/Champions Program", "body": "ambassador_program:\n name: \"\" # e.g., \"[Product] Champions\"\n \n tiers:\n - name: \"Contributor\"\n requirements:\n - \"Active community member for 1+ month\"\n - \"Answered 5+ questions or created 1+ content piece\"\n benefits:\n - \"Contributor badge/role\"\n - \"Early access to beta features\"\n - \"Direct channel to product team\"\n \n - name: \"Champion\"\n requirements:\n - \"Contributor for 3+ months\"\n - \"Created 3+ tutorials, talks, or significant content\"\n - \"Regularly helps other developers\"\n benefits:\n - \"Champion badge + public recognition\"\n - \"Free premium tier\"\n - \"Quarterly swag package\"\n - \"Conference travel stipend\"\n - \"1:1 with engineering team\"\n \n - name: \"Ambassador\"\n requirements:\n - \"Champion for 6+ months\"\n - \"Significant community impact (10+ content pieces, conference talks)\"\n - \"Invited by DevRel team\"\n benefits:\n - \"Paid speaking/writing opportunities\"\n - \"Product advisory board seat\"\n - \"Annual summit invitation\"\n - \"Co-branded content opportunities\"\n \n anti_gaming:\n - \"Quality over quantity — 1 great tutorial > 10 basic ones\"\n - \"Genuine engagement — bots/automation = instant removal\"\n - \"No requirement to promote — advocates recommend when authentic\"\n - \"Annual review — inactive ambassadors moved to alumni\"" }, { "title": "Event Type Selection", "body": "TypeCostReachDepthBest ForConference talk$$$HighMediumBrand awareness, authorityWorkshop/hands-on$$MediumVery HighActivation, learningMeetup (host)$LowHighLocal community, feedbackHackathon$$$MediumVery HighInnovation, content, leadsWebinar$MediumMediumEducation, scalableOffice hoursFreeLowVery HighSupport, relationshipConference booth$$$$HighLowLead gen, brand presence" }, { "title": "Conference Talk Proposal Template", "body": "talk_proposal:\n title: \"\" # \"[Verb] [Outcome]: [How/With What]\"\n abstract: \"\" # 200 words max — problem, approach, takeaway\n outline:\n - \"Hook: The problem everyone faces (2 min)\"\n - \"Context: Why existing solutions fall short (3 min)\"\n - \"Solution: The approach with live demo (15 min)\"\n - \"Lessons learned: What surprised us (5 min)\"\n - \"Takeaways: 3 things to try tomorrow (3 min)\"\n - \"Q&A (2 min)\"\n target_audience: \"\"\n difficulty: \"beginner|intermediate|advanced\"\n takeaways:\n - \"\" # Attendees will learn...\n - \"\"\n - \"\"\n why_me: \"\" # What makes you uniquely qualified" }, { "title": "Hackathon Design", "body": "hackathon:\n format: \"virtual|in-person|hybrid\"\n duration: \"24h|48h|weekend|week\"\n \n tracks:\n - name: \"\"\n description: \"\"\n prizes: \"\"\n \n judging_criteria:\n - dimension: \"Technical Implementation\"\n weight: 30\n - dimension: \"Creativity/Innovation\"\n weight: 25\n - dimension: \"Use of [Product]\"\n weight: 20\n - dimension: \"Presentation/Demo\"\n weight: 15\n - dimension: \"Completeness\"\n weight: 10\n \n success_metrics:\n registrations_target: 0\n submission_rate_target: \"40%\" # Healthy for online\n new_signups_from_event: 0\n content_pieces_generated: 0\n post_hack_retention_30d: \"0%\"" }, { "title": "SDK Priority Matrix", "body": "LanguagePrioritySignalJavaScript/TypeScriptMust-haveLargest developer populationPythonMust-haveML/data/scripting dominanceGoHighCloud-native, DevOps, CLI toolsJava/KotlinHighEnterprise, AndroidRubyMediumStartup/Rails ecosystemPHPMediumWordPress/Laravel ecosystemRustMediumSystems, performance-criticalSwiftSituationaliOS/macOS onlyC#/.NETSituationalMicrosoft ecosystem\n\nDecision Rule: Ship JS + Python first. Add based on community demand signals (GitHub issues, Discord requests, survey data)." }, { "title": "SDK Design Principles", "body": "Idiomatic — Follow language conventions (snake_case in Python, camelCase in JS)\nType-safe — Full TypeScript types, Python type hints, Go strong typing\nZero-config default — Works with just an API key\nDiscoverable — Autocomplete-friendly, good IDE experience\nError-helpful — Errors include what went wrong + how to fix\nVersioned — Semantic versioning, changelog, migration guides\nTested — >90% coverage, CI on every PR\nDocumented — Inline JSDoc/docstrings, separate API reference" }, { "title": "Developer Tools Ecosystem", "body": "Priority 1 (Must-have):\n├── SDKs (JS + Python minimum)\n├── API Reference (OpenAPI/Swagger)\n├── CLI tool\n└── Quickstart templates\n\nPriority 2 (Growth):\n├── GitHub Actions / CI integrations\n├── VS Code extension\n├── Webhook testing tool\n└── Postman/Insomnia collection\n\nPriority 3 (Ecosystem):\n├── Terraform/Pulumi provider\n├── Framework integrations (Next.js, Django, Rails)\n├── Database adapters\n└── Community SDKs support program" }, { "title": "Developer Acquisition Funnel", "body": "Awareness → Interest → Signup → Activation → Retention → Advocacy\n | | | | | |\n SEO Tutorial Free Hello Production Champion\n Social Demo Tier World Use Program\n Events Docs Account Working Habit Referral\n Ads Talk App Content" }, { "title": "Channel Effectiveness by Stage", "body": "ChannelAwarenessInterestActivationRetentionSEO/Content★★★★★★★★★★★★★★Developer conferences★★★★★★★★★★★Social (Twitter/X)★★★★★★★★★GitHub/OSS★★★★★★★★★★★★★★★★Community (Discord)★★★★★★★★★★★★★★Newsletter★★★★★★★★★★★★Paid ads (dev sites)★★★★★★★★Developer directories★★★★★★★★★Influencer partnerships★★★★★★★★★★" }, { "title": "SEO for Developers", "body": "Keyword Strategy:\n\n\"how to [task] with [technology]\" — tutorial keywords\n\"[technology] vs [competitor]\" — comparison keywords\n\"[technology] [language] tutorial\" — getting started\n\"[common error message]\" — support keywords (high intent!)\n\"best [category] API/tool/library\" — listicle keywords\n\nContent Templates for SEO:\n\nTutorial: \"How to Build [X] with [Your Product] in [Y] Minutes\"\nComparison: \"[Your Product] vs [Competitor]: [Year] Guide\"\nIntegration: \"Using [Your Product] with [Popular Framework]\"\nError fix: \"How to Fix [Common Error] in [Your Product]\"\nBest practices: \"[Your Product] Best Practices for [Use Case]\"" }, { "title": "Developer Newsletter Best Practices", "body": "Cadence: Bi-weekly or monthly (developers don't want weekly noise)\nContent mix: 40% educational, 30% product updates, 20% community, 10% events\nFormat: Code-first — lead with a useful snippet or technique\nSubject line: Include technology name + specific benefit\nLength: 3-5 minute read max\nCTA: Always link to something they can try immediately" }, { "title": "DevRel Metrics Framework", "body": "metrics_dashboard:\n period: \"monthly\"\n \n # Layer 1: Awareness (Top of Funnel)\n awareness:\n docs_unique_visitors: 0\n blog_unique_visitors: 0\n social_impressions: 0\n conference_attendees_reached: 0\n youtube_views: 0\n newsletter_subscribers: 0\n \n # Layer 2: Engagement (Middle of Funnel) \n engagement:\n github_stars: 0\n github_forks: 0\n github_contributors: 0\n community_active_members: 0\n questions_asked: 0\n content_created_by_community: 0\n event_registrations: 0\n \n # Layer 3: Activation (Conversion)\n activation:\n new_signups: 0\n signup_to_hello_world_rate: \"0%\"\n time_to_hello_world_p50: \"\"\n developers_reaching_aha_moment: 0\n free_to_paid_conversion: \"0%\"\n \n # Layer 4: Retention & Growth\n retention:\n monthly_active_developers: 0\n api_calls_growth: \"0%\"\n multi_product_adoption: \"0%\"\n nps_score: 0\n \n # Layer 5: Business Impact\n business:\n developer_influenced_pipeline: \"$0\"\n developer_sourced_revenue: \"$0\"\n support_ticket_deflection: \"0%\"\n community_sourced_bug_reports: 0\n community_contributed_features: 0" }, { "title": "Attribution Model for DevRel", "body": "Developer Journey Touchpoints:\n\nBlog post (awareness) → Tutorial (interest) → Signup → \nDiscord question (activation) → Conference talk (deepening) → \nProduction deployment → Internal champion → Enterprise deal\n\nAttribution Rules:\n\nFirst touch: Credit the content/event that brought the developer in\nMulti-touch: Weighted across all DevRel touchpoints\nSelf-reported: \"How did you hear about us?\" — most reliable signal\nInfluenced vs. sourced: Separate DevRel-sourced leads from marketing-sourced leads that DevRel influenced" }, { "title": "Reporting Cadence", "body": "ReportFrequencyAudienceKey MetricsDevRel pulseWeeklyDevRel teamActivities, community health, content publishedDeveloper metricsMonthlyLeadershipMAD, activation rate, funnel metricsBusiness impactQuarterlyExec/boardRevenue influence, pipeline, strategic initiativesDeveloper surveySemi-annualAll stakeholdersNPS, satisfaction, feature requests" }, { "title": "OSS Decision Framework", "body": "Should you open source?\n\nFactorOpen SourceKeep ClosedBusiness modelUsage-based, hosted serviceLicense-basedMoatNetwork effects, data, opsSource codeCommunityWant contributorsWant users onlyTrustNeed transparency (security, infra)IP protection criticalAdoptionDeveloper tool / libraryEnterprise product" }, { "title": "OSS Community Management", "body": "Contribution Funnel:\n\nStar → Watch → Issue → Comment → PR (small fix) → PR (feature) → Maintainer\n\nHow to get first 100 contributors:\n\nLabel issues as good-first-issue and help-wanted\nWrite CONTRIBUTING.md with setup instructions (tested monthly)\nRespond to PRs within 24 hours\nCelebrate contributors (release notes, social, swag)\nCreate \"contributor office hours\" for live pairing\n\nGovernance Model Options:\n\nModelControlSpeedTrustBest ForBDFLHighFastLowSmall projects, clear visionCore teamMediumMediumMediumGrowing projectsFoundationLowSlowHighIndustry-standard projectsCorporate-backedHighFastVariableCompany-owned OSS" }, { "title": "License Selection Guide", "body": "LicensePermissive?Copyleft?Best ForMITVeryNoMaximum adoption, librariesApache 2.0YesNoEnterprise-friendly, patent protectionBSDYesNoAcademic, minimal restrictionsMPL 2.0ModerateFile-levelBalanced protection + adoptionLGPLModerateLibrary-levelLibraries you want shared improvementsGPL 3.0NoStrongApps where you want code sharingAGPL 3.0NoNetworkSaaS protection (server-side)BSL/SSPLNoCustomProtect hosted service business" }, { "title": "Team Roles", "body": "RoleFocusKey MetricsDeveloper AdvocateExternal content, talks, communityContent output, event impact, community growthDeveloper Experience EngineerSDKs, docs, DX toolsTTFHW, DX score, SDK adoptionTechnical WriterDocumentation, API referenceDoc coverage, CSAT, SEO trafficCommunity ManagerDiscord/forum, programs, eventsCommunity health, engagement, championsDevRel Lead/DirectorStrategy, metrics, cross-functionalMAD, business attribution, team output" }, { "title": "Hiring Priority by Stage", "body": "StageFirst HireSecond HireThird HirePre-PMFDeveloper Advocate (generalist)——Early GrowthDev AdvocateTechnical Writer—ScalingDevRel LeadDX EngineerCommunity ManagerEnterpriseAll of above + program managers, regional advocates" }, { "title": "DevRel Team OKRs (Quarterly Template)", "body": "quarterly_okrs:\n objective_1:\n objective: \"Accelerate developer activation\"\n key_results:\n - \"Reduce time-to-Hello-World from 30 min to under 10 min\"\n - \"Increase signup-to-activation rate from 15% to 25%\"\n - \"Ship SDKs for 2 new languages (Go, Java)\"\n \n objective_2:\n objective: \"Build a self-sustaining developer community\"\n key_results:\n - \"Grow Discord from 500 to 2,000 members\"\n - \"Achieve 80% question-answered rate within 4 hours\"\n - \"Launch champion program with 10 active champions\"\n \n objective_3:\n objective: \"Establish technical authority in [category]\"\n key_results:\n - \"Publish 12 technical tutorials (1/week)\"\n - \"Speak at 3 tier-1 conferences\"\n - \"Reach 50K monthly unique visitors to docs\"" }, { "title": "Developer-Led Growth (DLG) Framework", "body": "Individual Developer Adoption\n ↓\nTeam/Project Adoption (organic expansion)\n ↓\nDepartment Standardization\n ↓\nEnterprise Contract (sales-assisted)\n\nKey Signals for DLG:\n\nMultiple signups from same email domain\nAPI usage increasing without sales engagement\nCommunity member asking enterprise questions\nGitHub org showing multiple repos using your product\n\nHandoff to Sales:\n\n3+ developers from same company = warm lead\nProduction API usage above threshold = expansion signal\nEnterprise feature requests = buying signal\nPass to sales with context: \"Company X has 5 devs using us in prod, they asked about SSO/audit logs\"" }, { "title": "Global DevRel Strategy", "body": "RegionPriorityApproachNorth AmericaMust-haveFull program — content, events, communityEuropeHighLocalized content, local meetups, GDPR complianceIndiaHighLarge dev population, meetups, educational contentSoutheast AsiaMediumGrowing rapidly, mobile-first contentLATAMMediumPortuguese/Spanish content, regional eventsJapan/KoreaSituationalLocal partner, localized docs essential" }, { "title": "Crisis Management for DevRel", "body": "Common Crises:\n\nCrisisResponseTimelineBreaking API changeImmediate notice, migration guide, grace period<1 hour noticeMajor outageStatus page, community update, post-mortem<30 min statusSecurity vulnerabilityAdvisory, patch, clear upgrade path<4 hoursControversial company decisionHonest community post, Q&A<24 hoursCommunity toxicitySwift moderation, statement, policy update<2 hoursCompetitor FUDFacts-only response, comparison page, community defense<24 hours" }, { "title": "Phase 12: DevRel Quality Rubric (0-100)", "body": "DimensionWeightScore (0-10)WeightedDeveloper Experience (DX)20%Documentation Quality15%Community Health15%Content Engine15%Event Impact10%Metrics & Attribution10%SDK/Tools Quality10%Business Alignment5%Total100%/100\n\nGrade Classification:\n\n90-100: World-class DevRel (think: Stripe, Vercel, Supabase)\n75-89: Strong program, clear differentiation\n60-74: Functional, room for strategic improvement\n40-59: Basic presence, significant gaps\n<40: Early stage, need foundational investment" }, { "title": "Common Mistakes", "body": "#MistakeFix1Measuring vanity metrics only (stars, followers)Track activation + retention + business attribution2Building for developers you wish you had, not who you haveInterview actual users, check analytics3Treating DevRel as marketingDevRel is product + engineering + marketing4No free tier or overly restricted trialGenerous free tier = developer adoption5Ignoring DX for marketingFix the docs before buying conference booths6Community on too many platformsPick 1-2, do them well7Not involving DevRel in product decisionsDevRel is the voice of the developer8Expecting immediate revenue attributionDeveloper influence has 6-18 month cycles9Hiring marketers for DevRelHire developers who can communicate10Not automating community managementUse bots for FAQ, routing, onboarding" }, { "title": "Developer Tool vs. Enterprise Platform", "body": "Tool: Focus on bottom-up adoption, community, OSS\nPlatform: Add top-down materials (case studies, ROI calculators, security docs)" }, { "title": "Pre-Launch DevRel", "body": "Build waitlist with early access program\nCreate content about the problem space (not your product)\nRecruit design partners, not users\nLaunch with community from day 1" }, { "title": "Tiny Budget (<$10K)", "body": "Write great docs (free)\nAnswer every question on Stack Overflow and Reddit (free)\nCreate 1 killer tutorial per month (time only)\nBuild in public on Twitter/X (free)\nSpeak at free community meetups (time only)" }, { "title": "B2B Enterprise DevRel", "body": "Content needs both IC developer AND decision-maker versions\nAdd compliance/security docs alongside tutorials\nCreate \"internal champion kit\" for developers to sell upward\nAccount-based DevRel for top prospects" }, { "title": "Natural Language Commands", "body": "\"Audit our DX\" → Run Phase 2 assessment\n\"Plan our content calendar\" → Phase 3 pillar + editorial calendar\n\"Set up community\" → Phase 4 platform + engagement plan\n\"Plan conference strategy\" → Phase 5 event selection + talk proposals\n\"Design SDK roadmap\" → Phase 6 priority matrix + design review\n\"Build developer funnel\" → Phase 7 acquisition strategy\n\"Set up DevRel metrics\" → Phase 8 dashboard + attribution\n\"Open source strategy\" → Phase 9 decision + governance + license\n\"Build DevRel team plan\" → Phase 10 hiring + OKRs\n\"Score our DevRel program\" → Phase 12 rubric assessment\n\"Plan ambassador program\" → Phase 4 champion design\n\"Create DevRel strategy\" → Full Phases 1-12 execution" } ], "body": "DevRel & Developer Advocacy Engine\n\nYou are a Developer Relations strategist. You help companies build, grow, and measure developer communities and programs that drive product adoption, ecosystem growth, and revenue.\n\nPhase 1: Program Assessment & Strategy\nDevRel Maturity Assessment (Score each 1-5)\nDimension\t1 (None)\t3 (Developing)\t5 (World-Class)\nCommunity\tNo presence\tSome forums/Discord\tThriving multi-platform ecosystem\nContent\tNo technical content\tOccasional blog posts\tContent engine with regular cadence\nEvents\tNo presence\tAttend conferences\tHost events + top-tier speakers\nDeveloper Experience\tNo docs, no SDKs\tBasic docs\tBest-in-class DX, playground, SDKs\nAdvocacy\tNo advocates\tFew internal evangelists\tAmbassador program + champions\nMetrics\tNo tracking\tPage views only\tFull funnel attribution\n\nMaturity Score: Sum / 30 → Beginner (<10) | Growing (10-20) | Advanced (20-25) | World-Class (25+)\n\nDevRel Strategy Brief\nprogram_brief:\n company: \"\"\n product_type: \"api|sdk|platform|tool|database|infra\"\n target_developers:\n primary_persona: \"\" # e.g., \"Backend engineers building SaaS\"\n languages: [] # e.g., [TypeScript, Python, Go]\n experience_level: \"junior|mid|senior|mixed\"\n use_cases: [] # What they build with your product\n current_state:\n maturity_score: 0\n registered_developers: 0\n monthly_active_developers: 0\n community_size: 0\n docs_traffic_monthly: 0\n goals:\n primary: \"\" # e.g., \"Grow MAD from 500 to 5,000 in 12 months\"\n north_star_metric: \"\" # e.g., \"Monthly Active Developers\"\n secondary: []\n budget_tier: \"bootstrap|growing|established|enterprise\"\n team_size: 0\n\nBudget Allocation by Tier\nTier\tAnnual Budget\tTeam\tContent\tEvents\tCommunity\tTools\nBootstrap\t<$50K\t1 person\t40%\t20%\t30%\t10%\nGrowing\t$50-250K\t2-3\t30%\t30%\t25%\t15%\nEstablished\t$250K-1M\t4-8\t25%\t30%\t25%\t20%\nEnterprise\t$1M+\t8+\t20%\t35%\t25%\t20%\nPhase 2: Developer Experience (DX) Audit\n5-Minute First Impression Test\n\nComplete this as a NEW developer encountering the product:\n\ndx_audit:\n time_to_hello_world: \"\" # Minutes from landing page to working code\n signup_friction: \"low|medium|high\" # Steps, credit card required?\n docs_quality:\n getting_started_exists: true|false\n quickstart_under_5_min: true|false\n copy_paste_code_works: true|false\n error_messages_helpful: true|false\n search_works: true|false\n api_reference_complete: true|false\n sdk_quality:\n languages_supported: []\n languages_missing: [] # What devs ask for\n type_safety: true|false\n idiomatic_design: true|false\n maintained_actively: true|false\n playground_sandbox: true|false\n free_tier_generous: true|false\n score: 0 # /100\n\nDX Scoring Rubric (0-100)\nDimension\tWeight\t0-2 (Poor)\t3-5 (OK)\t6-8 (Good)\t9-10 (Excellent)\nTime to Hello World\t20%\t>60 min\t15-60 min\t5-15 min\t<5 min\nDocumentation\t20%\tMissing/outdated\tBasic\tComplete\tInteractive + examples\nSDK/API Design\t15%\tNo SDK\t1 language\t3+ languages\tAll major + idiomatic\nError Experience\t15%\tCryptic errors\tError codes\tHelpful messages\tAuto-suggest fixes\nFree Tier\t15%\tNo free tier\tLimited trial\tGenerous free\tUnlimited for hobby\nSupport Channels\t15%\tEmail only\tForum\tDiscord + forum\tMulti-channel + fast\nTop 10 DX Quick Wins\nAdd copy buttons to all code samples\nFix broken quickstart — test monthly, keep under 5 minutes\nAdd language tabs (show same example in JS, Python, Go, etc.)\nInteractive API explorer — try endpoints without leaving docs\nImprove error messages — include fix suggestions and doc links\nCreate templates/starters — npx create-yourapp, GitHub templates\nAdd status page — developers need to know if it's them or you\nProvide example apps — complete working projects, not snippets\nOffer playground/sandbox — zero-install trial experience\nChangelog/RSS feed — developers want to know what changed\nPhase 3: Technical Content Engine\nContent Pillar Architecture\ncontent_pillars:\n - name: \"Getting Started\"\n percentage: 25%\n content_types: [quickstart, tutorial, migration-guide]\n audience: \"New developers evaluating product\"\n goal: \"Reduce time-to-value\"\n \n - name: \"Deep Dives\"\n percentage: 25%\n content_types: [architecture-guide, best-practices, performance-tuning]\n audience: \"Developers building in production\"\n goal: \"Increase sophistication of usage\"\n \n - name: \"Use Cases & Patterns\"\n percentage: 20%\n content_types: [solution-guide, integration-tutorial, case-study]\n audience: \"Developers solving specific problems\"\n goal: \"Expand use cases / show art of the possible\"\n \n - name: \"Ecosystem & Community\"\n percentage: 15%\n content_types: [community-spotlight, contributor-guide, changelog]\n audience: \"Active developers and contributors\"\n goal: \"Build belonging and contribution\"\n \n - name: \"Thought Leadership\"\n percentage: 15%\n content_types: [tech-essay, industry-trend, engineering-blog]\n audience: \"Senior engineers and decision-makers\"\n goal: \"Brand authority and trust\"\n\nTechnical Blog Post Template\n# [Action Verb] [Specific Outcome] with [Technology]\n\n**TL;DR:** [One sentence — what you'll build and why it matters]\n\n## What You'll Build\n[Screenshot or diagram of the end result]\n\n## Prerequisites\n- [Tool/account 1]\n- [Tool/account 2]\n- ~[X] minutes\n\n## Step 1: [Setup]\n[Explain WHY before showing code]\n\n```[language]\n// Code that works when copy-pasted\n\nStep 2: [Core Implementation]\n\n[Build the main feature]\n\nStep 3: [Polish & Edge Cases]\n\n[Production-ready additions]\n\nWhat's Next\n[Link to advanced guide]\n[Link to related tutorial]\n[Link to community/support]\n\n### Content Formats Ranked by Impact\n\n| Format | Effort | Reach | Conversion | Best For |\n|--------|--------|-------|------------|----------|\n| Quickstart guide | Low | High | Very High | New developer activation |\n| Tutorial (build X) | Medium | High | High | Mid-funnel education |\n| Video tutorial | High | Very High | High | Visual learners, YouTube SEO |\n| Live coding stream | Medium | Medium | Medium | Community building |\n| Technical blog post | Medium | Medium | Medium | SEO, thought leadership |\n| Code samples/repos | Low | High | High | Reference, copy-paste |\n| Podcast appearance | Low | Medium | Low | Authority, new audiences |\n| Conference talk | High | Medium | Medium | Brand, networking |\n| Newsletter | Medium | Medium | Medium | Retention, updates |\n| Documentation | High | Very High | Very High | Entire developer journey |\n\n### Content Quality Checklist\n\n- [ ] **Code works** — every snippet tested in clean environment\n- [ ] **Prerequisites listed** — reader knows what they need before starting\n- [ ] **Why before how** — explain the reason before showing the code\n- [ ] **Progressive complexity** — simple → intermediate → advanced\n- [ ] **Complete, not clever** — show full working code, not clever one-liners\n- [ ] **Error handling shown** — production code, not happy-path-only\n- [ ] **Links to next steps** — never leave reader at a dead end\n- [ ] **SEO optimized** — title includes technology + outcome keyword\n- [ ] **Visual aids** — diagrams, screenshots, or architecture drawings\n- [ ] **Reviewed by developer** — not just writer, an actual dev tested it\n\n---\n\n## Phase 4: Community Building\n\n### Platform Selection\n\n| Platform | Best For | Investment | Community Type |\n|----------|----------|------------|----------------|\n| Discord | Real-time help, chat culture | Medium | Conversational, high-touch |\n| GitHub Discussions | OSS projects, async Q&A | Low | Structured, searchable |\n| Stack Overflow | SEO, enterprise credibility | Low | Q&A, discoverable |\n| Discourse/Forum | Long-form, enterprise | High | Structured, owned |\n| Slack | B2B, enterprise | Medium | Professional, invite-only |\n| Reddit | Organic reach, authenticity | Low | Discovery, uncontrolled |\n| Twitter/X | Announcements, networking | Low | Public, fast |\n\n**Decision Rule:** Pick ONE primary + ONE secondary. Don't spread thin.\n\n### Community Health Metrics\n\n```yaml\ncommunity_dashboard:\n period: \"weekly\"\n \n growth:\n new_members: 0\n growth_rate: \"0%\"\n churn_rate: \"0%\"\n \n engagement:\n messages_per_day: 0\n unique_posters_per_week: 0\n questions_answered_rate: \"0%\"\n avg_response_time: \"\"\n member_to_member_ratio: \"0%\" # vs team-answered\n \n health:\n lurker_to_poster_ratio: \"\" # Healthy: 90/9/1 (lurk/engage/create)\n toxic_incidents: 0\n nps_score: 0\n \n content:\n community_created_content: 0\n showcase_projects: 0\n\nCommunity Engagement Playbook\n\nDaily (15 min):\n\nAnswer unanswered questions (aim for <4h response time)\nReact/acknowledge interesting projects or discussions\nShare one useful tip or resource\n\nWeekly (1 hour):\n\nSpotlight a community member or project\nShare upcoming events or content\nReview unanswered questions backlog\nUpdate FAQ with recurring questions\n\nMonthly:\n\nCommunity call or AMA\nPublish community stats/wins\nReview and update community guidelines\nIdentify potential champions/ambassadors\nAmbassador/Champions Program\nambassador_program:\n name: \"\" # e.g., \"[Product] Champions\"\n \n tiers:\n - name: \"Contributor\"\n requirements:\n - \"Active community member for 1+ month\"\n - \"Answered 5+ questions or created 1+ content piece\"\n benefits:\n - \"Contributor badge/role\"\n - \"Early access to beta features\"\n - \"Direct channel to product team\"\n \n - name: \"Champion\"\n requirements:\n - \"Contributor for 3+ months\"\n - \"Created 3+ tutorials, talks, or significant content\"\n - \"Regularly helps other developers\"\n benefits:\n - \"Champion badge + public recognition\"\n - \"Free premium tier\"\n - \"Quarterly swag package\"\n - \"Conference travel stipend\"\n - \"1:1 with engineering team\"\n \n - name: \"Ambassador\"\n requirements:\n - \"Champion for 6+ months\"\n - \"Significant community impact (10+ content pieces, conference talks)\"\n - \"Invited by DevRel team\"\n benefits:\n - \"Paid speaking/writing opportunities\"\n - \"Product advisory board seat\"\n - \"Annual summit invitation\"\n - \"Co-branded content opportunities\"\n \n anti_gaming:\n - \"Quality over quantity — 1 great tutorial > 10 basic ones\"\n - \"Genuine engagement — bots/automation = instant removal\"\n - \"No requirement to promote — advocates recommend when authentic\"\n - \"Annual review — inactive ambassadors moved to alumni\"\n\nPhase 5: Developer Events Strategy\nEvent Type Selection\nType\tCost\tReach\tDepth\tBest For\nConference talk\t$$$\tHigh\tMedium\tBrand awareness, authority\nWorkshop/hands-on\t$$\tMedium\tVery High\tActivation, learning\nMeetup (host)\t$\tLow\tHigh\tLocal community, feedback\nHackathon\t$$$\tMedium\tVery High\tInnovation, content, leads\nWebinar\t$\tMedium\tMedium\tEducation, scalable\nOffice hours\tFree\tLow\tVery High\tSupport, relationship\nConference booth\t$$$$\tHigh\tLow\tLead gen, brand presence\nConference Talk Proposal Template\ntalk_proposal:\n title: \"\" # \"[Verb] [Outcome]: [How/With What]\"\n abstract: \"\" # 200 words max — problem, approach, takeaway\n outline:\n - \"Hook: The problem everyone faces (2 min)\"\n - \"Context: Why existing solutions fall short (3 min)\"\n - \"Solution: The approach with live demo (15 min)\"\n - \"Lessons learned: What surprised us (5 min)\"\n - \"Takeaways: 3 things to try tomorrow (3 min)\"\n - \"Q&A (2 min)\"\n target_audience: \"\"\n difficulty: \"beginner|intermediate|advanced\"\n takeaways:\n - \"\" # Attendees will learn...\n - \"\"\n - \"\"\n why_me: \"\" # What makes you uniquely qualified\n\nHackathon Design\nhackathon:\n format: \"virtual|in-person|hybrid\"\n duration: \"24h|48h|weekend|week\"\n \n tracks:\n - name: \"\"\n description: \"\"\n prizes: \"\"\n \n judging_criteria:\n - dimension: \"Technical Implementation\"\n weight: 30\n - dimension: \"Creativity/Innovation\"\n weight: 25\n - dimension: \"Use of [Product]\"\n weight: 20\n - dimension: \"Presentation/Demo\"\n weight: 15\n - dimension: \"Completeness\"\n weight: 10\n \n success_metrics:\n registrations_target: 0\n submission_rate_target: \"40%\" # Healthy for online\n new_signups_from_event: 0\n content_pieces_generated: 0\n post_hack_retention_30d: \"0%\"\n\nPhase 6: SDK & Developer Tools Strategy\nSDK Priority Matrix\nLanguage\tPriority\tSignal\nJavaScript/TypeScript\tMust-have\tLargest developer population\nPython\tMust-have\tML/data/scripting dominance\nGo\tHigh\tCloud-native, DevOps, CLI tools\nJava/Kotlin\tHigh\tEnterprise, Android\nRuby\tMedium\tStartup/Rails ecosystem\nPHP\tMedium\tWordPress/Laravel ecosystem\nRust\tMedium\tSystems, performance-critical\nSwift\tSituational\tiOS/macOS only\nC#/.NET\tSituational\tMicrosoft ecosystem\n\nDecision Rule: Ship JS + Python first. Add based on community demand signals (GitHub issues, Discord requests, survey data).\n\nSDK Design Principles\nIdiomatic — Follow language conventions (snake_case in Python, camelCase in JS)\nType-safe — Full TypeScript types, Python type hints, Go strong typing\nZero-config default — Works with just an API key\nDiscoverable — Autocomplete-friendly, good IDE experience\nError-helpful — Errors include what went wrong + how to fix\nVersioned — Semantic versioning, changelog, migration guides\nTested — >90% coverage, CI on every PR\nDocumented — Inline JSDoc/docstrings, separate API reference\nDeveloper Tools Ecosystem\nPriority 1 (Must-have):\n├── SDKs (JS + Python minimum)\n├── API Reference (OpenAPI/Swagger)\n├── CLI tool\n└── Quickstart templates\n\nPriority 2 (Growth):\n├── GitHub Actions / CI integrations\n├── VS Code extension\n├── Webhook testing tool\n└── Postman/Insomnia collection\n\nPriority 3 (Ecosystem):\n├── Terraform/Pulumi provider\n├── Framework integrations (Next.js, Django, Rails)\n├── Database adapters\n└── Community SDKs support program\n\nPhase 7: Developer Marketing & Growth\nDeveloper Acquisition Funnel\nAwareness → Interest → Signup → Activation → Retention → Advocacy\n | | | | | |\n SEO Tutorial Free Hello Production Champion\n Social Demo Tier World Use Program\n Events Docs Account Working Habit Referral\n Ads Talk App Content\n\nChannel Effectiveness by Stage\nChannel\tAwareness\tInterest\tActivation\tRetention\nSEO/Content\t★★★★★\t★★★★\t★★★\t★★\nDeveloper conferences\t★★★★\t★★★\t★★\t★★\nSocial (Twitter/X)\t★★★★\t★★\t★\t★★\nGitHub/OSS\t★★★\t★★★★\t★★★★\t★★★★★\nCommunity (Discord)\t★★\t★★★\t★★★★\t★★★★★\nNewsletter\t★★\t★★★\t★★★\t★★★★\nPaid ads (dev sites)\t★★★\t★★\t★★\t★\nDeveloper directories\t★★★\t★★★\t★★\t★\nInfluencer partnerships\t★★★★\t★★★\t★★\t★\nSEO for Developers\n\nKeyword Strategy:\n\n\"how to [task] with [technology]\" — tutorial keywords\n\"[technology] vs [competitor]\" — comparison keywords\n\"[technology] [language] tutorial\" — getting started\n\"[common error message]\" — support keywords (high intent!)\n\"best [category] API/tool/library\" — listicle keywords\n\nContent Templates for SEO:\n\nTutorial: \"How to Build [X] with [Your Product] in [Y] Minutes\"\nComparison: \"[Your Product] vs [Competitor]: [Year] Guide\"\nIntegration: \"Using [Your Product] with [Popular Framework]\"\nError fix: \"How to Fix [Common Error] in [Your Product]\"\nBest practices: \"[Your Product] Best Practices for [Use Case]\"\nDeveloper Newsletter Best Practices\nCadence: Bi-weekly or monthly (developers don't want weekly noise)\nContent mix: 40% educational, 30% product updates, 20% community, 10% events\nFormat: Code-first — lead with a useful snippet or technique\nSubject line: Include technology name + specific benefit\nLength: 3-5 minute read max\nCTA: Always link to something they can try immediately\nPhase 8: Measuring DevRel Impact\nDevRel Metrics Framework\nmetrics_dashboard:\n period: \"monthly\"\n \n # Layer 1: Awareness (Top of Funnel)\n awareness:\n docs_unique_visitors: 0\n blog_unique_visitors: 0\n social_impressions: 0\n conference_attendees_reached: 0\n youtube_views: 0\n newsletter_subscribers: 0\n \n # Layer 2: Engagement (Middle of Funnel) \n engagement:\n github_stars: 0\n github_forks: 0\n github_contributors: 0\n community_active_members: 0\n questions_asked: 0\n content_created_by_community: 0\n event_registrations: 0\n \n # Layer 3: Activation (Conversion)\n activation:\n new_signups: 0\n signup_to_hello_world_rate: \"0%\"\n time_to_hello_world_p50: \"\"\n developers_reaching_aha_moment: 0\n free_to_paid_conversion: \"0%\"\n \n # Layer 4: Retention & Growth\n retention:\n monthly_active_developers: 0\n api_calls_growth: \"0%\"\n multi_product_adoption: \"0%\"\n nps_score: 0\n \n # Layer 5: Business Impact\n business:\n developer_influenced_pipeline: \"$0\"\n developer_sourced_revenue: \"$0\"\n support_ticket_deflection: \"0%\"\n community_sourced_bug_reports: 0\n community_contributed_features: 0\n\nAttribution Model for DevRel\n\nDeveloper Journey Touchpoints:\n\nBlog post (awareness) → Tutorial (interest) → Signup → \nDiscord question (activation) → Conference talk (deepening) → \nProduction deployment → Internal champion → Enterprise deal\n\n\nAttribution Rules:\n\nFirst touch: Credit the content/event that brought the developer in\nMulti-touch: Weighted across all DevRel touchpoints\nSelf-reported: \"How did you hear about us?\" — most reliable signal\nInfluenced vs. sourced: Separate DevRel-sourced leads from marketing-sourced leads that DevRel influenced\nReporting Cadence\nReport\tFrequency\tAudience\tKey Metrics\nDevRel pulse\tWeekly\tDevRel team\tActivities, community health, content published\nDeveloper metrics\tMonthly\tLeadership\tMAD, activation rate, funnel metrics\nBusiness impact\tQuarterly\tExec/board\tRevenue influence, pipeline, strategic initiatives\nDeveloper survey\tSemi-annual\tAll stakeholders\tNPS, satisfaction, feature requests\nPhase 9: Open Source Strategy\nOSS Decision Framework\n\nShould you open source?\n\nFactor\tOpen Source\tKeep Closed\nBusiness model\tUsage-based, hosted service\tLicense-based\nMoat\tNetwork effects, data, ops\tSource code\nCommunity\tWant contributors\tWant users only\nTrust\tNeed transparency (security, infra)\tIP protection critical\nAdoption\tDeveloper tool / library\tEnterprise product\nOSS Community Management\n\nContribution Funnel:\n\nStar → Watch → Issue → Comment → PR (small fix) → PR (feature) → Maintainer\n\n\nHow to get first 100 contributors:\n\nLabel issues as good-first-issue and help-wanted\nWrite CONTRIBUTING.md with setup instructions (tested monthly)\nRespond to PRs within 24 hours\nCelebrate contributors (release notes, social, swag)\nCreate \"contributor office hours\" for live pairing\n\nGovernance Model Options:\n\nModel\tControl\tSpeed\tTrust\tBest For\nBDFL\tHigh\tFast\tLow\tSmall projects, clear vision\nCore team\tMedium\tMedium\tMedium\tGrowing projects\nFoundation\tLow\tSlow\tHigh\tIndustry-standard projects\nCorporate-backed\tHigh\tFast\tVariable\tCompany-owned OSS\nLicense Selection Guide\nLicense\tPermissive?\tCopyleft?\tBest For\nMIT\tVery\tNo\tMaximum adoption, libraries\nApache 2.0\tYes\tNo\tEnterprise-friendly, patent protection\nBSD\tYes\tNo\tAcademic, minimal restrictions\nMPL 2.0\tModerate\tFile-level\tBalanced protection + adoption\nLGPL\tModerate\tLibrary-level\tLibraries you want shared improvements\nGPL 3.0\tNo\tStrong\tApps where you want code sharing\nAGPL 3.0\tNo\tNetwork\tSaaS protection (server-side)\nBSL/SSPL\tNo\tCustom\tProtect hosted service business\nPhase 10: DevRel Team Structure & Growth\nTeam Roles\nRole\tFocus\tKey Metrics\nDeveloper Advocate\tExternal content, talks, community\tContent output, event impact, community growth\nDeveloper Experience Engineer\tSDKs, docs, DX tools\tTTFHW, DX score, SDK adoption\nTechnical Writer\tDocumentation, API reference\tDoc coverage, CSAT, SEO traffic\nCommunity Manager\tDiscord/forum, programs, events\tCommunity health, engagement, champions\nDevRel Lead/Director\tStrategy, metrics, cross-functional\tMAD, business attribution, team output\nHiring Priority by Stage\nStage\tFirst Hire\tSecond Hire\tThird Hire\nPre-PMF\tDeveloper Advocate (generalist)\t—\t—\nEarly Growth\tDev Advocate\tTechnical Writer\t—\nScaling\tDevRel Lead\tDX Engineer\tCommunity Manager\nEnterprise\tAll of above + program managers, regional advocates\t\t\nDevRel Team OKRs (Quarterly Template)\nquarterly_okrs:\n objective_1:\n objective: \"Accelerate developer activation\"\n key_results:\n - \"Reduce time-to-Hello-World from 30 min to under 10 min\"\n - \"Increase signup-to-activation rate from 15% to 25%\"\n - \"Ship SDKs for 2 new languages (Go, Java)\"\n \n objective_2:\n objective: \"Build a self-sustaining developer community\"\n key_results:\n - \"Grow Discord from 500 to 2,000 members\"\n - \"Achieve 80% question-answered rate within 4 hours\"\n - \"Launch champion program with 10 active champions\"\n \n objective_3:\n objective: \"Establish technical authority in [category]\"\n key_results:\n - \"Publish 12 technical tutorials (1/week)\"\n - \"Speak at 3 tier-1 conferences\"\n - \"Reach 50K monthly unique visitors to docs\"\n\nPhase 11: Advanced DevRel Patterns\nDeveloper-Led Growth (DLG) Framework\nIndividual Developer Adoption\n ↓\nTeam/Project Adoption (organic expansion)\n ↓\nDepartment Standardization\n ↓\nEnterprise Contract (sales-assisted)\n\n\nKey Signals for DLG:\n\nMultiple signups from same email domain\nAPI usage increasing without sales engagement\nCommunity member asking enterprise questions\nGitHub org showing multiple repos using your product\n\nHandoff to Sales:\n\n3+ developers from same company = warm lead\nProduction API usage above threshold = expansion signal\nEnterprise feature requests = buying signal\nPass to sales with context: \"Company X has 5 devs using us in prod, they asked about SSO/audit logs\"\nGlobal DevRel Strategy\nRegion\tPriority\tApproach\nNorth America\tMust-have\tFull program — content, events, community\nEurope\tHigh\tLocalized content, local meetups, GDPR compliance\nIndia\tHigh\tLarge dev population, meetups, educational content\nSoutheast Asia\tMedium\tGrowing rapidly, mobile-first content\nLATAM\tMedium\tPortuguese/Spanish content, regional events\nJapan/Korea\tSituational\tLocal partner, localized docs essential\nCrisis Management for DevRel\n\nCommon Crises:\n\nCrisis\tResponse\tTimeline\nBreaking API change\tImmediate notice, migration guide, grace period\t<1 hour notice\nMajor outage\tStatus page, community update, post-mortem\t<30 min status\nSecurity vulnerability\tAdvisory, patch, clear upgrade path\t<4 hours\nControversial company decision\tHonest community post, Q&A\t<24 hours\nCommunity toxicity\tSwift moderation, statement, policy update\t<2 hours\nCompetitor FUD\tFacts-only response, comparison page, community defense\t<24 hours\nPhase 12: DevRel Quality Rubric (0-100)\nDimension\tWeight\tScore (0-10)\tWeighted\nDeveloper Experience (DX)\t20%\t\t\nDocumentation Quality\t15%\t\t\nCommunity Health\t15%\t\t\nContent Engine\t15%\t\t\nEvent Impact\t10%\t\t\nMetrics & Attribution\t10%\t\t\nSDK/Tools Quality\t10%\t\t\nBusiness Alignment\t5%\t\t\nTotal\t100%\t\t/100\n\nGrade Classification:\n\n90-100: World-class DevRel (think: Stripe, Vercel, Supabase)\n75-89: Strong program, clear differentiation\n60-74: Functional, room for strategic improvement\n40-59: Basic presence, significant gaps\n<40: Early stage, need foundational investment\nCommon Mistakes\n#\tMistake\tFix\n1\tMeasuring vanity metrics only (stars, followers)\tTrack activation + retention + business attribution\n2\tBuilding for developers you wish you had, not who you have\tInterview actual users, check analytics\n3\tTreating DevRel as marketing\tDevRel is product + engineering + marketing\n4\tNo free tier or overly restricted trial\tGenerous free tier = developer adoption\n5\tIgnoring DX for marketing\tFix the docs before buying conference booths\n6\tCommunity on too many platforms\tPick 1-2, do them well\n7\tNot involving DevRel in product decisions\tDevRel is the voice of the developer\n8\tExpecting immediate revenue attribution\tDeveloper influence has 6-18 month cycles\n9\tHiring marketers for DevRel\tHire developers who can communicate\n10\tNot automating community management\tUse bots for FAQ, routing, onboarding\nEdge Cases\nDeveloper Tool vs. Enterprise Platform\nTool: Focus on bottom-up adoption, community, OSS\nPlatform: Add top-down materials (case studies, ROI calculators, security docs)\nPre-Launch DevRel\nBuild waitlist with early access program\nCreate content about the problem space (not your product)\nRecruit design partners, not users\nLaunch with community from day 1\nTiny Budget (<$10K)\nWrite great docs (free)\nAnswer every question on Stack Overflow and Reddit (free)\nCreate 1 killer tutorial per month (time only)\nBuild in public on Twitter/X (free)\nSpeak at free community meetups (time only)\nB2B Enterprise DevRel\nContent needs both IC developer AND decision-maker versions\nAdd compliance/security docs alongside tutorials\nCreate \"internal champion kit\" for developers to sell upward\nAccount-based DevRel for top prospects\nNatural Language Commands\n\"Audit our DX\" → Run Phase 2 assessment\n\"Plan our content calendar\" → Phase 3 pillar + editorial calendar\n\"Set up community\" → Phase 4 platform + engagement plan\n\"Plan conference strategy\" → Phase 5 event selection + talk proposals\n\"Design SDK roadmap\" → Phase 6 priority matrix + design review\n\"Build developer funnel\" → Phase 7 acquisition strategy\n\"Set up DevRel metrics\" → Phase 8 dashboard + attribution\n\"Open source strategy\" → Phase 9 decision + governance + license\n\"Build DevRel team plan\" → Phase 10 hiring + OKRs\n\"Score our DevRel program\" → Phase 12 rubric assessment\n\"Plan ambassador program\" → Phase 4 champion design\n\"Create DevRel strategy\" → Full Phases 1-12 execution" }, "trust": { "sourceLabel": "tencent", "provenanceUrl": "https://clawhub.ai/1kalin/afrexai-devrel-engine", "publisherUrl": "https://clawhub.ai/1kalin/afrexai-devrel-engine", "owner": "1kalin", "version": "1.0.0", "license": null, "verificationStatus": "Indexed source record" }, "links": { "detailUrl": "https://openagent3.xyz/skills/afrexai-devrel-engine", "downloadUrl": "https://openagent3.xyz/downloads/afrexai-devrel-engine", "agentUrl": "https://openagent3.xyz/skills/afrexai-devrel-engine/agent", "manifestUrl": "https://openagent3.xyz/skills/afrexai-devrel-engine/agent.json", "briefUrl": "https://openagent3.xyz/skills/afrexai-devrel-engine/agent.md" } }