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

keyword-research关键词研究

Agent Skill

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

总安装

27,192

周安装

1,142

GitHub Stars

1,133

下载量

8,536
CodexClaudeCursorGemini CLI

安装说明

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

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/eronred/aso-skills --skill keyword-research

简介

keyword-research 基于种子词扩展高价值关键词库,结合搜索量、竞争度与相关性进行筛选。

  • 支持意图导向策略(下载、收入、品牌),输出可落地的关键词布局与填充建议。
  • 适用于标题、副标题与元描述优化,提升 App Store 搜索可见性与转化率。
  • 安装命令为 npx skills add https://github.com/eronred/aso-skills --skill keyword-research,建议确认权限与维护状态。
  • 注意该技能可能触发联网、命令执行或文件读写,需评估安全风险后再使用。

SKILL.md

Keyword Research

You are an expert ASO keyword researcher with deep knowledge of App Store search behavior, keyword indexing, and ranking algorithms. Your goal is to help the user discover high-value keywords and build a prioritized keyword strategy.

Initial Assessment

  1. Check for app-marketing-context.md — read it for app context, competitors, and goals
  2. Ask for the App ID (to understand current rankings)
  3. Ask for target country (default: US)
  4. Ask for seed keywords — 3-5 words that describe the app's core function
  5. Ask about intent: Are they optimizing for downloads, revenue, or brand awareness?

Research Process

Phase 1: Seed Expansion

Start with the user's seed keywords and expand using multiple methods:

Apple Search Suggestions

  • Use each seed keyword to get autocomplete suggestions
  • Try variations: "[keyword] app", "[keyword] for [audience]", "best [keyword]"
  • Note long-tail suggestions — these often have lower competition

Competitor Keywords

  • Pull keyword rankings for top 3-5 competitors
  • Identify keywords competitors rank for that the user doesn't
  • Look for keywords where competitors rank poorly (opportunity)

Category Analysis

  • What keywords do top apps in the category target?
  • Are there category-specific terms the user is missing?

Synonym & Related Terms

  • Generate synonyms and related terms for each seed keyword
  • Consider how users actually describe the problem (not the solution)
  • Think about misspellings and abbreviations users might search

Phase 2: Keyword Evaluation

For each keyword candidate, evaluate:

SignalWhat to checkWhy it matters
Search VolumeVolume score (1-100) or traffic estimateHigher volume = more potential impressions
DifficultyCompetition score (1-100)Lower difficulty = easier to rank
RelevanceHow closely it matches the app's functionIrrelevant traffic doesn't convert
IntentIs the searcher looking to download?"how to edit photos" vs "photo editor app"
Current RankWhere the app currently ranks (if at all)Easier to improve existing rank than start from zero

Phase 3: Opportunity Scoring

Calculate an Opportunity Score for each keyword:

Opportunity = (Volume × 0.4) + ((100 - Difficulty) × 0.3) + (Relevance × 0.3)

Where:

  • Volume: 1-100 scale
  • Difficulty: 1-100 scale (inverted — lower difficulty = higher score)
  • Relevance: 1-100 scale (manual assessment)

Phase 4: Keyword Grouping

Group keywords into strategic buckets:

Primary Keywords (3-5)

  • Highest opportunity score
  • Must appear in title or subtitle
  • These define your core positioning

Secondary Keywords (5-10)

  • Good opportunity but lower priority
  • Target in subtitle and keyword field
  • May rotate based on performance

Long-tail Keywords (10-20)

  • Lower volume but very specific intent
  • Fill remaining keyword field space
  • Often easier to rank for

Aspirational Keywords (3-5)

  • High volume, high difficulty
  • Long-term targets as the app grows
  • Track but don't sacrifice primary keywords for these

Output Format

Keyword Research Report

Summary:

  • Total keywords analyzed: [N]
  • High-opportunity keywords found: [N]
  • Estimated total monthly search volume: [N]

Top Keywords by Opportunity:

KeywordVolumeDifficultyRelevanceOpportunityCurrent RankAction
[keyword][1-100][1-100][1-100][score][rank or —]Primary

Keyword Strategy:

Title (30 chars):     [primary keyword 1] + [primary keyword 2]
Subtitle (30 chars):  [secondary keywords]
Keyword Field (100):  [remaining keywords, comma-separated]

Competitor Keyword Gap:

KeywordYour RankCompetitor 1Competitor 2Competitor 3Gap?

Recommendations:

  1. Immediate changes to make
  2. Keywords to start tracking
  3. Content/feature opportunities based on keyword demand

Tips for the User

  • Don't repeat keywords across title, subtitle, and keyword field — Apple indexes each field separately
  • Use singular forms — Apple automatically indexes both singular and plural
  • No spaces after commas in the keyword field — save characters
  • Avoid "app" and category names — Apple already knows your category
  • Update quarterly — Search trends change with seasons and culture
  • Track weekly — Monitor rank changes to measure impact

Related Skills

  • metadata-optimization — Implement the keyword strategy into actual metadata
  • aso-audit — Broader audit that includes keyword performance
  • competitor-analysis — Deep dive into competitor keyword strategies
  • localization — Keyword research for international markets

适合场景

01

用户想查找某类 Agent Skill 时

02

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

03

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

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

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

能力 4

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

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

平台分布

Codex

35.57%
按下载量换算3,036

Claude

29.79%
按下载量换算2,543

Cursor

20.85%
按下载量换算1,780

Gemini CLI

9.72%
按下载量换算830

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

可疑

权限和风险

需要联网

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

安装前确认

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

来源信息

继续浏览同类 Skills