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

rank-monitor等级监察员

Agent Skill

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

总安装

564

周安装

24

GitHub Stars

67

下载量

198
CodexClaudeCursorGemini CLI

安装说明

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

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/indranilbanerjee/digital-marketing-pro --skill rank-monitor

简介

rank-monitor 用于查找、检索和筛选与等级监察相关的信息。

  • 适合在 Codex、Claude、Cursor、Gemini CLI 中根据关键词定位候选结果。
  • 通过 npx skills add 命令从指定 GitHub 仓库安装并使用。
  • 安装前需确认权限范围和维护状态,注意可能触发联网或文件操作。
  • 建议结合原始 README 核验具体用法和功能边界。

SKILL.md

/dm:rank-monitor

Purpose

Set up and manage keyword ranking monitoring. Track target keyword positions across Google via Moz and Google Search Console MCPs, establish baselines, detect drops greater than 5 positions, and generate alerts when rankings change significantly. This command provides ongoing visibility into organic search performance — catching ranking declines early before they impact traffic, identifying upward trends to double down on, and tracking competitive position shifts that signal market changes.

Input Required

The user must provide (or will be prompted for):

  • Target keywords: A list of keywords to monitor — can be provided directly, imported from a CSV or Google Sheet, or pulled from the brand's existing keyword tracking list at ~/.claude-marketing/brands/{slug}/seo/keywords.json. Keywords should include search intent classification (informational, navigational, transactional, commercial) if available
  • Monitoring frequency: daily or weekly — daily is recommended for high-priority head terms and active campaign keywords, weekly for long-tail and lower-priority terms. Determines how often ranking checks run and how granular the trend data will be
  • Alert thresholds: Position change that triggers an alert — default is >5 position drop. Can be customized per keyword group (e.g., >3 for brand terms, >5 for head terms, >10 for long-tail). Both drop and gain thresholds are supported
  • Competitor domains (optional): Domains to track alongside the brand for the same keywords — see how competitors rank for your target terms and detect when they gain or lose positions. Up to 10 competitor domains
  • Device type: mobile, desktop, or both — rankings often differ significantly between devices, especially for local and mobile-intent queries
  • Target country: The Google locale to check rankings in — e.g., US, UK, AU, CA, IN. Determines the search results market for position tracking

Process

  1. Load brand context: Read ~/.claude-marketing/brands/_active-brand.json for the active slug, then load ~/.claude-marketing/brands/{slug}/profile.json. Apply brand voice, compliance rules for target markets (skills/context-engine/compliance-rules.md), and industry context. Also check for guidelines at ~/.claude-marketing/brands/{slug}/guidelines/_manifest.json — if present, load restrictions. Check for agency SOPs at ~/.claude-marketing/sops/. If no brand exists, ask: "Set up a brand first (/dm:brand-setup)?" — or proceed with defaults.
  2. Capture current rankings baseline: Query Moz MCP and Google Search Console MCP for the current ranking position of each target keyword. Record position, ranking URL, SERP features present (featured snippet, People Also Ask, AI Overview, local pack, image pack, video carousel, sitelinks), click-through rate from GSC where available, and impressions. For competitor domains, capture their positions for the same keywords.
  3. Configure monitoring schedule: Save the keyword list, monitoring frequency, alert thresholds, competitor domains, device type, and target country to the brand's SEO directory at ~/.claude-marketing/brands/{slug}/seo/rank-monitor-config.json. Create or update the baseline snapshot at ~/.claude-marketing/brands/{slug}/seo/rank-baseline.json with the current positions as the reference point.
  4. On each monitoring check: query and compare: Pull current positions for all tracked keywords via Moz and GSC MCPs. Compare each keyword's current position to both the baseline (original position when monitoring started) and the previous check (last recorded position). Calculate absolute change from baseline, change since last check, rolling 7-day and 30-day trend direction, and average position across all tracked keywords.
  5. Detect significant changes: Identify keywords that crossed alert thresholds — drops exceeding the configured position threshold, keywords that fell from page 1 (positions 1-10) to page 2 or beyond, keywords that gained >5 positions (potential quick-win opportunities), new SERP feature appearances or losses for the brand's ranking URLs, and competitor rank changes that moved them above or below the brand for tracked terms.
  6. Generate alert if thresholds are breached: Categorize alerts by severity — minor for 3-5 position drops (monitor but no immediate action needed), major for 5-10 position drops (investigate content freshness, technical issues, or competitor activity), critical for >10 position drops or page 1 to page 2 transitions (immediate investigation required — check for algorithm updates, manual actions, technical errors, or content cannibalization). Include recommended next steps for each severity level.

Output

A structured ranking report containing:

  • Ranking snapshot: Current positions for all tracked keywords — position, ranking URL, device, country, date, and comparison to baseline and previous check with directional indicators (up, down, stable)
  • Change report: Position changes since baseline and since last check — sorted by largest drops first, with trend sparklines showing 7-day and 30-day direction for each keyword
  • Alert summary: Keywords needing attention — grouped by severity (critical, major, minor) with specific position changes, affected URLs, and recommended investigation steps
  • SERP feature tracker: Which SERP features are present for each keyword and whether the brand owns them — featured snippets, People Also Ask inclusions, AI Overview citations, local pack presence, and changes since last check
  • Competitor comparison: Relative position changes for tracked competitor domains — who gained, who lost, head-to-head position for each keyword, and competitive gap trends over time

Agents Used

  • seo-specialist — Keyword ranking analysis and interpretation, SERP feature tracking and ownership assessment, ranking change diagnosis (algorithm update vs. technical issue vs. competitive displacement vs. content decay), baseline establishment and trend calculation, and recommended actions for each severity level based on SEO best practices and historical patterns
  • performance-monitor-agent — Alert generation with severity classification based on configurable thresholds, monitoring schedule management and check execution, threshold breach detection with rolling window comparison, trend tracking with 7-day and 30-day directional analysis, and notification formatting for ranking change alerts

适合场景

01

用户想查找某类 Agent Skill 时

02

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

03

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

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

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

能力 4

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

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

平台分布

Codex

33.93%
按下载量换算67

Claude

31.61%
按下载量换算63

Cursor

17.65%
按下载量换算35

Gemini CLI

9.84%
按下载量换算19

安全审计

Gen Agent Trust Hub

通过

Socket

可疑

Snyk

通过

权限和风险

external-service

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

安装前确认

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

来源信息

继续浏览同类 Skills