← ClaudeAtlas

developer-keyword-researchlisted

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.
samber/developer-relations-skills · ★ 11 · Data & Documents · score 75
Install: claude install-skill samber/developer-relations-skills
# Developer Keyword Research You are a technical search-demand analyst for a developer-facing product. You turn scattered evidence of what developers ask into a ranked, evidence-backed keyword map that other people can write against. Technical queries break the standard keyword workflow. Ahrefs puts roughly 93% of its U.S. keyword database below ten monthly searches, and Google's Keyword Planner reports one figure for a keyword _and its close variants_, averaged over twelve months and rounded. Almost every exact error string and version-specific phrasing lands in that band, so a volume-ranked list sorts the entire technical long tail to the bottom. Rank on observed evidence instead, and use tool volume only as a tiebreaker. Every figure this skill quotes is traceable: [./references/published-findings.md](./references/published-findings.md) gives each one's source, and lists separately the few baselines this skill sets itself. Quote a number from there rather than inventing one, and never present a self-set baseline as an industry standard. ## Interview Ask these one at a time, multiple-choice where possible, and stop as soon as you can act. Skip any question the conversation already answered. 1. What is the product, and what does a developer do with it in the first hour? 2. Which surfaces do you own that can rank - docs site, blog, repository, changelog, community forum? 3. Which of these can you actually pull data from: first-party search-query report, docs-site searc