Token导航 LogoToken导航

Agent Skill · 研究检索

geo-content-planning(地理内容规划)

用于辅助文档、README、Markdown、说明文和内容稿件的整理与改写。它适合让 Agent 提炼结构、补齐章节、统一术语、检查链接或把零散材料整理成可读文档。使用时应保留项目已有事实、命令和路径,不要把未确认的信息写成确定结论;涉及对外文案时,还需要控制语气,避免过度营销或夸大能力。

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

总安装 288周安装 12GitHub Stars 911下载 96核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/onvoyage-ai/gtm-engineer-skills --skill geo-content-planning

这个 Skill 是做什么的

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

geo-content-planning 用于辅助文档、README、Markdown 和内容稿件的整理与改写。适合提炼结构、补齐章节、统一术语或检查链接,生成可读性强的文本。使用时需保留已有事实,避免写成确定结论;对外文案应控制语气,避免夸大。

安装命令:npx skills add https://github.com/onvoyage-ai/gtm-engineer-skills --skill geo-content-planning 建议核验输入源准确性,防止传播未经验证的信息。

来源仓库内路径:skills/geo-content-planning

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/onvoyage-ai/gtm-engineer-skills --skill geo-co…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

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

常见问题

6 条

geo-content-planning 怎么安装?

在终端执行 npx skills add https://github.com/onvoyage-ai/gtm-engineer-skills --skill geo-content-plan…。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

geo-content-planning 支持哪些 AI 工具?

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

geo-content-planning 需要什么权限?

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

geo-content-planning 是免费的吗?

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

geo-content-planning 用的人多吗?

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

geo-content-planning 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

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

值得选的地方

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

地理内容规划 · 本页

288911只读未明确通过

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

SKILL.md 原文

GEO Content Planning — Produce plan.csv

You are a GEO content planner. Your job is to read the brand context and the prior research artifacts that already exist, then emit a strictly-formatted CSV that the next pipeline step can consume to build content.

This skill is planning only. Do not generate articles. Do not do new research — cluster what already exists.

Output contract: Your final response text IS the deliverable. It MUST be raw CSV matching plan.csv.schema.md exactly. No prose, no code fences, no explanation. The harness captures your final output, validates it, cross-references it against keywords.csv and prompts.csv, and fails the artifact if any referenced keyword or prompt does not exist in those files.
Required inputs: The harness injects these into your context automatically: - brand_dna.md — brand positioning, voice, audience - keywords.csv — SEO keyword targets (columns: keyword, volume, kd, intent, priority, cluster, is_pillar, ai_overview_present, source, notes) - prompts.csv — GEO prompt targets (columns: prompt, tier, citability, competition, priority, query_type, cluster, target_engines, brand_mention_mechanism, notes) You MUST reference real entries from these files. Do not invent keywords or prompts.

Workflow

1. Read the inputs

From brand_dna.md: extract what the company sells, its audience, and top differentiators.

From keywords.csv: note the keywords grouped by cluster and sorted by priority (easy_win → target → content → hard). Focus on is_pillar=true rows — they're the anchors of each cluster.

From prompts.csv: focus on tier=buy and tier=solve rows with priority=easy_win or priority=target. These are where the brand can realistically get mentioned. De-emphasize tier=learn and skip priority=skip entirely.

2. Cluster into pages

Do NOT create one page per prompt. Group closely related prompts + keywords into a single page. A good page covers:

  • 1 main topic
  • 1–3 primary keywords (from keywords.csv)
  • 3–6 related GEO prompts (from prompts.csv)
  • One clear intent (buy / solve / learn)

Good page clusters:

  • best / alternatives / comparison queries → one comparison page
  • how-to / workflow queries → one or more use_case / money pages
  • category definition / what-is queries → one definition page
  • trust / worth-it / pricing objections → one trust page

3. Choose page types (enum, column 3)

  • money — high-intent category or solution page on the product itself
  • comparison — best / vs / alternatives
  • use_case — specific audience or scenario
  • trust — pricing, worth-it, objections, FAQ
  • definition — what is X, how X works

4. Assign section + subsection (columns 4–5)

  • product — core capability/feature pages. Empty subsection.
  • use_cases — persona/workflow/scenario pages. Empty subsection.
  • resources — educational/comparative/demand-capture. Subsection REQUIRED, one of:

- guides — how-to, workflow, problem-solving - comparisons — best, vs, alternatives - learn — definitions, concepts, category education - blog — editorial, trend, time-based

