Loading...
Loading...
Found 71 Skills
Designs an employer-brand strategy for attracting software engineers - the engineering EVP, the channel plan (engineering blog, OSS presence, referrals, conference talks, compensation-transparency artifacts), a verification-surface audit (employer-review sites, compensation databases, anonymous forums), and the measurement baseline. Use whenever someone raises "engineering employer brand", "why can't we attract engineers", "developer hiring content strategy", "should we publish salary bands", "tech recruiting brand", or engineering offer-acceptance dropping - even if they frame it as a recruiting problem. Covers early-stage through big-company stages, junior through staff-level targeting. Not DevRel program strategy - use samber/developer-relations-skills@devrel-strategy.
You launched an ambassador program. 3 applications. One ghosted after week 2. Should you lower the bar? Offer more perks? Spam influencers? This gives you the complete community & ambassador operations SOP — from pre-launch checklist to recruitment to tiered management to retention to governance. Built from Notion (20M users, real ambassador interviews), AFFiNE (60K stars), Asana, and ClickUp programs. By @WeiYipei. 🇨🇳 You launched an ambassador program. 3 applications came in. One dropped out in the second week. Should you lower the bar? Add more perks? Spam influencers? This SOP provides you with a complete community/ambassador operation methodology from pre-launch prerequisites to recruitment, retention, and governance. Built from practical cases of Notion (20M users, real ambassador interviews), AFFiNE (60K stars), Asana, and ClickUp. 🇯🇵 You launched an ambassador program. 3 applications. One disappeared after 2 weeks. Should you lower the standards? Add more perks? This SOP provides a complete community & ambassador operation framework from pre-launch checklist to recruitment, tiered management, retention, and governance. Built from real cases of Notion (20M users) and AFFiNE (60K stars). 🇰🇷 You launched an ambassador program. 3 applications. One disappeared after 2 weeks. Should you lower the standards? This SOP provides a complete community & ambassador operation framework from pre-launch checklist to recruitment, tiered management, retention, and governance. Built from practical cases of Notion (20M users) and AFFiNE (60K stars). Triggers: "ambassador program" | "community building" | "community management" | "DevRel" | "developer relations" | "community growth" | "ambassador program" | "community operation" | "community building" | "community operation" | "ambassador" | "community operation" | "ambassador" | "open source community" | "user retention"
Generate cold emails for B2B personas. Use when asked to write cold outreach, sales emails, or prospect messaging. Supports 19 persona archetypes (Founder-CEO, CTO, VP Engineering, CIO, CPO, Product Directors, VP CX, Head of Support, Support Ops, DevRel, Head of Docs, Technical Writer, Head of Community, VP Growth, Head of AI, etc.). Can generate first-touch and follow-up emails. When a LinkedIn profile URL is provided, uses Crustdata MCP to enrich prospect data (name, title, company, career history, recent posts) for deep personalization.
Plans a developer-platform career from the candidate side - API Product Manager, Platform Engineer/Architect, Partner/Integration Engineer. Disambiguates "platform engineer" first - the term overwhelmingly means internal developer platforms (Kubernetes, Backstage, golden paths) elsewhere in the industry; this skill covers only the external/public-API-platform track. States the key finding that splits this track from DevRel's - platform compensation rides the general engineering/PM ladder, not a separate undersurveyed one. Covers GitLab's real Partner Engineer ladder, the API-design-vs-system-design interview split, and RFC/design-doc portfolio signals. Use when the user asks how to break into platform/API product work, prep for a platform or API-PM interview, or evaluate an offer. Do NOT use for hiring (samber/developer-platform-skills@developer-platform-hiring) or advocate/community/educator roles (samber/developer-relations-skills@devrel-career).
Runs a devtool vendor's, DevRel team's or open-source maintainer's presence on DEV Community (dev.to) - organization account, cross-posting with canonical_url and RSS import, tag rules and tag moderators, AI-disclosure tiers, promotion and backlink limits, feed ranking, Top 7 and Billboards. Use whenever the user mentions dev.to or DEV Community, cross-posting a blog there, a removed tag, a flagged or low-reach dev.to post, or a dev.to launch - even if they only say 'our dev.to posts get three reactions'. Not for administering a Forem instance. Do NOT use for drafting the article - use samber/developer-relations-skills@engineering-blog-post; for Hacker News, samber/developer-relations-skills@hackernews-playbook; for Substack, samber/developer-relations-skills@substack-playbook.
Use when you want to discover content series across your existing work — finds clusters by theme rather than topic, identifies repeated points from different angles, flags incomplete arcs, and suggests series framing that makes relationships explicit.
Builds a prioritized keyword list for technical search queries (error strings, "how to X in Y" tasks, integration intents, comparisons, migrations) mined from docs search logs, support tickets, issue trackers and first-party query data rather than keyword-tool volume. Use whenever the user asks what developers actually search for, wants keywords for a developer tool, API, SDK or docs site, an error-message keyword list, demand sizing for a technical topic, or which docs pages to create from search demand - even if they never say "keyword". Does not write the pages. Do NOT use for on-page or docs-site SEO - use samber/developer-relations-skills@docs-seo.
Cuts a developer audience into a few named, sized and ranked segments - the two dimensions worth cutting on, a size range with a confidence tier, the user/champion/approver/buyer split inside each, a weighted score, one primary and one secondary segment, and a written anti-segment. Use whenever someone asks who their developers actually are, which developer audience to serve first, how big a language ecosystem or persona is, whether to target hobbyists or enterprise platform teams, who signs when the developer is not the buyer, or why content reaches everyone and converts nobody - even if they only say "who is this for". Not the journey map - use samber/developer-relations-skills@developer-journey-map.
Decides whether and how to invest in structured developer education, such as learning paths, a developer academy, hands-on labs, badges or a full certification program - instead of more ad-hoc content, then designs its operating model, staffing, refresh cadence, measurement and kill rules. Use whenever someone mentions a developer academy, certification, a developer curriculum, training for developers, learning paths, skill badges or credentials, "should we certify our users", partner or SI enablement training, or scaling developer onboarding beyond docs - even if they only say "we need more training content". Covers B2B, partner and bottom-up motions. Never writes the courses themselves. Use samber/developer-relations-skills@developer-tutorial for a lesson.
When the user wants to establish or update their developer audience context. Also use when starting any other developer marketing skill to ensure foundational context is loaded. Trigger phrases include "developer persona," "target developers," "who are our developers," "developer profile," "ICP," or "ideal customer profile."
Writes or audits a teaching tutorial for a developer product - one new concept per step, checkpoints the learner can verify and resume from, guidance that fades, troubleshooting hooks, and a demonstrable skill at the end. Use whenever the user mentions a tutorial, a build-along or hands-on guide, a "learn X by building Y" article, a workshop or lab handout, a developer course lesson, or says nobody finishes their tutorial - even if they just say "write a guide that teaches this". Do NOT use for a zero-to-first-success quickstart (samber/developer-relations-skills@developer-quickstart-guide) or a video script (samber/developer-relations-skills@technical-video-script).