asale-ai/seo-geo-skill / skills/geo-update
geo-update
FlaggedUpdate the installed SEO + GEO skills and the seogeo CLI to the latest release. Reports the installed version, the latest published version, what changed, and reinstalls the skill set across every detected agent tool. Use when the user says "update geo", "update skills", "upgrade seogeo", "aggiorna", or asks whether a newer version exists.
Update the SEO + GEO toolkit
The skills and the seogeo binary version together. Updating means
upgrading the binary, then reinstalling the skills that ship inside it.
Step 1 — Report the current state
seogeo --version
seogeo install --list --json
install --list prints every supported agent tool, whether it is detected
on this machine, and where its skills live. Show the user the installed
version and the detected targets before changing anything.
If seogeo is not found, the toolkit is not installed. Point the user at
the install command rather than trying to repair the installation:
npx -y @asale/seogeo --version
The seo-geo-skill skill walks a first install properly, including the
no-Node route.
Step 2 — Check for a newer release
curl -fsSL https://api.github.com/repos/asale-ai/seo-geo-skill/releases/latest \
| grep '"tag_name"'
Compare against seogeo --version. If they match, tell the user they are
current and stop — do not reinstall for no reason.
Step 3 — Upgrade the binary
Upgrade by the same route the user installed by. Both are idempotent and replace the binary in place.
Installed from npm:
npm install -g @asale/seogeo@latest
npx -y @asale/seogeo@latest runs the newest release without installing
anything, which is the quicker check when the user only wants the new version
once.
Installed from the shell script:
curl -fsSL https://raw.githubusercontent.com/asale-ai/seo-geo-skill/main/install.sh | sh
irm https://raw.githubusercontent.com/asale-ai/seo-geo-skill/main/install.ps1 | iex
Every route verifies the release checksum before installing. If verification fails it aborts without touching the existing binary — report the failure verbatim and stop.
Step 4 — Reinstall the skills
The new binary carries the new skills:
seogeo install --target all
This writes to every agent tool detected on the machine (Claude Code, Codex CLI, Gemini CLI, OpenCode, and any AGENTS.md-based agent) and skips the ones that are not present. To target one tool:
seogeo install --target claude
seogeo install --target codex
Preview without writing:
seogeo install --target all --dry-run --json
Step 5 — Verify
seogeo --version
seogeo commands --json | head -20
seogeo install --list
Confirm the version advanced and that the skill count matches what
install --list reports. Tell the user which tools were updated and remind
them that Claude Code picks up new skills on the next session start.
What is preserved
Updating never touches user state. These survive an upgrade:
| State | Location |
|---|---|
| Drift baselines | ~/.cache/seogeo/drift/baselines.db |
| CRM prospects | <data dir>/seogeo/prospects.json |
| DataForSEO cost ledger | <data dir>/seogeo/dataforseo-costs.json |
| Google API config | ~/.config/seogeo/google-api.json |
| Backlink API config | ~/.config/seogeo/backlinks-api.json |
Skill files are overwritten. If the user edited a bundled skill, tell them to copy it to a new name before updating.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |