Content Brief
Ryze-AI-Adgent/open-seo-mcp-skills
SERP-driven content brief for a target keyword — what ranks, what to cover, headings, questions, internal links from your own data.
Reads existing brand DNA, keywords.csv, and prompts.csv, then produces a plan.csv — a strictly-schema'd content architecture telling the next pipeline step which pages to create, for which…
$ npx skills add onvoyage-ai/gtm-engineer-skills --skill geo-content-planning -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install onvoyage-ai/gtm-engineer-skills geo-content-planning --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/onvoyage-ai/gtm-engineer-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/geo-content-planning .claude/skills/geo-content-planning && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "geo-content-planning" agent skill from https://github.com/onvoyage-ai/gtm-engineer-skills/tree/main/geo-content-planning into .claude/skills/geo-content-planning/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "geo-content-planning", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/onvoyage-ai/gtm-engineer-skills/tree/main/geo-content-planningType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add onvoyage-ai/gtm-engineer-skills --skill geo-content-planning -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install onvoyage-ai/gtm-engineer-skills geo-content-planning --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/onvoyage-ai/gtm-engineer-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/geo-content-planning .agents/skills/geo-content-planning && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "geo-content-planning" agent skill from https://github.com/onvoyage-ai/gtm-engineer-skills/tree/main/geo-content-planning into .agents/skills/geo-content-planning/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "geo-content-planning", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add onvoyage-ai/gtm-engineer-skills --skill geo-content-planning -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install onvoyage-ai/gtm-engineer-skills geo-content-planning --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/onvoyage-ai/gtm-engineer-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/geo-content-planning .cursor/skills/geo-content-planning && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "geo-content-planning" agent skill from https://github.com/onvoyage-ai/gtm-engineer-skills/tree/main/geo-content-planning into .cursor/skills/geo-content-planning/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "geo-content-planning", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/onvoyage-ai/gtm-engineer-skills.git --path geo-content-planning--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add onvoyage-ai/gtm-engineer-skills --skill geo-content-planning -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install onvoyage-ai/gtm-engineer-skills geo-content-planning --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/onvoyage-ai/gtm-engineer-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/geo-content-planning .gemini/skills/geo-content-planning && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "geo-content-planning" agent skill from https://github.com/onvoyage-ai/gtm-engineer-skills/tree/main/geo-content-planning into .gemini/skills/geo-content-planning/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "geo-content-planning", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install onvoyage-ai/gtm-engineer-skills geo-content-planningInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add onvoyage-ai/gtm-engineer-skills --skill geo-content-planning -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/onvoyage-ai/gtm-engineer-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/geo-content-planning .github/skills/geo-content-planning && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "geo-content-planning" agent skill from https://github.com/onvoyage-ai/gtm-engineer-skills/tree/main/geo-content-planning into .github/skills/geo-content-planning/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "geo-content-planning", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add onvoyage-ai/gtm-engineer-skills --skill geo-content-planning -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install onvoyage-ai/gtm-engineer-skills geo-content-planning --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/onvoyage-ai/gtm-engineer-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/geo-content-planning .opencode/skills/geo-content-planning && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "geo-content-planning" agent skill from https://github.com/onvoyage-ai/gtm-engineer-skills/tree/main/geo-content-planning into .opencode/skills/geo-content-planning/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "geo-content-planning", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
geo-content-planningReads existing brand DNA, keywords.csv, and prompts.csv, then produces a plan.csv — a strictly-schema'd content architecture telling the next pipeline step which pages to create, for which…
Geo Content Planning is an agent skill from onvoyage-ai/gtm-engineer-skills. Reads existing brand DNA, keywords.csv, and prompts.csv, then produces a plan.csv — a strictly-schema'd content architecture telling the next pipeline step which pages to create, for which keyword/prompt clusters, and in what build order.
Its SKILL.md is about 1.9k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `plan.csv.schema.md`).
It sits in Marketing & SEO, covering Content strategy, AI search optimization and CSV and tabular files. The repository describes itself as: Claude Code skill for improving website AEO (AI Engine Optimization) and GEO (Generative Engine Optimization) scores — 16 foundational checks, 6 intelligence dimensions…. The licence is MIT.
8 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 3777930. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Geo Content Planning loads about 1.9k tokens when it runs. Until then it costs about 65 tokens; SKILL.md has 709 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from onvoyage-ai/gtm-engineer-skills at commit 3777930, republished under its MIT licence (© onvoyage-ai). 709 words, ~1,942 tokens.
.claude/skills/geo-content-planning/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.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.mdexactly. No prose, no code fences, no explanation. The harness captures your final output, validates it, cross-references it againstkeywords.csvandprompts.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, audiencekeywords.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.
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.
Do NOT create one page per prompt. Group closely related prompts + keywords into a single page. A good page covers:
keywords.csv)prompts.csv)Good page clusters:
money — high-intent category or solution page on the product itselfcomparison — best / vs / alternativesuse_case — specific audience or scenariotrust — pricing, worth-it, objections, FAQdefinition — what is X, how X worksproduct — 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-solvingcomparisons — best, vs, alternativeslearn — definitions, concepts, category educationblog — editorial, trend, time-basedPipe-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.
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.p1 — high business value, clear product-fit. At least one page in the plan must be P1.p2 — useful supporting contentp3 — lower-priority authority contentEmit at least 5 rows. A plan with fewer than 5 pages is not a plan.
p (from page_id). No prose, no fences.page_id,priority,page_type,section,subsection,title,url_slug,target_keywords,target_prompts,required_sections,why_it_matterstarget_keywords must appear in keywords.csv. Every prompt in target_prompts must appear in prompts.csv. The harness enforces this.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"page_id,priority,page_type,...priority=p1section=resources ⟹ subsection is filledsection ∈ {product, use_cases} ⟹ subsection is emptytarget_keywords entry exists in the keywords.csv you were giventarget_prompts entry exists in the prompts.csv you were given (write them lowercased without trailing ?)page_id or url_slugwhy_it_matters is concrete and ≥ 15 charsThen emit the CSV. Nothing else.
© onvoyage-ai, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 1 other file in geo-content-planning of onvoyage-ai/gtm-engineer-skills.
Open the folder on GitHubat commit 3777930
Geo Content Planning next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Geo Content Planning this skillonvoyage-ai/gtm-engineer-skills | 1.3k | — | ~1.9k | Automated safety check: Pass | MIT | |
| Content BriefRyze-AI-Adgent/open-seo-mcp-skills | 4.7k | — | ~610 | Automated safety check: Pass | MIT | |
| Geoyaojingang/GEOHub | 165 | — | ~364 | Automated safety check: Pass | AGPL-3.0 | |
| Blog StrategyAgriciDaniel/claude-blog | 2.3k | — | ~4.4k | Automated safety check: Pass | MIT | |
| SEO Aeo Content Clusterhenryalouf/ruflow | 157 | — | ~954 | Automated safety check: Pass | MIT | |
| SEO Geoeunomia-bpf/eunomia.dev | 236 | — | ~2.1k | Automated safety check: Pass | MIT |
Ryze-AI-Adgent/open-seo-mcp-skills
SERP-driven content brief for a target keyword — what ranks, what to cover, headings, questions, internal links from your own data.
yaojingang/GEOHub
Route GEO and generative engine optimization requests to an available GEOHub capability.
AgriciDaniel/claude-blog
Blog strategy development including topic cluster architecture with hub-and-spoke design, audience mapping, competitive landscape analysis, AI citation surface strategy across ChatGPT/Perplexity/AI…
henryalouf/ruflow
Builds a topical authority map with a pillar page, prioritised cluster articles, content types, internal link map, and content gap analysis.
eunomia-bpf/eunomia.dev
Technical-only page-level and site-level SEO/GEO checklist for eunomia.dev content.
rampstackco/claude-skills
How to author a content brief that actually guides a writer (human or AI) to produce a piece that ranks, converts, or both.
onvoyage-ai/gtm-engineer-skills
Audits a live website for AI-engine discoverability (AEO/GEO).
onvoyage-ai/gtm-engineer-skills
Researches a company from its URL and produces a Brand DNA file covering positioning, audience, competitors, voice, and messaging.
onvoyage-ai/gtm-engineer-skills
Finds high-value SEO and GEO keywords using web search, AI analysis, and optionally paid tools like Ahrefs or Semrush.
onvoyage-ai/gtm-engineer-skills
Verifies truthfulness, accuracy, and link integrity of content before publishing.
onvoyage-ai/gtm-engineer-skills
Finds free backlink and brand mention opportunities across Hacker News, Quora, GitHub, directories, and niche communities.
onvoyage-ai/gtm-engineer-skills
Takes existing content markdown files and builds production-final resource center pages on client websites using their existing tech stack and design system.
Reads existing brand DNA, keywords.csv, and prompts.csv, then produces a plan.csv — a strictly-schema'd content architecture telling the next pipeline step which pages to create, for which…. Geo Content Planning is an agent skill from onvoyage-ai/gtm-engineer-skills.csv — a strictly-schema'd content architecture telling the next pipeline step which pages to create, for which keyword/prompt clusters, and in what build order.
Geo Content Planning fits situations like: tasks that involve Content strategy; tasks that involve AI search optimization; tasks that involve CSV and tabular files.
Run `npx skills add onvoyage-ai/gtm-engineer-skills --skill geo-content-planning -a claude-code`. Or copy the skill folder (geo-content-planning in onvoyage-ai/gtm-engineer-skills) into .claude/skills/geo-content-planning in your project. Claude Code loads it when a task matches its description.
Run `npx skills add onvoyage-ai/gtm-engineer-skills --skill geo-content-planning -a codex`. Or copy the skill folder (geo-content-planning in onvoyage-ai/gtm-engineer-skills) into .agents/skills/geo-content-planning in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add onvoyage-ai/gtm-engineer-skills --skill geo-content-planning -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/geo-content-planning, .gemini/skills/geo-content-planning, .github/skills/geo-content-planning and .opencode/skills/geo-content-planning in your project.
SKILL.md names no scripts, command-line tools or credentials: Geo Content Planning is instructions for the agent only.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Geo Content Planning is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 1.9k tokens (SKILL.md is roughly 7.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Geo Content Planning: Content Brief (Ryze-AI-Adgent/open-seo-mcp-skills, 4.7k stars), Geo (yaojingang/GEOHub, 165 stars), Blog Strategy (AgriciDaniel/claude-blog, 2.3k stars) and SEO Aeo Content Cluster (henryalouf/ruflow, 157 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
onvoyage-ai (a GitHub organization) maintains it in onvoyage-ai/gtm-engineer-skills, which has 1,320 GitHub stars. The repository holds 12 skills in this directory. The repository was last updated on June 7, 2026.
Source: onvoyage-ai/gtm-engineer-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.