Agent skill

Pagezero Upgrade

by pagezero-dev in pagezero-dev/pagezero

Upgrade a PageZERO-based project to the latest starter while keeping project-specific business logic and marketing content.

MITAuto-check: notesDevelopment

Install Pagezero Upgrade

skills CLI

$ npx skills add pagezero-dev/pagezero --skill pagezero-upgrade -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install pagezero-dev/pagezero pagezero-upgrade --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/pagezero-dev/pagezero.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/pagezero-upgrade .claude/skills/pagezero-upgrade && rm -rf skills-src

Use ~/.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/

Paste into Claude Code

Install the "pagezero-upgrade" agent skill from https://github.com/pagezero-dev/pagezero/tree/main/.agents/skills/pagezero-upgrade into .claude/skills/pagezero-upgrade/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pagezero-upgrade", 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

$skill-installer install https://github.com/pagezero-dev/pagezero/tree/main/.agents/skills/pagezero-upgrade

Type 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.

skills CLI

$ npx skills add pagezero-dev/pagezero --skill pagezero-upgrade -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install pagezero-dev/pagezero pagezero-upgrade --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/pagezero-dev/pagezero.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/pagezero-upgrade .agents/skills/pagezero-upgrade && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "pagezero-upgrade" agent skill from https://github.com/pagezero-dev/pagezero/tree/main/.agents/skills/pagezero-upgrade into .agents/skills/pagezero-upgrade/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pagezero-upgrade", 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.

skills CLI

$ npx skills add pagezero-dev/pagezero --skill pagezero-upgrade -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install pagezero-dev/pagezero pagezero-upgrade --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/pagezero-dev/pagezero.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/pagezero-upgrade .cursor/skills/pagezero-upgrade && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "pagezero-upgrade" agent skill from https://github.com/pagezero-dev/pagezero/tree/main/.agents/skills/pagezero-upgrade into .cursor/skills/pagezero-upgrade/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pagezero-upgrade", 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

$ gemini skills install https://github.com/pagezero-dev/pagezero.git --path .agents/skills/pagezero-upgrade

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add pagezero-dev/pagezero --skill pagezero-upgrade -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install pagezero-dev/pagezero pagezero-upgrade --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/pagezero-dev/pagezero.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/pagezero-upgrade .gemini/skills/pagezero-upgrade && rm -rf skills-src

Use ~/.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/

Paste into Gemini CLI

Install the "pagezero-upgrade" agent skill from https://github.com/pagezero-dev/pagezero/tree/main/.agents/skills/pagezero-upgrade into .gemini/skills/pagezero-upgrade/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pagezero-upgrade", 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.

GitHub CLI

$ gh skill install pagezero-dev/pagezero pagezero-upgrade

Installs 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).

skills CLI

$ npx skills add pagezero-dev/pagezero --skill pagezero-upgrade -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/pagezero-dev/pagezero.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/pagezero-upgrade .github/skills/pagezero-upgrade && rm -rf skills-src

Use ~/.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/

Paste into GitHub Copilot

Install the "pagezero-upgrade" agent skill from https://github.com/pagezero-dev/pagezero/tree/main/.agents/skills/pagezero-upgrade into .github/skills/pagezero-upgrade/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pagezero-upgrade", 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.

skills CLI

$ npx skills add pagezero-dev/pagezero --skill pagezero-upgrade -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install pagezero-dev/pagezero pagezero-upgrade --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/pagezero-dev/pagezero.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/pagezero-upgrade .opencode/skills/pagezero-upgrade && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "pagezero-upgrade" agent skill from https://github.com/pagezero-dev/pagezero/tree/main/.agents/skills/pagezero-upgrade into .opencode/skills/pagezero-upgrade/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pagezero-upgrade", 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.

Facts

Skill name: pagezero-upgrade
GitHub stars: 143
Token cost: ~1.6k tokens
SKILL.md length: 695 words
Files: 1
Skills in repo: 5
Repo updated: Oct 1, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Upgrade a PageZERO-based project to the latest starter while keeping project-specific business logic and marketing content.

Development work in your project
SKILL.md covers Hard rules and Workflow
Calls bun, git and bunx

What it does

