keyword-discovery
Skill1.1k starsChanged 26 days agoMITView on GitHub
Finds long-tail search expressions from a seed, competitor sites, search suggestions and customer language. Use for keyword expansion and demand discovery.
2 other projects use a version of this.
Trending
More talk lately.thin dataabout the whole repository
Most recently taken up by
- About-Intelligence/awesome-marketing-skillstheir own version, first seen Nov 8, 2026
- DarynaRodriguez/seo-skillstheir own version, first seen Aug 27, 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.
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- About-Intelligence/awesome-marketing-skills★ 14same name
- DarynaRodriguez/seo-skills★ 1same name
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-mappingSkill
- keyword-opportunitySkill
- keyword-researchSkill
- 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
Files
Keyword Discovery
Start with the seed, product boundaries, target market and language. Follow the user's highest-value use case first. Explore alternative wording, action, input, desired output, audience, use case, workflow scale and quality or failure conditions. Combine dimensions into plausible tasks and retain the original wording of observed queries. For another market, find local usage independently, including colloquial terms.
Build the base expression family before expanding features or scenarios. Separate the action, object and optional qualifiers. Probe natural verb, process noun, tool noun, word order and number variants with and without qualifiers. Check tool-family heads, cross-root task paraphrases and audience-specific language when relevant. Preserve the raw strings; removing a modifier can broaden intent. For generate song with ai, probe generate song, generate a song, song generation, AI song generation, song generator, AI song generator, song maker and make a song with AI. Query distinct root forms separately to discover branches that the original string misses. Keep unattested forms labeled as hypotheses.
For a narrow seed, identify the constraint that narrows it (such as a symptom, material, audience or use case). Offer the nearest useful broader query by relaxing that constraint while preserving the task. Show the parent followed by the input seed and explain the difference. Label a parent as observed wording or an inferred topic. Keep the original seed as the research scope. Use the parent to find relevant siblings when helpful. Multiple plausible parents can reflect different dimensions. A parent-child relationship alone does not justify targeting both on one page.
Inspect the target-market search results for competitors serving the task. Open relevant navigation, sitemap URLs, feature pages, industry pages and help topics. Check title, H1, actual inputs and outputs, and the referring page. A link from an ecommerce solution to a white-background tool suggests a product-photo hypothesis. Record the page URL and label the derived query as inferred. A competitor page supports coverage; claims about its traffic or rankings require separate evidence. Reuse competitor-research findings if available.
Probe Google Autocomplete with the seed and promising partial phrases. Capture People Also Ask questions verbatim and People Also Search For or Related searches under the label actually displayed. Record the triggering query, market, language, date and source for each observation. A featured snippet gives clues about answer format. Use relevant GSC queries, ad search terms, site search, support language or user-provided exports to extend coverage. Re-query valuable new branches separately. If ordinary search access times out or cannot expose these surfaces, use an available authorized cloud browser or personal agent to run the queries in the target locale. Supply seeds, locale and required surfaces; request verbatim entries, triggering query, displayed module label, date and source URL or screenshot. Distinguish a module absent on an inspected page from a page that could not be inspected. If no such session is available, return the pending collection request and continue with available evidence. Keep synthesized phrases separate from observed suggestions, even when they sound natural.
For background remover, distinguish removing a white background from adding white to a product photo. Explore image versus video, ecommerce versus passport, and preserving fine edges versus repairing an existing cutout. Use these as probes until observed.
Hand keyword-clustering a deduplicated candidate pool retaining raw wording, source or URL, observed/inferred status and branch. Surface unsupported product needs separately. Stop at saturation or the agreed boundary.
For creative generation, explore the attributes of the output as well as the inputs. Probe genre or style, occasion, audience and intended use. For a pattern such as [genre] song generator, sample contrasting values and check demand evidence individually. Keep unverified combinations as probes.
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.

