version: "1.0.0" name: geo-update description: Inspect the bundled GEO source provenance and compare it with upstream releases without modifying the installed SEO + GEO Suite. Use only when the user asks whether GEO components are current or requests an update assessment.

GEO Update Assessment

The GEO components are integrated into seo-geo-suite; do not overwrite them directly from the upstream repository because that would bypass the unified routing, runtime paths, and validation applied by this plugin.

Workflow

1. Read .codex-plugin/plugin.json and THIRD_PARTY_NOTICES.md from the

installed plugin root.

1. If the user asks for a current comparison, inspect the upstream

geo-seo-claude repository and compare versions or commits read-only.

1. Summarize new, changed, and removed upstream capabilities. Do not treat

upstream wording changes as functional changes without evidence.

1. Explain which integrated files would be affected and whether the unified

router, renamed scripts, templates, or license notices need adaptation.

1. Only update the plugin when the user explicitly asks to apply the assessed

update. Use the local plugin development and reinstall flow, then rerun all Skill and plugin validation.

Never write into ~/.claude, install dependencies globally, or replace the installed plugin from a cloned repository.