Devmarketing Skills

Design SDKs that developers love to use—APIs that feel native, error messages that guide, and experiences that reduce friction. This skill covers creating SDKs that drive adoption through exceptional developer experience rather than aggressive marketing. Trigger phrases: "SDK design",...

When the user wants to build a developer following on Twitter/X, write technical threads, or understand what works for dev audiences on X. Trigger phrases include "Twitter," "X," "developer Twitter," "tech Twitter," "technical threads," "building dev following," or "Twitter for developers."

Paid advertising strategies for developer audiences on Carbon Ads, BuySellAds, Reddit, and developer newsletters. Covers which platforms work for developers, creating ad creative that doesn't feel like ads, targeting by technology stack, and measuring ad spend ROI. Use when asked about: - Developer advertising - Paid ads for developer tools - Carbon Ads strategy - Reddit advertising for developers - Newsletter sponsorships - Developer ad creative - Targeting developers with ads

SEO strategy for technical queries and developer audiences. Covers keyword research for "how to X in language" queries, error message SEO, Stack Overflow-style content, technical long-tail keywords, and competing with official documentation sites.

Reduce time-to-first-API-call (TTFAC) by optimizing every step of the developer onboarding journey. This skill covers authentication simplification, sandbox environments, interactive documentation, and identifying and eliminating common failure points.

When the user wants to create technical content for developers including blog posts, tutorials, and documentation.

When the user wants to create developer YouTube content, technical screencasts, or video tutorials. Trigger phrases include "YouTube," "developer video," "screencast," "video tutorial," "live coding," "YouTube for developers," "tech YouTube," or "YouTube thumbnails."

When the user wants to publish on Dev.to, Hashnode, or other developer blogging platforms. Trigger phrases include "Dev.to," "Hashnode," "developer blog," "cross-posting," "technical blogging," "canonical URL," or "developer content platform."

When the user wants to understand, reduce, or recover from developer churn. Trigger phrases include "why developers leave," "churn rate," "win-back campaign," "at-risk users," "developer retention," "preventing churn," or "competitor switching."

Create release notes and product updates that developers actually read and care about. This skill covers changelog formatting, versioning communication, breaking change announcements, deprecation notices, and building anticipation for new features.

Design and build interactive playgrounds that let developers experience your product without commitment. This skill covers playground architecture, pre-populated examples, embedding strategies, gating decisions, and converting playground users to signups.

Transform documentation into a powerful marketing channel that attracts, converts, and retains developers.

When the user wants to promote on Reddit, engage developer subreddits, or understand Reddit self-promotion rules. Trigger phrases include "Reddit," "subreddit," "r/programming," "r/webdev," "self-promotion," "Reddit marketing," or "getting upvotes on Reddit."

When the user wants to build, grow, or improve a developer community on Discord, Slack, or forums.

When the user wants to do developer advocacy activities including conference talks, live coding, podcasts, and building in public.

Lead generation strategies for developer audiences using free tools, code generators, and ungated resources. Covers tool ideas that attract developers, build vs buy decisions for lead gen tools, ungated vs gated content tradeoffs, conversion without forms, and measuring attribution. Use when asked about: - Developer lead generation - Free tools for marketing - Ungated content strategy - Developer conversion tactics - Code generator marketing - Attribution for developer tools

Design free tiers that convert to paid without creating resentment or abuse. Trigger phrases: free tier design, freemium model, free trial strategy, free tier limits, developer free plan, open source commercial, feature gating, upgrade triggers, free tier conversion

When the user wants to reach developers on LinkedIn, create technical content for B2B audiences, or understand when LinkedIn beats Twitter. Trigger phrases include "LinkedIn," "LinkedIn for developers," "B2B developer marketing," "engineering managers," "reaching CTOs," or "technical LinkedIn content."

Systematic competitor analysis for developer tools. Track features, pricing, positioning, content strategy, and community sentiment for direct and indirect competitors.

Monitor what developers say about your brand, competitors, and the problems they're solving. Track mentions and conversations across GitHub, Hacker News, Reddit, Stack Overflow, Twitter, and Discord.

When the user wants to create step-by-step technical tutorials, quickstarts, or code walkthroughs. Trigger phrases include "tutorial," "quickstart," "getting started guide," "walkthrough," "step by step," "how to guide," "hands-on guide," or "code tutorial."

Design pricing models that developers understand, accept, and can predict. Trigger phrases: usage-based pricing, API pricing, metered billing, developer pricing, pricing page, cost calculator, pay as you go, pricing transparency, competitive pricing, developer billing

When the user wants to create, write, or improve a newsletter for developer audiences. Trigger phrases include "newsletter," "email marketing," "developer email," "weekly digest," "dev newsletter," "email subscribers," "newsletter growth," or "email list."

Get developers to "Hello World" fast with optimized quickstarts, tutorials, and sample apps.

When the user wants to promote on Hacker News, launch on HN, or understand what works on HN. Trigger phrases include "Hacker News," "HN post," "Show HN," "HN strategy," "getting upvotes on HN," "HN launch," or "why did my HN post die."

Design frictionless signup experiences for developers including GitHub OAuth, API key generation, and onboarding personalization.

When the user wants to market an open source project authentically. Trigger phrases include "open source marketing," "OSS marketing," "GitHub marketing," "promote my library," "grow stars," "launch open source," "open source growth," or "contributor marketing."

When the user wants to identify and nurture developer advocates, build champion programs, or turn active users into contributors and evangelists.

When the user wants to create email sequences for developers including onboarding, product updates, re-engagement, or changelog communications. Trigger phrases include "developer emails," "onboarding sequence," "email drip," "developer newsletter," "changelog email," "re-engagement campaign," or "email cadence."

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.

Getting listed on developer tool directories, awesome lists, and curated resources. Covers which directories matter for developer tools, submission best practices, contributing to awesome-lists on GitHub, maintaining listings over time, and tracking referral traffic. Use when asked about: - Developer tool directories - Awesome list submissions - Getting listed on dev resources - Directory submission strategy - Curated list contributions - Tool discovery platforms