Keyword Research logo

Keyword Research

Community
superamped
keyword-research

Use this skill to expand seed topics with Keywords Everywhere, retrieve live metrics, cluster terms by search intent, and score priorities. Trigger it when building a keyword universe, planning SEO content, validating demand, or finding search gaps.

Overview

Publishersuperamped
Repositoryai-marketing-skills
Skill namekeyword-research
Stars
73
Forks
6
Bundled files
Instructions only
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by superamped on GitHub. Read the source before you install it.

Installation

Install the Keyword Research AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/superamped/ai-marketing-skills/tree/main/skills/research/keyword-research
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/superamped/ai-marketing-skills.git /tmp/ai-marketing-skills
mkdir -p .claude/skills
cp -r /tmp/ai-marketing-skills/skills/research/keyword-research .claude/skills/keyword-research
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Keyword Research in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Keyword Research on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Keyword Research is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Keyword Research

Usage

Use when planning content around a topic before writing, building a keyword map for a new content area, finding question-based keywords for GEO optimization, or identifying gaps where competitors rank and you don't.

Process

Step 1: Gather Inputs

Ask the user for:

  1. Seed topic or keyword — e.g., "AI search optimization", "B2B SaaS customer acquisition"
  2. Country code (optional) — for localised volumes (default: "us")
  3. Competitor domain(s) (optional) — to identify keyword gaps
  4. Number of clusters (optional) — default: let the data dictate

Step 2: Validate & Prepare

  • Confirm the Keywords Everywhere MCP server is connected. If not configured, tell the user — this skill requires it.
  • Check credit balance with Get Credit Balance before starting — warn the user if credits are low.

Credit estimate formula: (related_count + pasf_count) * 2 credits for expansion + total_unique_keywords * 1 credit for metrics. A typical run with 100 related + 100 PASF keywords costs ~500 credits. Warn if balance would drop below 1,000 after the run.

Step 3: Expand the Seed

Run two Keywords Everywhere tools against the seed keyword:

  1. Get Related Keywords (num: 100) — returns a list of keyword strings (no metrics yet)
  2. Get "People Also Search For" Keywords (num: 100) — returns a list of keyword strings (no metrics yet)

If PASF returns empty results: This is common for newer or niche terms. Proceed with the related keywords only. If the combined list is thin (< 30 keywords), consider running a second expansion on a broader variant of the seed.

Combine the results into a single deduplicated keyword list.

If the seed returns fewer than 20 keywords total, it may be too narrow. Suggest broader alternatives to the user.

Step 3b: Pull Metrics

Run Get Keyword Data on the deduplicated keyword list to get volume, CPC, competition, and trend data for every keyword.

Batch in groups of 50 keywords per API call to avoid oversized responses. Run batches in parallel where possible.

Parameters: country: "us" (or from user input), currency: "usd", dataSource: "cli" (includes clickstream data for more accurate volumes).

Step 4: Competitor Gap Analysis (optional)

If competitor domain(s) were provided:

  1. Get Domain Keywords for each competitor — returns keywords they rank for
  2. Cross-reference with the expanded keyword list from Step 3
  3. Flag keywords where competitors rank but the user's domain doesn't — these are gaps
  4. Add any high-volume competitor keywords that didn't appear in the Step 3 expansion

If no competitors provided, skip this step.

Step 5: Cluster by Intent

Group the full keyword list into semantic clusters. Each cluster represents a potential piece of content.

Pre-clustering: Filter brand/navigational noise

Before clustering, separate out brand-specific and product-name keywords. These are navigational queries for specific tools, not topics you'd write content about. List them in an "Excluded: Brand/Navigational Keywords" section at the end — they're useful market intelligence but shouldn't inflate your topic clusters.

