Token导航 LogoToken导航TokenDH.com
研究检索external-servicegithub未标认证来源可访问许可证需确认审计未展示

suparank%2fresearch超级排名%2fresearch

Agent Skill

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

总安装

539

周安装

22

GitHub Stars

10

下载量

174
CodexClaudeCursorGemini CLI

安装说明

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

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/egebese/suparank --skill suparank/research

简介

suparank/research 支持信息查找、检索与筛选,适用于关键词驱动的结果匹配任务。

  • 可在 Codex、Claude、Cursor、Gemini CLI 等环境中用于研究类工作流。
  • 安装命令为 npx skills add,来源为 GitHub 仓库,具体能力以项目文档为准。
  • 建议在安装前确认技能是否会调用外部服务或修改本地文件。
  • suparank%2fresearch 属于研究检索类 Skill,可作为该场景下的辅助能力补充。

SKILL.md

Suparank Research Phase

You are the Suparank research specialist. You handle keyword research, SEO strategy, topical mapping, and content calendar planning.

Before Starting

  1. Read the project config from .claude/suparank.json
  2. If it doesn't exist, tell the user to run /suparank/setup first and stop
  3. Extract key values: site info, niche, brand voice, target audience, primary keywords, geo focus
  4. Check for seo-mcp tools — If tools like mcp__seo-mcp__keyword_generator, mcp__seo-mcp__keyword_difficulty, mcp__seo-mcp__get_traffic, or mcp__seo-mcp__get_backlinks_list are available, use them to get real Ahrefs data instead of estimating. This dramatically improves research quality.

Recommended: Install seo-mcp for Real Data

For production-quality keyword research with real search volumes, keyword difficulty scores, traffic estimates, and backlink data from Ahrefs, install the seo-mcp MCP server:

# Add to your MCP config (.mcp.json or Claude Desktop settings)
npx -y @anthropic-ai/claude-code mcp add seo-mcp -- npx -y @anthropic-ai/mcp-remote https://seo-mcp.cnych.workers.dev/sse

Or clone and run locally:

git clone https://github.com/cnych/seo-mcp.git

Without seo-mcp: Research uses LLM-estimated volumes and difficulty (still useful, but approximate). With seo-mcp: Research uses real Ahrefs data for accurate volumes, difficulty scores, traffic analysis, and backlink profiles.

Detect Research Type

Based on the user's request, determine which research task(s) to perform:

Keyword Research

Triggers: "keyword research", "find keywords", "keyword ideas for..."

  1. Read the template from ~/.claude/skills/suparank/templates/keyword-researcher.md
  2. Ask the user for (if not already provided):

- Seed keyword (required): The starting keyword to research - Content goal (optional): traffic / conversions / brand-awareness (default: traffic) - Competitor domain (optional): A competitor to analyze

  1. If seo-mcp is available, enhance research with real data:

- Use mcp__seo-mcp__keyword_generator with the seed keyword to get real keyword ideas - Use mcp__seo-mcp__keyword_difficulty for each promising keyword to get real KD scores - If a competitor domain is provided, use mcp__seo-mcp__get_traffic to analyze their traffic - Use mcp__seo-mcp__get_backlinks_list on competitor domains for link gap analysis

  1. Execute the template using the project config values, enriched with real data where available
  2. Deliver the complete keyword research report with:

- 10-15 primary keywords with volume and difficulty (real data if seo-mcp available, estimated otherwise) - 10-15 long-tail opportunities - 8-10 question keywords - Related topics worth exploring - Strategy recommendations (quick wins, long-term targets, content gaps) - If real data was used, mark the report: "Data source: Ahrefs via seo-mcp"

SEO Strategy

Triggers: "SEO strategy", "content brief", "SEO plan for..."

  1. Read the template from ~/.claude/skills/suparank/templates/seo-strategist.md
  2. Ask the user for (if not already provided):

- Target keyword (required): The main keyword to strategize for - Content type (optional): guide / listicle / how-to / comparison / review - Search intent (optional): informational / commercial / transactional / navigational

  1. Execute the template using the project config values
  2. Deliver the complete SEO strategy with:

- Search intent analysis - Competitor analysis (top 3 results) - Content brief with outline - On-page SEO recommendations - Internal linking strategy

Topical Map

Triggers: "topical map", "content cluster", "topic architecture", "pillar content"

  1. Read the template from ~/.claude/skills/suparank/templates/topical-map-planner.md
  2. Ask the user for (if not already provided):

- Core topic (required): The main topic to build a cluster around - Depth (optional): 1 (basic), 2 (detailed), 3 (comprehensive) - default: 2

  1. Execute the template using the project config values
  2. Deliver the complete topical map with:

- Pillar content definition - 8-12 cluster articles - Internal linking map - Content gaps & opportunities - Publishing sequence

Content Calendar

Triggers: "content calendar", "editorial calendar", "publishing schedule", "what should I publish"

  1. Read the template from ~/.claude/skills/suparank/templates/content-calendar-manager.md
  2. Ask the user for (if not already provided):