Pagezero Upgrade is an agent skill from pagezero-dev/pagezero. Upgrade a PageZERO-based project to the latest starter while keeping project-specific business logic and marketing content. Invoke only via /pagezero-upgrade; do not apply from ambient context.

Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development. It works with Cloudflare Workers and Git. The repository describes itself as: Open source, Cloudflare-native web app starter for the AI era. The licence is MIT.

When your agent uses it

Development work in your project

Example prompts

“/pagezero-upgrade”

What it can do on your machine

Read from SKILL.md and the folder at commit 5619f1b. It shows what the files ask for, not the result of running them.

Tool permissions
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.
Runs code
Shell commands in SKILL.md call:
- bun
- git
- bunx
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git and bunx, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Pagezero Upgrade loads about 1.6k tokens when it runs. Until then it costs about 53 tokens; SKILL.md has 695 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~53
When it runs · the whole SKILL.md, loaded when a task matches: ~1.6k

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.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

NoteMentions a .env fileSKILL.md:23

- Do **not** commit `.env` or `.env.test`.

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.

SKILL.md

The full file from pagezero-dev/pagezero at commit 5619f1b, republished under its MIT licence (© pagezero-dev). 695 words, ~1,608 tokens.

Download SKILL.mdSave it as .claude/skills/pagezero-upgrade/SKILL.md (or your agent's skills folder).

name: pagezero-upgrade
description: Upgrade a PageZERO-based project to the latest starter while keeping project-specific business logic and marketing content. Invoke only via /pagezero-upgrade; do not apply from ambient context.
disable-model-invocation: true

PageZERO Upgrade

The project is based on the PageZERO starter. Run the official upgrade CLI (it overwrites files), then reconcile from a pre-upgrade snapshot.

If some ./apps/* are not used by this project, don't bring them from pagezero. If there is some marketing content specific to this project, leave it. If there is business logic specific to this project, leave it.

Do not assume a local starter checkout or a fixed PageZERO layout. Discover what belongs to this project from PRE_HEAD and git diff.

Hard rules

Do not add starter modules this project did not already use.
Do not run bun run setup:wrangler (resets live D1 IDs and related vars).
Do not apply migrations that belong only to dropped modules.
Do not commit .env or .env.test.
Do not commit unless the user asks.

Workflow

- [ ] 1. Clean tree; branch off main if needed (`chore/pagezero-upgrade`)
- [ ] 2. Snapshot PRE_HEAD and project identity
- [ ] 3. bunx pagezero@latest upgrade -y
- [ ] 4. Classify every change
- [ ] 5. Restore / drop starter / drop site / merge
- [ ] 6. bun install, generate:types, check, test, test:e2e
- [ ] 7. Summarize

Snapshot

PRE_HEAD=$(git rev-parse HEAD). Record (no secrets):

Directories under apps/ (used modules). Ignore root route/entry files.
wrangler.json identity: worker name, D1 names/IDs, project-specific env vars
package.json deps this project's code actually imports
Project-specific AGENTS.md rules and extra skills
Env key names this project already uses

Working tree must be clean. Confirm wrangler.json exists and rsync is available.

Upgrade

bash

bunx pagezero@latest upgrade -y

If it fails, stop. Site-only files the CLI does not delete should still be present; overwritten files need classification.

Classify

For each path in git status / git diff "$PRE_HEAD":

Class	When	Action
KEEP_STARTER	Shared infra/tooling the project did not customize	Leave the upgraded file
RESTORE_SITE	Copy, branding, assets, live config, unique site features	`git restore --source=$PRE_HEAD -- <path>`
DROP_STARTER	New starter module (and its routes, deps, schema, env, tests) this project did not use	Delete; do not register
DROP_SITE	Path from `PRE_HEAD` that was leftover starter structure; the new starter removed or replaced that approach	Delete (do not restore). Port unique project logic to the new location if any
MERGE	Starter mechanics and project logic in the same file	Two-way merge

When unsure between KEEP_STARTER and MERGE: MERGE. When unsure between DROP_SITE and RESTORE_SITE: RESTORE_SITE. Never KEEP_STARTER or DROP_SITE a file whose only real differences are this project's copy, URLs, branding, IDs, or product behavior.

Inspect with git diff "$PRE_HEAD" -- <path>:

Only versions, types, or imports → KEEP_STARTER (MERGE if the project also had extra imports)
Copy, URLs, IDs, or product behavior → RESTORE_SITE or MERGE
New file under an unused app → DROP_STARTER
New shared tooling/shell → KEEP_STARTER
Gone after upgrade, and it was unique product → RESTORE_SITE
Gone after upgrade, or still present but unused, and it was old starter layout the new tree no longer uses → DROP_SITE
Customization still needed but the starter moved the seam → MERGE into the new path, then DROP_SITE the old path

Placeholder starter copy left unchanged in PRE_HEAD can KEEP_STARTER. The CLI may not delete files the starter dropped — also scan PRE_HEAD paths that the upgrade never touched.

Show full SKILL.md (233 more words)Show less

Restore, drop, merge

Restore overwritten product files. If restore would throw away a starter API change in that same file, MERGE instead.

Drop starter every apps/<name>/ the upgrade added that was not in the snapshot, unless the user asked to adopt it. Also drop that module's routes, deps, schema/migrations, env keys, config, sample content, and e2e. Keep shared shell that every PageZERO app needs (app entry, router, core styles, and similar).

Drop site obsolete project paths that only existed because an older starter put them there. Do not resurrect files the new starter deleted unless they hold unique product logic. After dropping, remove dangling imports, routes, and tests.

Merge by comparing $PRE_HEAD with the working tree. Take starter mechanical changes (APIs, types, scripts, tooling, dependency versions). Keep this project's values and behavior. Typical merge surfaces: package manifest/lockfile, route table, wrangler identity vs new structural keys, Vite/test config, app config, AGENTS.md, env templates, schema barrels, CI. After merging package.json, regenerate the lockfile with bun install. Do not add deps, env, or config for dropped modules.

Verify

bash

bun install
bun run generate:types
bun run check:fix
bun run check
bun run test
bun run test:e2e

Run db:generate only if a kept feature schema changed. Fix leftover imports from dropped modules and tests that now assert starter placeholder copy or unused-module flows. Use local Playwright (test:e2e), not deployed smoke. Do not open a PR unless asked.

Summarize

Unused starter apps dropped, obsolete site paths dropped, files restored, files merged (starter vs project), remaining risks.

Files

Just SKILL.md in .agents/skills/pagezero-upgrade of pagezero-dev/pagezero.

Open the folder on GitHubat commit 5619f1b

Compare with similar skills

Pagezero Upgrade 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.

Pagezero Upgrade compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Pagezero Upgrade this skillpagezero-dev/pagezero	143	—	~1.6k	Automated safety check: Notes	MIT	6 days ago
Obsidian Plugin Release Noteshjinco/synch	257	—	~1.1k	Automated safety check: Pass	MIT	today
Product Surface Checkelliothux/open-compute	1.6k	—	~2.4k	Automated safety check: Pass	Apache-2.0	yesterday
Cloudflare Sandboxsecondsky/claude-skills	227	—	~4.5k	Automated safety check: Pass	MIT	9 days ago
Codflow Updatebighadj22/codflow	343	—	~6.2k	Automated safety check: Notes	Apache-2.0	yesterday
Finishing a Development Branchobra/superpowers	296k	5 repos	~1.9k	Automated safety check: Pass	MIT	today

Similar skills

Obsidian Plugin Release Notes
hjinco/synch
Ensure Synch Obsidian plugin release notes are checked and updated once per pull request, or before committing directly to main, when changes affect apps/obsidian-plugin, packages/sync-client, root…
257 GitHub stars~1.1k tokensUpdated today
DevelopmentAuto-check passed
Product Surface Check
elliothux/open-compute
Manually review changed open-compute behavior for drift across maintained user, operator, API, SDK, configuration, deployment, capability, CLI, Dashboard, and release surfaces.
1.6k GitHub stars~2.4k tokensUpdated yesterday
DevelopmentAuto-check passed
Cloudflare Sandbox
secondsky/claude-skills
Cloudflare Sandboxes SDK for secure code execution in Linux containers at edge.
227 GitHub stars~4.5k tokensUpdated 9 days ago
DevOps & CloudAuto-check passed
Codflow Update
bighadj22/codflow
Update runbook for a self-hosted CodFlow install — an AI agent following it fetches the latest code from the CodFlow GitHub repo, merges it into an EXISTING checkout, syncs the gitignored…
343 GitHub stars~6.2k tokensUpdated yesterday
DevOps & CloudAuto-check: notes
Finishing a Development Branch
obra/superpowers
Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.
296k GitHub starsUsed in 5 repos~1.9k tokens
DevelopmentAuto-check passed
Code Review Checklist
shareAI-lab/learn-claude-code
Reviews code against a five-part checklist covering security, correctness, performance, maintainability and testing, and reports findings in a fixed format.
78k GitHub starsUsed in 5 repos~1.1k tokens
DevelopmentAuto-check passed

Questions about Pagezero Upgrade

What does Pagezero Upgrade do?

Upgrade a PageZERO-based project to the latest starter while keeping project-specific business logic and marketing content. Pagezero Upgrade is an agent skill from pagezero-dev/pagezero. Upgrade a PageZERO-based project to the latest starter while keeping project-specific business logic and marketing content.

When should I use Pagezero Upgrade?

Pagezero Upgrade fits situations like: development work in your project.

How do I install Pagezero Upgrade in Claude Code?

Run `npx skills add pagezero-dev/pagezero --skill pagezero-upgrade -a claude-code`. Or copy the skill folder (.agents/skills/pagezero-upgrade in pagezero-dev/pagezero) into .claude/skills/pagezero-upgrade in your project. Claude Code loads it when a task matches its description.

How do I install Pagezero Upgrade in Codex?

Run `npx skills add pagezero-dev/pagezero --skill pagezero-upgrade -a codex`. Or copy the skill folder (.agents/skills/pagezero-upgrade in pagezero-dev/pagezero) into .agents/skills/pagezero-upgrade in your project. Codex loads it when a task matches its description.

Can I use Pagezero Upgrade in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add pagezero-dev/pagezero --skill pagezero-upgrade -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/pagezero-upgrade, .gemini/skills/pagezero-upgrade, .github/skills/pagezero-upgrade and .opencode/skills/pagezero-upgrade in your project.

What does Pagezero Upgrade need to run?

Going by SKILL.md and its folder, Pagezero Upgrade needs the command-line tools its instructions call (bun, git and bunx).

Does Pagezero Upgrade access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Pagezero Upgrade safe to install?

Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Pagezero Upgrade use?

Pagezero Upgrade is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Pagezero Upgrade use?

About 1.6k tokens (SKILL.md is roughly 6.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Pagezero Upgrade?

Skills that share tags, products or a category with Pagezero Upgrade: Obsidian Plugin Release Notes (hjinco/synch, 257 stars), Product Surface Check (elliothux/open-compute, 1.6k stars), Cloudflare Sandbox (secondsky/claude-skills, 227 stars) and Codflow Update (bighadj22/codflow, 343 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Pagezero Upgrade?

pagezero-dev (a GitHub organization) maintains it in pagezero-dev/pagezero, which has 143 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on October 1, 2026.

Source: pagezero-dev/pagezero on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Pagezero Upgrade

Install Pagezero Upgrade

Facts

At a glance

What it does

When your agent uses it

Example prompts

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

PageZERO Upgrade

Hard rules

Workflow

Snapshot

Upgrade

Classify

Restore, drop, merge

Verify

Summarize

Files

Compare with similar skills

Similar skills

Obsidian Plugin Release Notes

Product Surface Check

Cloudflare Sandbox

Codflow Update

Finishing a Development Branch

Code Review Checklist

More from pagezero-dev/pagezero

Create Component

Create PR

Merge PR

Change Theme

Questions about Pagezero Upgrade

Install Pagezero Upgrade

Facts

At a glance

What it does

When your agent uses it

Example prompts

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

PageZERO Upgrade

Hard rules

Workflow

Snapshot

Upgrade

Classify

Restore, drop, merge

Verify

Summarize

Files

Compare with similar skills

Similar skills

More from pagezero-dev/pagezero

Related

Questions about Pagezero Upgrade