devmarketing-skills

Create "[Competitor] alternative" and comparison pages for developer tools. Build honest, high-converting comparison content that ranks for competitive search terms. Trigger phrases: "alternatives page", "comparison page", "vs page", "[competitor] alternative", "competitor comparison", "competitive content", "comparison table", "migration guide", "switch from [competitor]", "compare to [competitor]", "alternative to"

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. Trigger phrases: "API onboarding", "time to first API call", "TTFAC", "developer onboarding", "first API call", "auth simplification", "sandbox environment", "interactive docs", "try it now", "API playground", "developer activation", "onboarding friction"

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. Trigger phrases: "changelog", "release notes", "product updates", "version communication", "breaking changes", "deprecation notice", "what's new", "release communication", "developer updates", "API versioning", "migration announcement"

When the user wants to build, grow, or improve a developer community on Discord, Slack, or forums. Trigger phrases include "developer community," "Discord server," "Slack community," "community strategy," "community engagement," "community moderation," "community growth," or "community management."

Systematic competitor analysis for developer tools. Track features, pricing, positioning, content strategy, and community sentiment for direct and indirect competitors. Trigger phrases: "competitor analysis", "track competitors", "competitive intelligence", "competitor research", "what are competitors doing", "competitive landscape", "competitor features", "competitor pricing", "battlecard", "competitive battlecard", "compete against", "vs [competitor]"

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

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

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

When the user wants to do developer advocacy activities including conference talks, live coding, podcasts, and building in public. Trigger phrases include "developer advocacy," "devrel," "conference talk," "CFP," "call for papers," "live coding," "podcast," "building in public," "technical speaking," or "dev evangelism."

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

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

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

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

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. Trigger phrases: "developer listening", "monitor developer conversations", "track developer mentions", "what are developers saying", "developer sentiment", "brand monitoring", "social listening for devtools", "find developer conversations", "monitor GitHub mentions", "track Hacker News mentions"

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. Trigger phrases: developer onboarding, time to first value, quickstart guide, hello world tutorial, developer activation, onboarding checklist, sample apps, getting started experience, reduce time to value

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. Trigger phrases: "developer sandbox", "API playground", "interactive playground", "try it now", "demo environment", "code playground", "live examples", "embedded playground", "developer trial", "sandbox conversion", "playground design"

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. Use when asked about: - SEO for developer tools - Ranking for technical queries - Error message content strategy - Competing with documentation in search - Technical keyword research - Developer content SEO

Design frictionless signup experiences for developers including GitHub OAuth, API key generation, and onboarding personalization. Trigger phrases: developer signup, dev registration, OAuth flow, API key onboarding, reduce signup friction, developer authentication, signup conversion, registration UX

When the user wants to create technical content for developers including blog posts, tutorials, and documentation. Trigger phrases include "write a blog post," "technical article," "developer content," "tutorial," "devrel content," "dev blog," "technical writing," or "content for developers."

Transform documentation into a powerful marketing channel that attracts, converts, and retains developers. This skill covers creating documentation that ranks in search, converts visitors into users, and accelerates adoption through exceptional information architecture and developer-focused writing. Trigger phrases: "documentation strategy", "docs that convert", "quickstart optimization", "API reference best practices", "developer documentation", "docs SEO", "information architecture for docs", "technical writing for marketing", "docs-led growth"

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 optimize their GitHub profile, README, or project discoverability. Trigger phrases include "GitHub README," "README optimization," "GitHub profile," "GitHub stars," "GitHub discoverability," "awesome lists," or "GitHub marketing."

Getting ROI from hackathon sponsorships for developer tools. Covers evaluating which hackathons to sponsor, booth presence strategies, prizes that actually work, judge involvement, follow-up strategies, and measuring sponsorship ROI. Use when asked about: - Hackathon sponsorship strategy - Developer event sponsorship ROI - Hackathon prizes - Booth presence at hackathons - Post-hackathon follow-up - Hackathon sponsorship evaluation

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

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

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. Trigger phrases include "power users," "developer advocates," "ambassador program," "champion program," "community contributors," "referral program," or "user-generated content."

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

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", "developer experience", "API design", "SDK DX", "error messages", "type safety", "IDE integration", "SDK versioning", "migration guides", "client library design", "making SDKs feel native", "SDK best practices"

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

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