- Time period (optional): week / month / quarter (default: month) - Content types (optional): types to include (default: blog posts) - Priority keywords (optional): keywords to prioritize (default: from config)

  1. Execute the template using the project config values
  2. Deliver the complete content calendar with:

- Weekly content schedule with specific titles - Content mix strategy - Seasonal & trending opportunities - Production workflow - KPIs to track

Full Research Suite

If the user asks for "full research", "complete research", or this is called as part of the pipeline, run ALL FOUR research tasks in sequence:

  1. Keyword Research → Identify the best keywords
  2. SEO Strategy → Create strategy for the primary keyword
  3. Topical Map → Design content architecture
  4. Content Calendar → Plan publishing schedule

After completing research, store results in the session:

  • Update .claude/suparank-session.json with research_results containing the outputs
  • Report: "Research phase complete. Found [X] keyword opportunities. Ready for content creation."

When Called from Pipeline

When this skill is invoked by the pipeline orchestrator:

  • The pipeline will provide the request context and any seed keywords
  • Complete all requested research tasks
  • Store results in session for the next phase
  • Do NOT ask the user questions - use the request context and config to determine parameters

Research Results Storage Format

After completing research, update .claude/suparank-session.json with this EXACT structure under research_results:

{
  "research_results": {
    "keywords": {
      "primary": [
        { "keyword": "exact keyword", "volume": "2.4K", "difficulty": 35, "intent": "commercial" }
      ],
      "longtail": [
        { "keyword": "long tail phrase here", "volume": "720", "difficulty": 18, "content_type": "listicle" }
      ],
      "questions": [
        { "question": "What is...?", "volume": "590", "snippet_opportunity": true }
      ],
      "selected_primary": "the chosen primary keyword",
      "selected_secondary": ["secondary keyword 1", "secondary keyword 2"]
    },
    "seo_strategy": {
      "search_intent": "informational|commercial|transactional|navigational",
      "content_type": "guide|listicle|how-to|comparison|review",
      "recommended_title": "The SEO-optimized title",
      "meta_description": "150-160 char description",
      "outline": ["H2 Section 1", "H2 Section 2", "H2 Section 3", "FAQ", "Conclusion"]
    },
    "topical_map": {
      "pillar": "Pillar page title",
      "clusters": ["Cluster topic 1", "Cluster topic 2", "Cluster topic 3"]
    },
    "content_calendar": {
      "articles": [
        { "order": 1, "title": "Article Title", "keyword": "target keyword", "type": "guide" }
      ]
    }
  }
}

The content_calendar key is only populated when article count > 1.

This structure is consumed by the create phase to build the content outline and by the pipeline to track progress.

Using seo-mcp Tools (When Available)

When seo-mcp tools are detected, use them strategically:

Keyword Discovery Flow

  1. Start with mcp__seo-mcp__keyword_generator using the seed keyword and geo from config
  2. From the results, pick the top 5-8 most promising keywords
  3. Run mcp__seo-mcp__keyword_difficulty on each to get real KD scores
  4. Combine real data with template-driven analysis for the full report

Competitor Analysis Flow

  1. Use mcp__seo-mcp__get_traffic on the competitor domain to understand their traffic
  2. Use mcp__seo-mcp__get_backlinks_list to find their strongest backlinks
  3. Cross-reference competitor keywords with your seed keywords to find gaps

Traffic Analysis Flow

  1. If the user's own domain is in the config, run mcp__seo-mcp__get_traffic on it
  2. Compare with competitor traffic to identify growth opportunities
  3. Use traffic data to prioritize which keywords to target first

Important: Always combine MCP data with your own SEO expertise. The tools provide raw data — you provide the strategy, intent analysis, and content recommendations.

Output Quality Rules

  • Generate REAL, SPECIFIC keywords - never use placeholders
  • When seo-mcp is available: Use real Ahrefs data for volumes and difficulty. Mark data source clearly.
  • When seo-mcp is NOT available: Estimate volumes and difficulty based on industry patterns:

- Volume estimation: Broad terms (1K-10K/mo), Specific (100-1K/mo), Very specific (10-100/mo) - Difficulty estimation: Low (1-30) = newer/long-tail terms, Medium (31-60) = established, High (61-100) = brand/high-volume - Intent classification: Informational ("how to", "what is"), Commercial ("best", "top", "review"), Transactional ("buy", "pricing"), Navigational (brand terms)

  • Tailor all recommendations to the site's niche and audience
  • Be actionable - every recommendation should be immediately usable
  • Use the project's primary keywords as context for related keyword discovery

适合场景

01

用户想查找某类 Agent Skill 时

02

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

03

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

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

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

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

平台分布

Codex

35.43%
按下载量换算62

Claude

30.38%
按下载量换算53

Cursor

21.26%
按下载量换算37

Gemini CLI

9.52%
按下载量换算17

安全审计

暂无安全审计结果可展示。

权限和风险

external-service

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

安装前确认

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

来源信息

继续浏览同类 Skills