keyword-research
Skill1.1k starsChanged 27 days agoMITView on GitHub
Coordinates keyword research from a seed or existing keyword data through discovery, intent clustering, opportunity assessment and page mapping.
59 other projects use a version of this.
Trending
More talk lately.thin dataabout the whole repository
Most recently taken up by
- gaznil/seo-skills-by-gazniltheir own version, first seen Nov 16, 2026
- gaznilmuzammil12-prog/seo-skills-by-gazniltheir own version, first seen Nov 16, 2026
- teemukarjaluoto/seo-sauna-mcptheir own version, first seen Nov 16, 2026
- harborrank/harborrank-skillstheir own version, first seen Nov 16, 2026
- winsley-jeune/harborrank-skillstheir own version, first seen Nov 15, 2026
- asospy/asospy-agent-skillstheir own version, first seen Nov 15, 2026
Who's talking about kostja94/marketing-skills
- akhmadilham/pinax-registry“[Skill Proposal]: marketing-skills”GitHub · Nov 2, 2026
- ProSkillsMD/proskills“[Candidate] kostja94/marketing-skills - large collection (172 SKILL.md files)”GitHub · Oct 17, 2026
- sudosubin/agents.nix“agent-skills.github.kostja94.marketing-skills: init at 1.0.0”GitHub · Oct 3, 2026
- alexanderkinging/Skill-Checker“False positives: Marketing terminology flagged as promotional content (CONT-005)”GitHub · Mar 9, 2026
The biggest 4 of 4 mentions linking to the repository that our crawl found. Each line is their own headline.
Used with
Projects with it also use link-prospecting, seo-project-setup and 7 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 11 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 11 projects that use this
liangdabiaoSkillreview-analysis
对亚马逊商品评论进行深度分析,自动识别产品痛点、分析退货原因,生成改进建议和客服回复模板。Invoke when user uses /review-analysis command with a product ASIN.
Also in 5 projects that use this
opencueSkillserp-analysis
Use when the user asks to "analyze SERPs"; reviews ranking factors, features, intent, AI Overviews, and snippets. SERP分析/搜索结果
Also in 6 projects that use this
- +5 more from Jwuthri
Other versions59 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 59
- every-app/open-seo★ 28ksame name
- Ryze-AI-Adgent/open-seo-mcp-skills★ 8.4ksame name
- nowork-studio/toprank★ 4.2ksame name
- nowork-studio/notfair-plugin★ 4.2ksame name
- Jwuthri/Tracely-ai★ 1.3ksame name
- liangdabiao/amazon-sorftime-research-MCP-skill★ 1.1ksame name
- VladSez/easy-invoice-pdf★ 1.1ksame name
- jwuthri-cloud/Tracely-ai★ 979same name
- indranilbanerjee/digital-marketing-pro★ 934same name
- OpenClaudia/openclaudia-skills★ 731same name
49 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.
In this repository25 other files it gives its agents.
- analytics-trackingSkill
- competitor-researchSkill
- article-contentSkill
- copywritingSkill
- podcast-marketingSkill
- translationSkill
- video-marketingSkill
- visual-contentSkill
- keyword-clusteringSkill
- keyword-discoverySkill
- keyword-mappingSkill
- keyword-opportunitySkill
- githubSkill
- grokipedia-recommendationsSkill
- linkedin-postsSkill
- medium-postsSkill
- pinterest-postsSkill
- reddit-postsSkill
- tiktok-captionsSkill
- twitter-x-postsSkill
- youtube-seoSkill
- entity-seoSkill
- local-seoSkill
- parasite-seoSkill
- programmatic-seoSkill
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 5 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 54 edited versions we read keep these.
5
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
Read the relevant sibling skills by name from the installed collection or local repository.
- Distinctive: line 23
Default to concise findings, decision-relevant clusters and outstanding checks in the conversation.
- Distinctive: line 31
Before delivery, account for each research node as observed, inferred, blocked or outside the requested scope.
- Distinctive: line 34
Run discovery across base word forms and task branches.
- Distinctive: line 36
Check product fit and evidence at cluster level.
“Common” is measured: kept by at least 6 in 10 of the 54 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
Keyword Research
For a market or category, start with category research to identify demand branches and seeds. For an existing website, start with its URL inventory and check indexability before diagnosing weak keyword performance. For a single seed, begin directly with the workflow below. Establish the decision, product capabilities, market, language and channel. Reuse relevant project context (including {project}.md when available), existing queries, URLs and CSV exports. State reasonable assumptions. A single seed is enough. When exploring several seeds one at a time, complete the current one before continuing.
Read the relevant sibling skills by name from the installed collection or local repository. Start at the earliest missing input and stop at the requested deliverable.
| Request | Skill | Handoff |
| Find demand or long-tail expressions | keyword-discovery | Candidate queries with provenance |
| Decide whether queries serve one page | keyword-clustering | Task, same-page variants, separate or uncertain branches |
| Choose what to pursue first | keyword-opportunity | Priorities, reasons and evidence gaps |
| Decide where validated demand belongs | keyword-mapping | Existing asset or proposed action per cluster |
By default, skip US search volume and keyword prioritization. Run keyword-opportunity for US rankings only when requested and suitable third-party data is available. Otherwise pass clusters directly to mapping. For a full study, pass these outputs forward in order. Return to discovery for a specific unresolved branch. If a sibling skill is unavailable, identify the missing step and use the handoff above to provide a bounded result. Keep source observations distinguishable from hypotheses throughout. For ads or product research, stop at the requested demand or opportunity decision. Hand content architecture and scheduling to content-strategy.
Default to concise findings, decision-relevant clusters and outstanding checks in the conversation. Produce full inventories or files on request. Stop when additional sources yield no material new tasks or variants, or at the agreed scope limit.
In a full report, show the base expression family before modifier clusters. Carry each material action, process and tool form into the page map or explain its pending placement. Report the concrete keyword strings, and mark observed versus inferred wording.
For a general keyword research request, deliver a decision report even if site inventory is missing. Lead with the main search task and proposed destination. Provide one row per candidate page cluster with a primary term, same-page variants, intent, landing page / blog / other type, proposed URL, decision and evidence or gap. Distinguish proposed paths from existing URLs. Separate confirmed observations from inferred expansions and show pending clusters. Respect a discovery-only request.
Completion check for a full study
Before delivery, account for each research node as observed, inferred, blocked or outside the requested scope. A blocked source is an evidence gap. Resume at the first unresolved decision when more evidence becomes available.
- Establish the seed, market, audience and product task. Identify useful parents while preserving the seed.
- Run discovery across base word forms and task branches. Record competitor URLs and the status of Autocomplete, People Also Ask and related searches separately. Preserve provenance when deduplicating.
- Hand discovery evidence to clustering. Resolve same-page variants, separate tasks and uncertain relationships against user goals, product capability and available search results. Send ambiguous high-impact branches back for targeted research.
- Check product fit and evidence at cluster level. Apply the optional prioritization rule above. Label unknown metrics and unsupported capabilities explicitly.
- Map each actionable cluster to a current or provisional destination, page type and reason. Distinguish an independent intent from a decision to create a new URL.
- Deliver findings, cluster decisions, open checks and any explicitly requested, data-backed priorities. If a missing step prevents a decision, label that part provisional. For a narrower request, stop at its agreed node.
For authenticated sources use the configured credential provider. In an environment configured for 1Password, retrieve credentials through that integration and keep secret values out of files, logs and reports.
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.