Clustering rules:

  • Group keywords that would be answered by the same piece of content
  • Name each cluster after its core topic (not the highest-volume keyword)
  • Assign an intent to each cluster:
    • Informational — "what is", "how to", "why does" — answered by blog posts, guides
    • Commercial — "best", "vs", "review", "pricing" — answered by comparison pages, landing pages
    • Navigational — brand-specific or product-specific queries — answered by product/feature pages
    • Transactional — "buy", "sign up", "get started" — answered by landing pages, pricing pages
  • A cluster should have 3–20 keywords. If larger, split into sub-clusters. If smaller, consider merging.
  • Keywords with very low volume (< 10/mo) can be grouped into clusters but shouldn't form their own cluster
  • Drop zero-volume keywords entirely

Within each cluster, identify:

  • The primary keyword — highest volume keyword that best represents the cluster's intent
  • Question keywords — any keywords phrased as questions (valuable for H2 headings and FAQ sections)
  • Long-tail keywords — lower volume, more specific phrases (valuable for weaving into content)

Step 6: Prioritize

Score each cluster for content priority:

SignalWhat to look at
Total volumeSum of all keyword volumes in the cluster
CompetitionAverage competition score (lower = easier to rank)
Gap opportunityAre competitors ranking here and you're not? (from Step 4)
Intent fitDoes this cluster match content you'd actually create?
Question densityClusters with more question keywords are better for GEO

Rank clusters by a blended priority — not just volume. A low-competition cluster with good question density and a clear gap often beats a high-volume, high-competition cluster.

Output Format

# Keyword Research: [Seed Topic]

**Seed:** [seed keyword]
**Date:** [current date]
**Total keywords found:** [X]
**Clusters:** [X]

---

## Cluster 1: [Cluster Name]

**Intent:** Informational / Commercial / Navigational / Transactional
**Primary keyword:** [keyword] ([volume]/mo)
**Total cluster volume:** [X]/mo
**Avg competition:** [X]
**Gap opportunity:** Yes / No
**Priority:** High / Medium / Low

| Keyword | Volume | CPC | Competition | Type |
|---------|--------|-----|-------------|------|
| [keyword] | [vol] | [cpc] | [comp] | Primary |
| [question keyword]? | [vol] | [cpc] | [comp] | Question |
| [long-tail keyword] | [vol] | [cpc] | [comp] | Long-tail |

---

## Cluster 2: [Cluster Name]
[Same format...]

---

## Summary

| Cluster | Intent | Primary Keyword | Volume | Competition | Priority |
|---------|--------|----------------|--------|-------------|----------|
| [name] | [intent] | [keyword] | [vol] | [comp] | High |
| [name] | [intent] | [keyword] | [vol] | [comp] | Medium |

## Recommended Next Steps

- [Which clusters to write first and why]
- [Suggested content type for each high-priority cluster]
- [Any gaps that need competitor research first]

Rules

  • Never invent keyword volumes or competition scores — all data must come from the Keywords Everywhere API.
  • Never cluster keywords you haven't actually retrieved — don't pad clusters with guesses.
  • Never present unclustered keyword dumps — always group and prioritize.
  • If the MCP server is not connected, stop and tell the user.
  • If credit balance is low (< 100 credits), warn before starting.
  • If the seed returns fewer than 20 keywords, suggest broadening.
  • If the seed returns 1000+ keywords, confirm they want the full expansion or suggest narrowing.
  • Country code matters — volumes vary significantly by market. Default to "us" if no country specified.
  • Run this skill periodically (quarterly) on core topics to catch new keywords and shifting volumes.

Frequently asked questions

What does the Keyword Research AI skill do?

Use this skill to expand seed topics with Keywords Everywhere, retrieve live metrics, cluster terms by search intent, and score priorities. Trigger it when building a keyword universe, planning SEO content, validating demand, or finding search gaps.

Why use Keyword Research on TypingMind?

Because you install it once and use it with any model. Keyword Research is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Keyword Research in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/superamped/ai-marketing-skills/tree/main/skills/research/keyword-research. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Keyword Research?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Keyword Research?

As many as you like. As long as a model supports skills, you can use Keyword Research with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Keyword Research AI skill free?

Yes. It is published on GitHub by superamped under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