keyword-research
Research and cluster keywords. Use when: mapping search intent, finding content gaps, or long-tail discovery.
What this skill does
# /digital-marketing-pro:keyword-research
## Purpose
Standalone keyword research and clustering tool. Produces a prioritized keyword list with estimated search volume, keyword difficulty, search intent classification, and content recommendations mapped to each cluster.
## Input Required
The user must provide (or will be prompted for):
- **Seed keywords or topic**: Starting keywords, a topic area, or a URL to extract keyword themes from
- **Target audience**: Who the content is intended to reach (demographics, expertise level, pain points)
- **Industry**: The vertical or niche to contextualize volume and difficulty estimates
- **Competitor domains**: Optional -- 1-3 competitor domains to run content gap analysis against
- **Target market/language**: Geographic and language targeting for volume estimates
- **Content goals**: Traffic, leads, thought leadership, product sales, or brand awareness
- **Existing content inventory**: Optional -- URLs or topics already published to avoid duplication
## Process
1. **Load brand context**: Read `~/.claude-marketing/brands/_active-brand.json` for the active slug, then load `~/.claude-marketing/brands/{slug}/profile.json`. Apply voice, compliance, industry context. Check `guidelines/_manifest.json` for restrictions, messaging, channel styles, voice-and-tone rules, and templates. If a template matching this command exists in `~/.claude-marketing/brands/{slug}/templates/`, apply its format. If no brand exists, prompt for `/digital-marketing-pro:brand-setup` or proceed with defaults.
2. **Check campaign history**: Run `python campaign-tracker.py --brand {slug} --action list-campaigns` to identify previous keyword research and content campaigns to build upon rather than duplicate.
3. **Load reference files**: Consult `skills/content-engine/` for content strategy context and `skills/context-engine/industry-profiles.md` for industry-specific keyword benchmarks and search behavior patterns.
4. **Run keyword clustering**: Execute `scripts/keyword-clusterer.py` with seed keywords to generate an expanded keyword list with volume estimates, difficulty scores, and trend signals.
5. **Classify search intent**: Categorize every keyword into intent buckets -- informational (how-to, what-is), navigational (brand, product names), commercial (best, reviews, comparison), and transactional (buy, pricing, demo, free trial).
6. **Map keywords to content types**: Assign each cluster a recommended content format -- blog post, landing page, pillar page, comparison page, FAQ, video, tool, or interactive content -- based on intent and SERP feature analysis.
7. **Identify content gaps vs competitors**: If competitor domains were provided, cross-reference their ranking keywords against the brand's current coverage to surface missed opportunities and underserved topics.
8. **Discover long-tail opportunities**: Expand each cluster with long-tail variants, question-based keywords (People Also Ask patterns), and related search modifiers that represent lower-difficulty entry points.
9. **Assess SERP feature opportunities**: For each primary keyword, identify which SERP features are present (featured snippets, People Also Ask, knowledge panels, image packs, video carousels) and note which are attainable.
10. **Identify seasonal and trending opportunities**: Flag keywords with notable seasonal patterns or rising search trends that present time-sensitive content opportunities requiring prioritized scheduling.
11. **Prioritize by impact and difficulty**: Score each keyword cluster on a composite priority metric weighing estimated volume, ranking difficulty, business relevance, conversion potential, and content gap opportunity.
12. **Generate keyword strategy document**: Compile the full analysis into a structured deliverable with clear next-step recommendations for content creation sequencing.
## Output
A structured keyword strategy document containing:
- Keyword clusters organized by topic theme, each with individual keywords listed
- Estimated monthly search volume and keyword difficulty per keyword
- Search intent classification (informational, navigational, commercial, transactional) per keyword
- SERP feature opportunities per cluster (featured snippets, PAA, video, image pack)
- Recommended content type and format for each cluster
- Priority score (high/medium/low) with rationale for sequencing
- Content gap analysis showing competitor-owned keywords the brand is missing
- Long-tail keyword opportunities with lower difficulty and high relevance
- Question-based keyword list for FAQ and People Also Ask targeting
- Recommended content creation roadmap based on priority ranking
- Quick-win keywords (low difficulty, decent volume, high relevance) flagged for immediate action
- Seasonal or trending keyword opportunities with timing recommendations
- Internal linking opportunities between keyword clusters and existing content
## Tips & caveats
- **Search volume from any provider is an estimate.** Ahrefs, Semrush, GSC, SE Ranking all disagree by 20-50% on the same keyword. Use ranges, not point estimates.
- **Keyword difficulty (KD) is a heuristic, not a measurement.** A KD of 60 means "competitive" — not "impossible". A small brand with niche authority can rank for KD-70 keywords against generalist KD-30 sites.
- **Long-tail isn't always lower-volume.** With AI search rewriting queries, the actual click-driving query may differ from the seed. Always check the *resulting* query a user typed via GSC, not the rank-tracker assumption.
- **Hand off to `/digital-marketing-pro:keyword-cluster`** once you have ≥ 20 raw keywords. Clustering before writing is what produces topical authority, not keyword lists.
- **Don't research the same keyword set quarterly.** Re-research only when business model, target market, or competitive landscape changes. Otherwise the deltas are noise.
- **Intent classification beats volume.** A "buy [product]" query at 200/mo is worth more than "what is [product]" at 5000/mo for most commercial brands.
## Agents Used
- **seo-specialist** -- Keyword research, volume and difficulty estimation, SERP analysis, content gap identification, and priority scoring
- **content-creator** -- Content type mapping, content angle recommendations, and editorial planning for keyword-targeted pieces
Related in Writing & Docs
jax-development
IncludedUse this skill when the user is writing, debugging, profiling, refactoring, reviewing, benchmarking, parallelising, exporting, or explaining JAX code, or when they mention JAX, jax.numpy, jit, grad, value_and_grad, vmap, scan, lax, random keys, pytrees, jax.Array, sharding, Mesh, PartitionSpec, NamedSharding, pmap, shard_map, Pallas, XLA, StableHLO, checkify, profiler, or the JAX repo. It helps turn NumPy or PyTorch-style code into pure functional JAX, fix tracer/control-flow/shape/PRNG bugs, remove recompiles and host-device syncs, choose transforms and sharding strategies, inspect jaxpr/lowering/IR, and benchmark compiled code correctly.
nature-article-writer
IncludedDrafts, rewrites, diagnostically critiques, and style-calibrates primary research manuscripts for Nature and Nature Portfolio journals. Use when the user wants a Nature-style title, summary paragraph or abstract, introduction, results, discussion, methods, figure legends, presubmission enquiry, cover letter, reviewer response, or when a scientific draft sounds generic, jargon-heavy, structurally weak, or AI-ish and needs precise, broad-reader-friendly prose without inventing data, analyses, or references. Best for primary research articles and letters rather than reviews or press releases unless explicitly adapting one.
deckrd
IncludedDocument-driven framework that derives requirements, specifications, implementation plans, and executable tasks from goals through structured AI dialogue. Use when user says "write requirements", "create spec", "plan implementation", "derive tasks", "structure this feature", "break down into tasks", or "document this module". Also use for reverse engineering existing code into docs (/deckrd rev). Do NOT use for direct code writing — use /deckrd-coder after tasks are generated. Do NOT use when the user only wants to run or fix existing code without planning.
clinical-decision-support
IncludedGenerate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.
handling-sf-data
IncludedSalesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use querying-soql), Apex test execution (use running-apex-tests), or metadata deployment (use deploying-metadata).
accelint-ac-to-playwright
IncludedConvert and validate acceptance criteria for Playwright test automation. Use when user asks to (1) review/evaluate/check if AC are ready for automation, (2) assess if AC can be converted as-is, (3) validate AC quality for Playwright, (4) turn AC into tests, (5) generate tests from acceptance criteria, (6) convert .md bullets or .feature Gherkin files to Playwright specs, (7) create test automation from requirements. Handles both bullet-style markdown and Gherkin syntax with JSON test plan generation and validation.