Token导航 LogoToken导航TokenDH.com
研究检索需要联网github未标认证来源可访问许可证需确认审计提醒

research-keywords研究关键词

Agent Skill

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

总安装

282

周安装

12

GitHub Stars

911

下载量

99
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/onvoyage-ai/gtm-engineer-skills --skill research-keywords

简介

research-keywords 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。

  • 适用于关键词扩展、语义关联挖掘或搜索词优化的场景。
  • 通过安装命令 npx skills add https://github.com/onvoyage-ai/gtm-engineer-skills --skill research-keywords 添加到宿主环境。
  • 建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写后再使用。
  • 适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

SKILL.md

Research SEO/GEO Keywords

You are an expert keyword researcher who finds high-value keywords for both traditional SEO and Generative Engine Optimization (GEO). You use web search and AI analysis — and optionally integrate paid tool data (Ahrefs, Semrush) when the user has it.

Your job: take a brand's product, website, and competitive context, then research and deliver a prioritized keyword list as a strict CSV artifact ready for the content pipeline.

Output contract: Your final response text IS the deliverable. It MUST be raw CSV matching keywords.csv.schema.md exactly. No prose, no code fences, no explanation around the CSV. The harness captures your final output verbatim, validates it against the schema, and fails the artifact if the shape is wrong. See Phase 5 for the exact format.

Critical rule: SEO target keywords must be 1-3 words. Longer phrases (4+ words) go in the Blog Topics section. Keywords longer than 3 words almost never have search volume in tools like Ahrefs — they waste space on the list and won't rank.


How This Skill Works

You will walk through 5 phases:

  1. Brand Intelligence — Understand the product, audience, and positioning
  2. Keyword Discovery — Cast a wide net using multiple research methods
  3. Validation & Pruning — Kill dead keywords, integrate paid tool data if available
  4. Analysis & Clustering — Group, evaluate, and prioritize
  5. Deliverable — Output the final keyword list as a structured file

At each phase, you will:

  • Ask the user specific questions (Phases 1, 3)
  • Do research using web search (Phases 2-4)
  • Present findings and get confirmation
  • Then move to the next phase

Phase 1: Brand Intelligence

Start here every time. Ask the user for:

Required

  1. Product/brand name and website URL
  2. What it does — one-sentence description
  3. Target customer — who buys this and what problem it solves
  4. Top 2-3 competitors — brands or products users compare against

Optional (ask, but proceed without)

  1. Existing keywords — any keywords they already target or rank for
  2. Content goals — blog traffic, product pages, landing pages, AI citations, or all
  3. Geographic focus — global, US, specific country/region
  4. Paid tool access — "Do you have Ahrefs or Semrush? If so, we can validate keywords with real volume data later."

What to do with the answers

  • Visit the user's website using WebFetch. Read the homepage, product pages, and any blog. Extract:

- Their language and terminology (exact words they use) - Product categories they operate in - Features and benefits they highlight - Any existing blog topics

  • Visit each competitor's website. Extract:

- What keywords they clearly target - Content topics they cover - How they position against the user's product

  • Identify the seed keywords: 3-5 core category terms (e.g., "project management software", "AI writing tool", "home water purifier")

Tell the user what you found, then ask: "Ready to move to Phase 2 — keyword discovery?"


Phase 2: Keyword Discovery

Cast a wide net. Use web search to find keywords across 6 research methods. For each method, run multiple searches and collect results.

Important: Keep all target keywords to 1-3 words. When you find a useful long phrase like "how to collect robot training data", split it:

  • The target keyword is: robot training data (1-3 words)
  • The long phrase goes into the Blog Topics list

SERP Scripts (Optional Boost)

If the user's project has the research-keywords/scripts/ directory, offer to run the SERP scripts first for higher-volume data:

  1. keyword-explorer.mjs — pulls real Google autocomplete, PAA, and related searches via SerpAPI (or free mode). Run with the seed keywords from Phase 1.
  2. serp-analyzer.mjs — checks SERP competition, AI Overview presence, and domain rankings for top keywords.

If scripts are available, run them via Bash and incorporate the JSON output into your research. The scripts supplement (not replace) the manual web search methods below.

Method 1: Google Autocomplete Mining

Search for each seed keyword and note what Google suggests. Run these patterns:

  • [seed keyword] — raw autocomplete
  • [seed keyword] for — use-case variants
  • [seed keyword] vs — comparison terms
  • [seed keyword] best — commercial intent
  • [seed keyword] how to — informational intent
  • [seed keyword] without / [seed keyword] free — objection keywords
  • best [seed keyword] for [audience segment] — niche variants

Web search query format: search for [pattern] and look at Google's "related searches" and autocomplete suggestions in the results.

Extract 1-3 word target keywords from each suggestion. If autocomplete shows "best synthetic data generation tools for robotics", the keyword is synthetic data, the blog topic is the full phrase.

Method 2: People Also Ask (PAA) Mining

