Skip to content
SkillModel-led1,072 tokens in use

geo-update

Updates an installed GEO-SEO toolkit to the latest upstream version, with a diff summary first and no local files deleted.

11,792 stars on the repository MIT Licensezubair-trabzada/geo-seo-claude · skills/geo-update
curl -fsSL https://raw.githubusercontent.com/zubair-trabzada/geo-seo-claude/main/install.sh | bash
View source

Install command as written in the repository's README

Skill label

measured from its files

What installing geo-update costs

44tokens idle
1,072tokens in use

Idle is what sits in context while the skill is installed. In use is its instructions, loaded when it runs. Counts are approximate, made offline with cl100k_base.

Model dependence Model-led

Script-ledMixedModel-led

Mostly instructions, so how well it works depends on the model that follows them.

This describes the skill's structure, how much of it is scripts. It does not say how well it works.

Touches

shelldeclared and detectednetworkdetectedwrites filesdeclared and detectedgitdetected

Declared tags come from the skill's frontmatter; detected ones from its scripts, its code blocks and the commands it names in inline code. This is detected, not audited.

How it scores

Quality

How well the skill is written, counted from its own files: its frontmatter, its steps, examples, stated output and constraints, its size and whether every file it ships is one it names.How we score it →
Good
  • Frontmatter8/15
  • Structure25/25
  • Examples9/15
  • Output10/15
  • Size15/15
  • Resources10/15

Security

Starts at 100 and loses points for each thing in the skill's files that a reader should look at first.How we score it →
Good
  • Runs shell commands−2

    does this on the machine, as the frontmatter declares

    SKILL.md, line 38
  • Runs git commands−5

    does this on the machine, and the frontmatter does not say so

    SKILL.md, line 39
  • Writes files−4

    does this on the machine, as the frontmatter declares

    SKILL.md, line 64
  • Reaches the network−10

    does this on the machine, and the frontmatter does not say so

    SKILL.md, line 102

Repository health

Pre-computed score based on development activity, maintenance, community, maturity, and trend momentum.How we score it →
Good
  • Development activity100
  • Maintenance52
  • Community68
  • Maturity32
  • Momentum40

geo-update keeps the GEO-SEO toolkit current. It checks that the toolkit is installed under ~/.claude, clones the upstream repository, compares it with the installed files, shows what is new or modified, and then copies the updated skills, agents, scripts, schema templates and hooks into place.

Files that no longer exist upstream are listed and left alone, settings files are never touched, and it reminds you to restart your session so the new skills load.

What You Get

  • A diff summary of new, modified and upstream-removed files before anything is copied
  • Updated main skill, sub-skills, agents, scripts, schema templates and hooks in your .claude folder
  • A refreshed Python dependency install when requirements.txt changed
  • A closing report with counts of new, modified and unchanged files
  • A list of locally kept files that upstream no longer ships

Common Use Cases

  • Pulling new audit checks after the GEO-SEO repository changes
  • Refreshing schema templates and scripts without reinstalling
  • Reviewing what changed upstream before accepting an update
  • Keeping several machines on the same toolkit version

What Makes It Unique

It is an update path built into the toolkit, so the skills can be refreshed from inside Claude Code. It shows the differences first, never deletes files you may have customized, leaves settings.json and settings.local.json alone, and treats a failed clone or failed dependency install as a reported error that stops or skips safely.

Under The Hood

The skill is written instructions for the agent with no scripts of its own. The agent uses the shell to create a temporary folder, runs git clone of the upstream GitHub repository over the network, compares folders with diff, and copies files with cp into skills, agents, scripts, schema and hooks folders under ~/.claude, marking scripts executable. If requirements.txt changed it runs pip install for the Python dependencies, which downloads packages. Then it deletes the temporary folder. You are shown the changes before it copies, and a failed clone stops the run before anything is modified.

Join founders building with open source

Opinionated takes, migration guides, cost-saving tips, and insights from the open source ecosystem.

Subscribe on SubstackJoin 750+ subscribers