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

geo-monitor地理监测器

Agent Skill

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

总安装

612

周安装

26

GitHub Stars

66

下载量

214
CodexClaudeCursorGemini CLI

安装说明

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

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

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

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

命令行安装

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

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

简介

geo-monitor 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中快速定位候选结果。

  • 适用于关键词搜索、任务场景匹配或来源线索梳理等研究检索场景。
  • 通过 npx skills add 命令从指定 GitHub 仓库安装并使用该技能。
  • 安装前需确认权限范围、维护状态及是否涉及联网、命令执行或文件读写操作。
  • 适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

SKILL.md

/dm:geo-monitor

Purpose

Monitor and track brand visibility across generative AI engines. Systematically test how AI platforms respond to queries relevant to the brand, score visibility using a structured rubric, track changes over time, and identify opportunities to improve AI presence. This command provides a repeatable, quantitative framework for understanding where and how the brand appears (or fails to appear) in AI-generated responses — giving marketers the data they need to optimize for the emerging generative engine optimization (GEO) channel. Supports baselining, trend tracking, competitive benchmarking, and narrative alignment checks across all major AI platforms.

Input Required

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

  • Target queries to test: Organized by intent type — brand queries ("What is [brand]?"), product queries ("[brand] [product] features"), comparison queries ("[brand] vs [competitor]"), and category queries ("best [category] tools"). Minimum 5 queries recommended for meaningful scoring. If not provided, the command will generate a default query portfolio based on the brand profile
  • AI platforms to monitor: ChatGPT, Perplexity, Gemini, AI Overviews, and Copilot — default is all five. The user can narrow to specific platforms if they only care about certain engines or have limited testing capacity
  • Monitoring frequency: weekly or monthly — determines how often the brand should be re-tested and how trend data is bucketed. Weekly is recommended for active optimization campaigns, monthly for steady-state monitoring
  • Competitor brands to benchmark against (optional): One or more competitor brand names to test with the same query portfolio — enables side-by-side visibility scoring to understand relative AI presence. If omitted, the report focuses solely on the user's brand without competitive context

Process

  1. Load brand context: Read ~/.claude-marketing/brands/_active-brand.json for the active slug, then load ~/.claude-marketing/brands/{slug}/profile.json. Extract brand name, product names, category, key differentiators, and desired positioning to inform query portfolio and narrative alignment scoring. Also check for guidelines at ~/.claude-marketing/brands/{slug}/guidelines/_manifest.json — if present, load brand voice and messaging constraints. If no brand exists, ask: "Set up a brand first (/dm:brand-setup)?" — or proceed with defaults.
  2. Define query portfolio: Organize target queries by intent type — informational (what is, how does), navigational (brand-specific), transactional (buy, pricing, sign up), and comparison (vs, alternatives, best). If the user provided queries, classify them into these buckets. If not, generate a balanced portfolio of 10-20 queries from the brand profile covering all four intent types. Each query is tagged with its type for segmented scoring.
  3. Test each query on each platform: For every query-platform combination, record the AI response and score brand visibility using the rubric — cited with link (10 points: brand is mentioned by name and a direct link to the brand's website or content is provided), mentioned by name (7 points: brand is explicitly named in the response but no link), concept referenced without attribution (3 points: brand's product, feature, or approach is described but the brand itself is not named), absent (0 points: brand does not appear in any form), misrepresented (-5 points: brand is mentioned but with incorrect, outdated, or damaging information). Record the full response text for narrative analysis.
  4. Record results: Store all query-platform-score data via geo-tracker.py audit-visibility with timestamp, brand slug, query text, platform, score, response excerpt, and any flags for misrepresentation or drift.
  5. Compare to baseline: If previous monitoring data exists, run geo-tracker.py diff to compare current scores against the most recent previous check and the original baseline. Identify per-query and per-platform improvements (score increases), declines (score decreases), new appearances (went from absent to visible), lost appearances (went from visible to absent), and new opportunities (queries where competitors appear but the brand does not).
  6. Calculate visibility scores: Compute per-platform visibility scores (average of all query scores on that platform, scaled 0-100), per-intent-type scores (how visible is the brand for informational vs transactional queries), and an overall GEO health score (weighted average across all platforms and query types). If competitors were provided, calculate the same scores for each competitor to enable ranking.
  7. Assess narrative alignment: For queries where the brand appears, compare what the AI says against the desired brand positioning from the brand profile. Flag narrative drift (AI describes the brand differently than intended positioning), outdated information (AI cites old features, pricing, or leadership), missing key attributes (AI omits core differentiators), and misrepresentation (AI states something factually incorrect about the brand).
  8. Generate recommendations: Based on weak spots, produce a prioritized list of actions to improve AI visibility — content to create or update for better citation, structured data to add, entity consistency to fix (cross-reference with /dm:entity-audit), narrative corrections needed, and platforms where investment in visibility would have the highest impact.

Output

A comprehensive AI visibility monitoring report containing:

  • AI visibility scorecard: Per-platform scores (ChatGPT, Perplexity, Gemini, AI Overviews, Copilot) and overall GEO health score, scaled 0-100, with letter grade (A-F) and trend indicator vs previous check
  • Query-level results matrix: Every query-platform combination with score, response excerpt, and flags — sortable by platform, intent type, or score
  • Trend report: Score changes vs baseline and vs previous check — per-platform and overall, with sparkline indicators for directional trends and specific queries that improved or declined
  • Narrative alignment assessment: Per-platform summary of how well AI responses match desired brand positioning, with specific drift flags, outdated information callouts, and missing attribute gaps
  • Competitive benchmark: If competitors were provided — side-by-side visibility scores, queries where competitors outperform the brand, and narrative territory each brand occupies in AI responses
  • Top opportunities for improvement: Queries and platforms where the brand is absent or underrepresented but competitors are visible, or where high-intent queries return no brand presence
  • Recommended actions ranked by impact: Prioritized list of specific actions — content creation, structured data updates, entity fixes, citation building — with estimated impact on visibility scores and effort level
  • Execution log entry: Timestamped record with query count, platform count, overall score, trend direction, and key flags for audit trail

Agents Used

  • seo-specialist — AI visibility analysis across generative engines, query portfolio design by intent type, visibility scoring with the citation-mention-absent-misrepresentation rubric, narrative alignment assessment against brand positioning, citation building recommendations, structured data optimization for AI discoverability, and prioritized action plans for improving GEO health scores
  • performance-monitor-agent — Trend tracking across monitoring periods with baseline comparison, per-platform and per-query score change detection, threshold alerting for significant visibility drops or gains, competitive score tracking over time, and GEO health score history maintenance for long-term trend analysis

适合场景

01

用户想查找某类 Agent Skill 时

02

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

03

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

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

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

能力 4

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

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

平台分布

Codex

33.57%
按下载量换算72

Claude

30.53%
按下载量换算65

Cursor

19.11%
按下载量换算41

Gemini CLI

8.78%
按下载量换算19

安全审计

Gen Agent Trust Hub

可疑

Socket

可疑

Snyk

可疑

权限和风险

只读

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

安装前确认

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

来源信息

继续浏览同类 Skills