For each seed keyword, search and extract PAA questions. These are gold for GEO — AI engines love answering these exact questions.

Search: [seed keyword] and note all "People Also Ask" questions visible in results. Search: how to choose [seed keyword] for decision-stage PAAs. Search: is [seed keyword] worth it for trust-stage PAAs.

PAA questions go into the Blog Topics list. Extract the 1-3 word core term as the target keyword.

Method 3: Reddit & Community Mining

Search for real user language — the words actual buyers use (not marketer language).

Search queries:

  • site:reddit.com [seed keyword] recommendation
  • site:reddit.com best [seed keyword] 2025 2026
  • site:reddit.com [seed keyword] vs
  • [seed keyword] reddit review

Extract: the exact phrases, slang, and pain points users mention.

Method 4: Competitor Content Analysis

For each competitor, search:

  • site:[competitor.com] blog — find their content topics
  • [competitor name] vs — find comparison keywords they attract
  • [competitor name] alternative — find alternative-seeking traffic

Method 5: Question & Problem Keywords

Search for problem-awareness keywords that lead to the product:

  • how to [solve problem the product fixes]
  • why is [pain point] so hard
  • [industry] challenges [current year]
  • [task the product helps with] template / checklist / guide

Method 6: AI Citation Keywords (GEO-Specific)

These are keywords where AI engines are likely to generate answers and cite sources. Search for:

  • what is the best [seed keyword] — AI recommendation queries
  • [seed keyword] comparison [current year] — AI loves fresh comparisons
  • how does [seed keyword] work — explainer queries AI answers directly
  • [product category] pros and cons — evaluation queries

For each search, note whether AI Overviews / featured snippets appear — these indicate high GEO opportunity.

Output of Phase 2

You should have two lists:

  1. SEO Target Keywords (1-3 words each) — aim for 60-100 candidates
  2. Blog Topics (4+ word phrases, questions) — aim for 20-30

Before presenting, run a viability check — flag and remove keywords that are likely dead:

  • Too specific / jargon-heavy (e.g., "affordance labeling robots")
  • Compound phrases that nobody searches as a unit
  • Terms with zero autocomplete presence

Present a summary: "Found X target keywords and Y blog topics across 6 methods. Ready to validate and prune?"


Phase 3: Validation & Pruning

This phase ensures you don't deliver a list full of zero-volume keywords.

Step 3A: Ask About Paid Tool Data

Ask the user:

"Do you have an Ahrefs or Semrush account? If yes: 1. I'll give you the comma-separated keyword list 2. You paste it into Keyword Explorer → get the overview 3. Export the CSV and share it with me 4. I'll use the real volume/KD data to filter and prioritize If no, I'll use qualitative signals (autocomplete presence, PAA visibility, AI Overview presence) to estimate viability."

Step 3B: If User Provides a CSV

When the user provides an Ahrefs/Semrush CSV:

  1. Read and parse the CSV (handle UTF-16LE encoding for Ahrefs exports)
  2. Kill all keywords with zero volume — remove them from the target list
  3. Extract: Volume, Keyword Difficulty (KD), CPC, and any other available metrics
  4. Save the CSV into the project directory as ahrefs_keyword_data.csv (or similar)

Step 3C: If No Paid Tool Data

Use qualitative signals to estimate viability:

  • Autocomplete presence — does Google suggest it? (strong signal)
  • PAA presence — do People Also Ask boxes appear? (strong signal)
  • AI Overview presence — does Google show an AI answer? (GEO signal)
  • SERP richness — do dedicated pages exist for this term, or only tangential mentions?

Flag low-confidence keywords (no autocomplete, no PAA, no dedicated pages) and recommend removing them.

Step 3D: Present the Pruned List

Show the user how many keywords survived validation:

  • "Started with X keywords → Y have confirmed volume / strong signals → Z removed as dead weight"
  • Present the surviving list sorted by volume (or signal strength)

Ask: "Ready to cluster and prioritize?"


Phase 4: Analysis & Clustering

Step 4A: Classify Intent

Tag every keyword with search intent:

IntentSignalExample
Informationalhow, what, why, guide, tutorial"synthetic data"
Commercialbest, top, review, platform, tool"data labeling"
Researchdataset, benchmark, model"VLA model"
Transactionalbuy, pricing, discount, free trial"asana pricing"

Step 4B: Assign Priority by Difficulty

Use KD (Keyword Difficulty) when available from paid tool data. Otherwise estimate from SERP competition.

PriorityKD RangeMeaning
Easy Win0-15Low competition — target immediately
Target16-50Winnable with good content
ContentAny KD, but broad/tangentialWrite about it for authority, don't expect to rank
Hard50+Only pursue with strong domain authority

Step 4C: Cluster by Topic

Group keywords into topic clusters. A good cluster has:

  • 1 pillar keyword (broadest term, highest volume)
  • 3-8 supporting keywords (related terms in the same topic area)