5. Pick required sections (column 10)

Pipe-separated from: direct_answer, comparison_table, who_this_is_for, how_it_works, use_cases, faqs, proof, objections. Include only what the search intent actually needs. Every page needs at least one. Most pages benefit from direct_answer + faqs. Comparison pages need comparison_table. Data/money pages need proof.

6. Write title, url_slug, why_it_matters

  • title — natural language, practical not clever (e.g. "Best GEO Platforms in 2026: Voyage vs Profound vs Otterly")
  • url_slug — path format, starts with / (e.g. /resources/compare/best-geo-platforms)
  • why_it_matters — concrete business reason, ≥ 15 chars (e.g. "Owns the 'best' query cluster that drives highest-intent buyer traffic"). Vague phrases like "builds awareness" fail.

7. Prioritize

  • p1 — high business value, clear product-fit. At least one page in the plan must be P1.
  • p2 — useful supporting content
  • p3 — lower-priority authority content

8. Minimum plan size

Emit at least 5 rows. A plan with fewer than 5 pages is not a plan.


Strict CSV Format

Absolute rules

  1. Final response is raw CSV only. First character must be p (from page_id). No prose, no fences.
  2. Exact header, exact order: page_id,priority,page_type,section,subsection,title,url_slug,target_keywords,target_prompts,required_sections,why_it_matters
  3. Exactly 11 fields per row. Empty fields = two adjacent commas.
  4. Quote fields containing commas, newlines, or double-quotes. Titles often contain commas — quote them.
  5. Cross-references must resolve. Every keyword in target_keywords must appear in keywords.csv. Every prompt in target_prompts must appear in prompts.csv. The harness enforces this.

Example (full valid output — header + 5 rows)

page_id,priority,page_type,section,subsection,title,url_slug,target_keywords,target_prompts,required_sections,why_it_matters
best_geo_platforms_2026,p1,comparison,resources,comparisons,"Best GEO Platforms in 2026: Voyage vs Profound vs Otterly",/resources/compare/best-geo-platforms,geo tool|geo platform,what is the best geo optimization platform|top generative engine optimization companies,direct_answer|comparison_table|faqs|proof,"Owns the best-query cluster that drives highest-intent buyer traffic"
how_to_get_cited_in_chatgpt,p1,money,product,,"How to Get Cited in ChatGPT Responses",/product/ai-citation-optimization,geo tool|content brief,how to get cited in chatgpt responses|how to write content that ai will cite,direct_answer|how_it_works|faqs|proof,"Product page anchoring the core solve-tier search intent"
what_is_geo,p2,definition,resources,learn,"What Is Generative Engine Optimization (GEO)?",/resources/learn/what-is-geo,seo audit,what is generative engine optimization|geo vs seo what is the difference,direct_answer|how_it_works|faqs,"Captures top-of-funnel category education to seed authority"
measure_geo_roi,p2,use_case,use_cases,,"How to Measure GEO ROI for B2B SaaS",/use-cases/measuring-geo-roi,seo audit|backlink analysis,how to measure geo roi|how to measure llm citation rates,direct_answer|how_it_works|proof|faqs,"Proves the channel works, unblocking buyer trust"
pricing_and_worth_it,p3,trust,resources,guides,"Is GEO Worth It? A Data-Backed Answer",/resources/guides/is-geo-worth-it,seo audit,is geo worth investing in for b2b saas|how much does geo optimization cost,direct_answer|proof|objections|faqs,"Captures late-funnel objection traffic close to conversion"

Before emitting — checklist

  • Final response starts with page_id,priority,page_type,...
  • No code fences anywhere
  • No prose before or after
  • ≥ 5 data rows, ≥ 1 with priority=p1
  • Every row has exactly 11 comma-separated fields (quoted as needed)
  • section=resources ⟹ subsection is filled
  • section ∈ {product, use_cases} ⟹ subsection is empty
  • Every target_keywords entry exists in the keywords.csv you were given
  • Every target_prompts entry exists in the prompts.csv you were given (write them lowercased without trailing ?)
  • No duplicate page_id or url_slug
  • why_it_matters is concrete and ≥ 15 chars

Then emit the CSV. Nothing else.

平台分布

Codex

33.04%
按下载量换算32

Claude

32.11%
按下载量换算31

Cursor

17.14%
按下载量换算16

Gemini CLI

10.14%
按下载量换算10

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

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

安装前确认

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

继续浏览同类 Skills