Skill Detail

Run AEO and GEO marketing workflows with GTM Engineer Skills

Install GTM Engineer Skills so Codex or Claude Code can research a brand, plan SEO/GEO content, audit AEO readiness, and produce reviewable marketing artifacts.

Content Writing & SEOMulti-Framework
Content Writing & SEO Multi-Framework Security Reviewed
⭐ 1.3k GitHub stars
COPY SKILL INSTRUCTIONS (OPTIONAL)
npx skills add agentskillexchange/skills --skill run-aeo-and-geo-marketing-workflows-with-gtm-engineer-skills Copy
Uses the third-party skills CLI, not an ASE-owned installer. Check your agent’s compatibility. This copies instructions; complete the upstream tool setup below separately.
At a glance
Tools required
Codex or Claude Code with local Agent Skill folders; optional Node.js for included scripts
Install & setup
Clone https://github.com/onvoyage-ai/gtm-engineer-skills, then symlink the desired skill folders such as research-brand, research-keywords, geo-content-planning, or audit-website-aeo into ~/.codex/skills or ~/.claude/skills.
Author
onvoyage-ai
Publisher
Organization
Last updated
Oct 12, 2026
Quick brief

Use GTM Engineer Skills when an operator wants a coding agent to run a structured growth workflow that produces files: brand research, keyword clusters, GEO prompt targets, content architecture, AEO audit reports, resource pages, or code-level AI discoverability fixes. The boundary is the skill pipeline and its reviewable artifacts; it is not a generic marketing platform or a loose prompt collection.

How it works

What this skill actually does

Inputs and prerequisites: Codex or Claude Code with local Agent Skill folders; optional Node.js for included scripts.

Setup notes: Clone https://github.com/onvoyage-ai/gtm-engineer-skills , then symlink the desired skill folders such as research-brand , research-keywords , geo-content-planning , or audit-website-aeo into ~/.codex/skills or ~/.claude/skills .

Source and verification boundary: use https://github.com/onvoyage-ai/gtm-engineer-skills as the canonical reference before running the workflow; keep commands, API calls, CLI usage, and generated outputs reviewable against that upstream source.

Framework fit: publish this as a Multi-Framework workflow only when the operator can invoke the documented toolchain directly, rather than treating the upstream project as a generic product listing.