keyword-research
Skill873 starsChanged 9 months agoMITView on GitHub
Research keywords via the connected data source: intent, gaps. Grouping → keyword-cluster. \"what keywords should we target\"
We split this skill into the rules it gives an agent
3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 44 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 30
Check campaign history: Run python "${CLAUDE_PLUGIN_ROOT}/scripts/campaign-tracker.py" --brand {slug} --action list-campaigns to identify …
- Distinctive: line 35
Identify content gaps vs competitors: If competitor domains were provided, cross-reference their ranking keywords against the brand's …
- Distinctive: line 48
Search intent classification (informational, navigational, commercial, transactional) per keyword
“Common” is measured: kept by at least 6 in 10 of the 44 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
/digital-marketing-pro:keyword-research
Script location. If your host does not set
${CLAUDE_PLUGIN_ROOT}, the scripts are in this plugin'sscripts/folder, next toskills/. Run them with Python 3.10 or newer:python, orpython3wherepythonis not found (macOS, many Linux systems).
Purpose
Standalone keyword research tool — expansion, search-intent classification, and competitor gap analysis. Produces a prioritized, intent-classified keyword list with content recommendations. Volume and keyword-difficulty figures come from the brand's connected keyword MCP (Ahrefs / Semrush / SE Ranking / GSC) — this skill surfaces and interprets them, it does not fabricate them. Clustering into a pillar+spokes plan is delegated to /digital-marketing-pro:keyword-cluster (the keyword_cluster.py engine); this skill produces the seeds that skill consumes.
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
- Load brand context: Read
~/.claude-marketing/brands/_active-brand.jsonfor the active slug, then load~/.claude-marketing/brands/{slug}/profile.json. Apply voice, compliance, industry context. Checkguidelines/_manifest.jsonfor 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-setupor proceed with defaults. - Check campaign history: Run
python "${CLAUDE_PLUGIN_ROOT}/scripts/campaign-tracker.py" --brand {slug} --action list-campaignsto identify previous keyword research and content campaigns to build upon rather than duplicate. - Load reference files: Consult
skills/content-engine/for content strategy context andskills/context-engine/industry-profiles.mdfor industry-specific keyword benchmarks and search behavior patterns. - Expand the seed set: Use the brand's connected keyword MCP (Ahrefs
getRelatedKeywords, Semrush, SE Ranking, or GSC query mining) to expand seeds into a candidate list, pulling provider volume and keyword-difficulty figures where available. Record the provider and pull date — volume/KD are provider estimates, not measurements, and providers disagree by 20-50%. Do not claim volume/KD/trend numbers the connected tools didn't return. - 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).
- 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.
- 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.
- 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.
- 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.
- Identify seasonal and trending opportunities: Flag keywords with notable seasonal patterns or rising search trends that present time-sensitive content opportunities requiring prioritized scheduling.
- 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.
- 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-clusteronce 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
Other versions48 projects use a version of this.
Word for word · 0
None found.
Edited · 1
Wrote their own version · 47
- every-app/open-seo★ 24ksame name
- Ryze-AI-Adgent/open-seo-mcp-skills★ 7.1ksame name
- nowork-studio/notfair-plugin★ 4.1ksame name
- nowork-studio/toprank★ 4ksame name
- appeeky/aso-skills★ 2.2ksame name
- Eronred/aso-skills★ 2.2ksame name
- Jwuthri/Tracely-ai★ 1.5ksame name
- jwuthri-cloud/Tracely-ai★ 1.2ksame name
- VladSez/easy-invoice-pdf★ 1.1ksame name
- liangdabiao/amazon-sorftime-research-MCP-skill★ 971same name
37 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
Used alongsideProjects with it also use link-prospecting, seo-project-setup and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
JwuthriSkilllink-prospecting
Find link prospects, discover contact paths, and draft outreach from SERPs and backlink signals.
Also in 10 projects that use this
JwuthriSkillseo-project-setup
Set up a durable local SEO workspace with project context, notes, goals, positioning, preferences, MCP checks, and Search Console data intake.
Also in 10 projects that use this
appeekySkillapp-marketing-context
When the user wants to create or update their app marketing context document. Also use when the user mentions "app context", "marketing brief", "app positioning", or when starting any ASO or app marketing project. This is the foundation skill — all other skills check for this context first.
Also in 5 projects that use this
appeekySkillmetadata-optimization
When the user wants to optimize App Store metadata — title, subtitle, keyword field, or description. Also use when the user mentions "optimize my title", "ASO metadata", "keyword field", "character limits", "app description", or "write my subtitle". For keyword discovery, see keyword-research. For full ASO audits, see aso-audit.
Also in 5 projects that use this
OpenClaudiaSkillbacklink-audit
Audit a domain's backlink profile using the SemRush API. Use when the user says "audit backlinks", "check my backlinks", "backlink analysis", "link profile", "toxic links", "disavow", "link building opportunities", "referring domains", "anchor text", or asks about a site's link authority.
Also in 4 projects that use this
liangdabiaoSkillreview-analysis
对亚马逊商品评论进行深度分析,自动识别产品痛点、分析退货原因,生成改进建议和客服回复模板。Invoke when user uses /review-analysis command with a product ASIN.
Also in 4 projects that use this
- +4 more from Jwuthri
- +1 more from appeeky
In this repository164 other files it gives its agents.
- AGENTS.mdAGENTS.md
- ab-test-planSkill
- ad-creativeSkill
- add-integrationSkill
- aeo-auditSkill
- aeo-geoSkill
- agency-dashboardSkill
- agent-readiness-auditSkill
- analytics-insightsSkill
- anomaly-scanSkill
- attribution-modelSkill
- attribution-reportSkill
- audience-intelligenceSkill
- audience-profileSkill
- autopilot-statusSkill
- backlink-gapSkill
- brand-setupSkill
- budget-optimizerSkill
- budget-trackerSkill
- c2pa-metadataSkill
- campaign-auditSkill
- campaign-orchestratorSkill
- campaign-planSkill
- campaign-statusSkill
- case-study-planSkill
- checkSkill
- churn-riskSkill
- client-onboardingSkill
- client-proposalSkill
- client-reportSkill
- client-validation-documentSkill
- cohort-analysisSkill
- competitor-alertsSkill
- competitor-analysisSkill
- competitor-monitorSkill
- competitor-pagesSkill
- connectSkill
- content-briefSkill
- content-calendarSkill
- content-decay-scanSkill
- content-engineSkill
- content-repurposeSkill
- context-engineSkill
- continuous-improvement-loopSkill
- counter-narrativeSkill
- cowork-setupSkill
- creative-healthSkill
- creative-testing-frameworkSkill
- credential-switchSkill
- crisis-responseSkill
- crm-syncSkill
- croSkill
- dark-funnelSkill
- data-exportSkill
- data-importSkill
- digital-prSkill
- email-sequenceSkill
- emerging-channelsSkill
- engagement-workflowSkill
- entity-auditSkill
- The first 60 shown.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

