Token导航 LogoToken导航

Agent Skill · 研究检索

keyword-research(关键词研究)

keyword-research 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

keyword-research 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为调用外部服务;许可证信息还不明确,第三方扫描有提醒项,按安装量在研究检索类的 73,675 个 Skill 里排第 52,043。

总安装 564周安装 24GitHub Stars 35下载 198核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:keyword-research(关键词研究)
来源仓库:https://github.com/superamped/ai-marketing-skills
仓库路径:skills/keyword-research
安装命令:
npx skills add https://github.com/superamped/ai-marketing-skills --skill keyword-research
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/superamped/ai-marketing-skills --skill keyword-research

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

keyword-research 用于信息查找、检索与筛选,支持关键词相关内容的匹配。适用于 Codex、Claude、Cursor、Gemini CLI 等平台的市场与 SEO 研究场景。通过 npx skills add 从 GitHub 安装,具体能力以项目文档为准。

使用前应确认其是否访问外部数据源或执行敏感操作。适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

来源仓库内路径:skills/keyword-research

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/superamped/ai-marketing-skills --skill keyword…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要调用外部服务,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

keyword-research 怎么安装?

在终端执行 npx skills add https://github.com/superamped/ai-marketing-skills --skill keyword-research。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

keyword-research 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

keyword-research 需要什么权限?

权限级别是调用外部服务。该 Skill 可能调用第三方服务、云服务或外部模型 API,使用前需要确认账号、额度、数据发送范围和服务条款。

keyword-research 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

keyword-research 用的人多吗?

公开数据是累计安装 564 次,近一周安装 24 次,下载 198 次,GitHub 35 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

keyword-research 安全吗?

第三方扫描有提醒项,说明存在需要人工确认的行为。安装前请打开源码看清它读了什么、联网到哪里。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方扫描存在提醒项或未通过项,需要人工逐条确认。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
find-skills

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
keyword-research

关键词研究 · 本页

56435调用外部服务未明确有提醒

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

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.

平台分布

Codex

34.03%
按下载量换算67

Claude

30.91%
按下载量换算61

Cursor

17.43%
按下载量换算35

Gemini CLI

9.31%
按下载量换算18

安全审计

Gen Agent Trust Hub

通过

Socket

可疑

Snyk

可疑

权限和风险

调用外部服务

该 Skill 可能调用第三方服务、云服务或外部模型 API,使用前需要确认账号、额度、数据发送范围和服务条款。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在提醒或未通过项,安装前请自行复核。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills