Token导航 LogoToken导航

Agent Skill · 研究检索

seo-keywords(SEO keywords 搜索)

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

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

总安装 346周安装 14GitHub Stars 28下载 109核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/mangollc/claude-seo-skill --skill seo-keywords

这个 Skill 是做什么的

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

用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词快速定位候选结果。适用于关键词研究、SEO 策略制定、信息收集和线索筛选等场景。通过关键词、任务场景或来源线索快速定位候选结果,可结合来源仓库继续核验具体用法。

安装命令:npx skills add https://github.com/mangollc/claude-seo-skill --skill seo-keywords。建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

来源仓库内路径:skills/seo-keywords

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

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

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

    它标注为只读,先用只读任务试一次,确认行为符合预期再扩大使用范围。

常见问题

6 条

seo-keywords 怎么安装?

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

seo-keywords 支持哪些 AI 工具?

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

seo-keywords 需要什么权限?

权限级别是只读。该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

seo-keywords 是免费的吗?

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

seo-keywords 用的人多吗?

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

seo-keywords 安全吗?

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

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

值得选的地方

  • 同时适配 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调用外部服务未明确有提醒
seo-keywords

SEO keywords 搜索 · 本页

34628只读未明确有提醒

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

SKILL.md 原文

SEO Keyword Strategy

Always load client context first. See rules/client-setup.md for the client loading pattern.

File Organization

Save all output to .seo/clients/{slug}/keywords/:

keywords/
├── research-{date}.json           # Raw keyword research
├── clusters.json                  # Keyword clusters
├── competitor-gap.json            # Gap analysis
├── topic-map.json                 # Topical authority map
├── serp-features-{date}.json      # SERP feature analysis
├── competitor-strategy.json       # Competitor content RE
└── programmatic-templates/        # Template patterns
    ├── location-template.json
    └── comparison-template.json

Workflow A: Local/Service Business Keywords

For clients with business_type: "local".

Step 1: Seed Keyword Discovery

# Search for core service + location combinations
firecrawl search "{service} {city}" --limit 20 -o .seo/clients/{slug}/keywords/.firecrawl/seed-{service}.json --json
firecrawl search "{service} near me" --limit 20 -o .seo/clients/{slug}/keywords/.firecrawl/seed-nearme.json --json
firecrawl search "best {service} in {city}" --limit 20 -o .seo/clients/{slug}/keywords/.firecrawl/seed-best.json --json

Run in parallel for each service and service area from client config.

Step 2: Competitor Keyword Extraction

# Map competitor sites to find all their pages
firecrawl map {competitor-domain} --search "{industry}" -o .seo/clients/{slug}/keywords/.firecrawl/comp-{name}-urls.txt &
# Repeat for each competitor in parallel
wait

# Scrape competitor service pages for keyword patterns
firecrawl scrape {competitor-url} --format markdown,links -o .seo/clients/{slug}/keywords/.firecrawl/comp-{name}-page.json

Extract from competitor pages: title tags, H1s, H2s, service names, location modifiers, URL slugs. These reveal the keywords they target.

Step 3: Local Keyword Expansion

Generate geo-modified variants for each core service:

  • {service} {city} — primary
  • {service} {city} {state} — long-tail
  • {service} near {neighborhood} — hyperlocal
  • {service} in {zip_code} — zip-targeted
  • best {service} {city} — commercial intent
  • {service} cost {city} — transactional
  • emergency {service} {city} — urgent intent
  • {service} reviews {city} — social proof

Step 4: Revenue Mapping

Classify each keyword by revenue potential:

  • High: directly leads to service booking (e.g., "emergency plumber austin")
  • Medium: research phase but close to conversion (e.g., "plumber cost austin")
  • Low: informational, builds authority (e.g., "how to fix a leaky faucet")

Prioritize high-revenue keywords first. Low-revenue informational keywords support topical authority.

Workflow B: SaaS/Online Business Keywords

For clients with business_type: "saas" or "ecommerce".

Step 1: Product-Led Discovery

# Search for product category and feature keywords
firecrawl search "{product-category} software" --limit 20 -o .seo/clients/{slug}/keywords/.firecrawl/product-cat.json --json
firecrawl search "{product-name} alternatives" --limit 20 -o .seo/clients/{slug}/keywords/.firecrawl/alternatives.json --json
firecrawl search "{problem-solved} tools" --limit 20 -o .seo/clients/{slug}/keywords/.firecrawl/problem-tools.json --json

Step 2: Funnel-Stage Classification

  • BOFU (Bottom of Funnel): "{product} pricing", "{product} vs {competitor}", "buy {product}", "{product} demo"
  • MOFU (Middle of Funnel): "best {category} software", "how to {solve problem}", "{category} comparison"
  • TOFU (Top of Funnel): "what is {concept}", "{industry} trends", "{problem} guide"

Step 3: Feature vs Problem Keywords

  • Feature keywords: "{feature-name} software", "tool with {feature}"
  • Problem keywords: "how to {solve problem}", "{pain point} solution"
  • Use-case keywords: "{product-category} for {industry}", "{product-category} for {team-size}"

Keyword Clustering

Group keywords into clusters by semantic similarity and shared SERP results.

Method

For each seed keyword group, search Google via firecrawl and compare the top 10 results. Keywords that share 3+ of the same top 10 URLs belong to the same cluster.

# Search for each keyword to see SERP overlap
firecrawl search "{keyword}" --limit 10 -o .seo/clients/{slug}/keywords/.firecrawl/serp-{keyword-slug}.json --json

Output Format

{
  "clusters": [
    {
      "name": "Cluster Name",
      "pillar_keyword": "main keyword",
      "keywords": ["keyword1", "keyword2", "keyword3"],
      "intent": "commercial",
      "estimated_volume": "high|medium|low",
      "recommended_page_type": "service-page|blog-post|landing-page|comparison-page",
      "current_url": null,
      "gap": true
    }
  ]
}

Search Intent Classification

For each keyword, classify intent based on SERP analysis:

IntentSERP SignalsExamples
TransactionalProduct pages, pricing, buy buttons dominate"buy X", "X pricing", "X coupon"
CommercialComparison pages, reviews, listicles dominate"best X", "X vs Y", "X reviews"
InformationalBlog posts, how-tos, Wikipedia dominate"what is X", "how to X", "X guide"
NavigationalBrand homepages, login pages dominate"X login", "X website", brand names

Difficulty Assessment

For each target keyword, analyze the top 10 SERP results:

firecrawl search "{keyword}" --scrape --limit 10 -o .seo/clients/{slug}/keywords/.firecrawl/difficulty-{slug}.json --json

Score difficulty (1-10) based on:

  • Content depth: avg word count of top 10 results
  • Domain authority signals: well-known brands vs niche sites
  • Content freshness: how recently updated
  • SERP feature presence: featured snippets, PAA boxes (more features = more competition)
  • Content type match: can you create the same content type as top results?

Competitor Keyword Gap Analysis

Compare client's content against 2-3 competitors:

# Map all pages for client and each competitor
firecrawl map {client-domain} -o .seo/clients/{slug}/keywords/.firecrawl/client-urls.txt &
firecrawl map {competitor1-domain} -o .seo/clients/{slug}/keywords/.firecrawl/comp1-urls.txt &
firecrawl map {competitor2-domain} -o .seo/clients/{slug}/keywords/.firecrawl/comp2-urls.txt &
wait

Compare URL structures and page titles to identify topics competitors cover that the client does not. Output as prioritized gap list.

Topical Authority Mapping

Build a content architecture around topic clusters:

Step 1: Identify Pillar Topics

From keyword clusters, identify 3-5 broad pillar topics that the client should own. Each pillar becomes a comprehensive page (2000+ words).

Step 2: Map Cluster Content

For each pillar, identify 8-15 supporting cluster articles that link back to the pillar page. Use keyword clusters to assign one cluster per article.

Step 3: Internal Link Map

Define the linking structure:

  • Each cluster article links to its pillar page
  • Pillar page links to all cluster articles
  • Related cluster articles interlink where natural

Output Format

{
  "pillars": [
    {
      "topic": "Pillar Topic Name",
      "pillar_keyword": "main keyword",
      "pillar_url": "/pillar-page-slug",
      "clusters": [
        {
          "title": "Cluster Article Title",
          "target_keyword": "cluster keyword",
          "url": "/cluster-slug",
          "status": "exists|gap",
          "links_to_pillar": true,
          "interlinks": ["/related-cluster-1", "/related-cluster-2"]
        }
      ]
    }
  ]
}

SERP Feature Analysis

For target keywords, identify which SERP features appear and which the client can win:

firecrawl search "{keyword}" --scrape --limit 5 -o .seo/clients/{slug}/keywords/.firecrawl/serp-{slug}.json --json

Track these SERP features:

  • Featured Snippet (paragraph, list, table) — optimize content format to match
  • People Also Ask — create FAQ content for these questions
  • Image Pack — optimize images with descriptive alt text and filenames
  • Video Carousel — create video content for these queries
  • Local Pack — requires GBP optimization (see seo-local skill)
  • Knowledge Panel — requires entity optimization (see seo-aeo skill)
  • AI Overview — requires AEO optimization (see seo-aeo skill)
  • Sitelinks — requires clear site architecture and navigation

Competitor Content Strategy Reverse Engineering

Analyze competitor content operations:

# Map all competitor content
firecrawl map {competitor-domain} --search "blog" -o .seo/clients/{slug}/keywords/.firecrawl/comp-blog-urls.txt
firecrawl map {competitor-domain} -o .seo/clients/{slug}/keywords/.firecrawl/comp-all-urls.txt

Then scrape a sample of pages to analyze:

  • Content types: blog posts, landing pages, tools, comparisons, case studies
  • Publishing frequency: estimate from URL dates, sitemap lastmod, or content dates
  • Content length patterns: sample 10-15 pages, calculate avg word count by content type
  • Topic coverage: map their content to your topic clusters to find their strengths/weaknesses
  • Update cadence: look for "updated on" dates, fresh statistics, recent examples

Programmatic SEO Templates

For SaaS/ecommerce clients with repeatable page patterns:

Location Pages Template

{
  "template_type": "location",
  "url_pattern": "/{service}-{city}-{state}",
  "title_pattern": "{Service} in {City}, {State} | {Brand}",
  "h1_pattern": "{Service} in {City}, {State}",
  "sections": [
    "Local intro paragraph with city-specific details",
    "Service description (shared, with local modifiers)",
    "Service area map / neighborhoods served",
    "Local testimonials / reviews",
    "FAQPage schema with city-specific FAQ",
    "CTA with local phone number"
  ],
  "schema_type": "LocalBusiness",
  "internal_links": ["pillar-service-page", "nearby-location-pages"]
}

Comparison Pages Template

{
  "template_type": "comparison",
  "url_pattern": "/{product}-vs-{competitor}",
  "title_pattern": "{Product} vs {Competitor}: {Year} Comparison",
  "h1_pattern": "{Product} vs {Competitor}",
  "sections": [
    "Quick verdict / summary table",
    "Feature-by-feature comparison",
    "Pricing comparison",
    "Pros and cons of each",
    "Who should choose which",
    "FAQPage schema"
  ],
  "schema_type": "Article",
  "internal_links": ["product-page", "pricing-page"]
}

Category Pages Template

{
  "template_type": "category",
  "url_pattern": "/best-{category}-{modifier}",
  "title_pattern": "Best {Category} for {Modifier} ({Year})",
  "sections": [
    "Quick picks / top 3 summary",
    "Evaluation criteria",
    "Detailed reviews of each option",
    "Comparison table",
    "How to choose guide",
    "FAQ section"
  ]
}

Output Schema

All keyword data should follow this format:

{
  "keyword": "emergency plumber austin",
  "cluster": "emergency-plumbing",
  "intent": "transactional",
  "difficulty": 6,
  "volume_estimate": "medium",
  "revenue_potential": "high",
  "funnel_stage": "bofu",
  "serp_features": ["local_pack", "paa", "ai_overview"],
  "recommended_page_type": "service-page",
  "current_url": null,
  "competitor_coverage": ["comp-a", "comp-b"],
  "priority": 1,
  "notes": ""
}

平台分布

Codex

37.26%
按下载量换算41

Claude

31.29%
按下载量换算34

Cursor

16.78%
按下载量换算18

Gemini CLI

9.21%
按下载量换算10

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

可疑

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

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

继续浏览同类 Skills