Name each cluster with a descriptive label. No scoring — just group related keywords so the user can see which topics have depth.

Step 4D: Identify Top Easy Wins

Extract the best opportunities — keywords with the highest volume-to-difficulty ratio and strong relevance. These are the "do first" list.

Present the clustered, scored list to the user. Ask: "Ready for the final deliverable?"


Phase 5: Deliverable — keywords.csv (STRICT FORMAT)

Your final response must be raw CSV content and nothing else. The harness captures your final output verbatim, saves it as keywords.csv, and validates it against keywords.csv.schema.md. Any deviation fails the artifact.

Absolute rules

  1. No prose before or after the CSV. The first character of your final response must be k (start of the header keyword,...). The last character must be the final character of the last data row.
  2. No code fences. Do not wrap the CSV in ``` ` `` or `` `csv ```. Just emit the CSV content.
  3. Exact header, exact order. First row must be: keyword,volume,kd,intent,priority,cluster,is_pillar,ai_overview_present,source,notes
  4. Exactly 10 fields per row. Empty fields are allowed where the schema permits; write them as two adjacent commas (e.g. ,,).
  5. Quote fields containing commas, newlines, or double-quotes. Escape embedded " as "".
  6. Minimum 10 data rows. Fewer rows fails validation.

Column contract

#ColumnTypeRequiredAllowed values
1keywordstringyes1–3 words, unique (case is normalized by the harness — write naturally, e.g. GEO tool)
2volumeinteger \emptyno0+; empty if unknown
3kdinteger \emptyno0100; empty if unknown
4intentenumyesinformational \commercial \research \transactional
5priorityenumyeseasy_win \target \content \hard
6clusterstringyesnon-empty
7is_pillarbooleanyestrue \false
8ai_overview_presentboolean \emptynotrue \false \empty
9sourcestringyesone of ahrefs, semrush, serpapi, autocomplete, paa, reddit, competitor, manual
10notesstringnofree text

Semantic rules

  • Keywords with volume=0 from paid-tool data MUST be removed, not emitted
  • Every cluster must have at least one row with is_pillar=true
  • No duplicate keyword values
  • Apply your intent/priority classification from Phase 4 consistently

Example (what your entire final response must look like)

keyword,volume,kd,intent,priority,cluster,is_pillar,ai_overview_present,source,notes
synthetic data,2400,42,research,target,synthetic_data,true,true,ahrefs,high GEO signal
data labeling,1900,38,commercial,target,synthetic_data,false,true,ahrefs,
vla model,320,12,research,easy_win,robotics_models,true,,serpapi,uncontested niche
robot training,880,35,commercial,target,robotics_models,false,false,ahrefs,
teleoperation,210,28,research,easy_win,robotics_models,false,,paa,strong PAA coverage

(Above is illustrative — your actual CSV has 10+ rows covering your full validated keyword set.)

Strategic notes, blog topics, killed keywords

These do NOT go in the final CSV. If you want to surface them, fold signal into the notes column per row (e.g. notes="polluted by enterprise infra — always use modifiers"). Everything else is dropped for this artifact.

Before emitting

Mentally run through the checklist:

  • Final response starts with keyword,volume,kd,intent,priority,cluster,is_pillar,ai_overview_present,source,notes\n
  • No code fences anywhere
  • No prose before or after
  • ≥ 10 data rows
  • Every row has exactly 10 comma-separated fields
  • Every enum value is from the allowed set (exact spelling)
  • No duplicate keywords
  • Every cluster has one pillar

Then emit the CSV. Nothing else.


Rules

  1. Target keywords must be 1-3 words — this is non-negotiable. Longer phrases go in Blog Topics or GEO Queries. Keywords like "teleoperation data collection for robots" are blog titles, not target keywords.
  2. No fabricated data — do not invent search volumes. Use paid tool data when available, qualitative signals when not. Never estimate or guess a number.
  3. Kill dead keywords early — if a keyword has no autocomplete presence, no PAA, no dedicated SERP results, and no volume in paid tools, remove it. A list of 50 real keywords beats 100 with half dead.
  4. This skill is SEO-focused — SEO keywords (1-3 words) optimize pages for Google ranking. For GEO prompt targeting (full questions for AI citation), use the geo-content-research skill separately.
  5. Real language over marketer language — prioritize the words actual users type, not industry jargon
  6. Interactive — do not skip phases. Get user confirmation before moving to the next phase
  7. Output is actionable — the deliverable should be directly usable for content planning without further analysis
  8. Integrate paid tools when available — Ahrefs/Semrush data is always better than guessing. Offer to integrate it. But the skill works without it too.

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

32.46%
按下载量换算32

Claude

29.53%
按下载量换算29

Cursor

18.84%
按下载量换算19

Gemini CLI

10.06%
按下载量换算10

安全审计

Gen Agent Trust Hub

通过

Socket

可疑

Snyk

可疑

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在 warning/failed 结果,不能写成本站确认安全。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills