Repository navigation
/all-deploy now covers web pages, not just apps, APIs and agents.
The most common question this skill got was the one it couldn't answer: "I have a folder with index.html in it — how do I put it on the internet?" That person usually has no git repo, no remote, no package.json and no terminal. v0.1.0 didn't just lack a path for them — it actively bounced them, with two criticals that were both wrong:
gitignore.missing .gitignore is missing.
git.dirty Tracked files have uncommitted changes (0 file(s)).
The second one was a bug: in a folder that isn't a git repo, git diff-index exits 128, and only FileNotFoundError was being caught. v0.2.0 fixes that, and builds a first-class static path around it.
Static sites
A new project class, detected in a Phase 0.0 that runs before the prerequisites — the ordering was what did the bouncing. A static site needs no git repo and no remote (except on GitHub Pages and Render). Detection stays narrow: any app manifest keeps a project on the app pipeline, so a Vite or Next repo — which also has an index.html — behaves exactly as before.
scripts/static_check.py — 14 checks aimed at what breaks a page after it goes live:
| Check | Why it matters |
|---|---|
static.entry.missing |
Hosts serve index.html exactly. mi-pagina.html 404s at the site root |
static.asset.case-mismatch |
imagenes/foto.png when the file is Imagenes/Foto.PNG loads on macOS and 404s on every Linux host. The images vanish and no log explains why |
static.path.absolute-local |
file:///Users/... — blank for everyone but you |
static.env-file.in-publish-dir |
A .env in the upload folder is downloadable at /.env the moment the site is live |
static.secret.client-exposed |
A private repo doesn't help: a static host serves what you give it |
static.nojekyll.missing |
On GitHub Pages, a _folder/ without .nojekyll makes every stylesheet silently 404 |
Plus warnings for broken references, oversized images, total site size, and a missing <title> / description / Open Graph block — without which sharing the link on WhatsApp shows a blank card that reads as broken.
The capitalisation check resolves every reference against a case-folded index of real on-disk names, not Path.exists() — which on macOS returns True for the wrong spelling and would make the check silently useless for exactly the people who need it.
Publishable keys (pk_live_, referrer-restricted Google Maps) only warn. They're designed to be public, and blocking them would train you to ignore the audit.
Four new free targets
- Cloudflare Pages — the default pick for a static site
- Netlify — including Drop, and the credit budget that pauses your site
- GitHub Pages — branch-based, which is what GitHub recommends for plain HTML
- Render — with its bandwidth reality stated up front
Plus a static path and the Hobby commercial-use terms on the existing Vercel playbook.
The free-hosting question nobody asks
Before ranking static hosts, the skill asks one thing: is anyone being paid in connection with this page?
It matters more than any technical comparison. Vercel's Fair Use Guidelines count "receiving payment to create, update, or host the site" as commercial usage — so a client's brochure page is out on Hobby even if it sells nothing, carries no ads and takes no payments. GitHub Pages bars sites "primarily directed at facilitating commercial transactions." Cloudflare Pages, Netlify and Render have no such restriction.
Two more things worth knowing, both quoted rather than summarised in references/static-hosting.md:
- Netlify's free plan is a 300-credit monthly budget. A production deploy costs 15, and when it runs out the site is paused with a "Site not available" page.
- Render's free static bandwidth is now 5 GB/month, down from 100 GB, then $0.15/GB.
And the part every guide glosses over: the hosting is free on all five, the domain never is — around $10–15/year, and none of them include one. references/custom-domain.md has the DNS records per host, apex vs www, and what to expect while the certificate is issued.
publish-website — the no-terminal companion
A separate, self-contained skill for the same job aimed at someone with no terminal, no GitHub account and no budget. Browser steps by default; commands only if you want them. Install it in Cowork from publish-website.plugin below, or drop it into ~/.claude/skills/.
Its copies of the shared files are generated by scripts/sync_cowork_plugin.py, and CI fails if they drift.
Also in this release
- Hard Rule 2 gains a clause. On one-shot static targets with no preview environment — GitHub Pages, a browser upload — the green artifact is a local
python3 -m http.serverrun of the exact publish directory. The gate stays mandatory; only where it's served changes. - Documented where preview → prod doesn't hold, including that Vercel's first deploy of a new project is always production even without
--prod. - Two audit bugs fixed — the false
git.dirty, andcheck_port_bindingreading_tracked_files()instead of_scannable_files(), so it silently no-opped without git. SKILL.mddescription was at 1003 of 1024 characters with no room for static triggers. Rewritten to 909 by moving the auto/step-by-step explanation into the body.validate_skill.pynow enforces the 1024 cap it never checked, and warns at 950.- Tests 15 → 35. CI also exercises the static profile on Linux, where the filesystem is case-sensitive — the opposite of the Mac most contributors use, which is the whole point of the capitalisation check.
Install
git clone https://github.com/Hainrixz/all-deploy.git ~/.claude/skills/all-deployUpdating from v0.1.0:
cd ~/.claude/skills/all-deploy && git pullOr download all-deploy.skill below and install it via your Claude Code skill manager. For the companion skill, download publish-website.plugin and install it from the Cowork desktop app.
Not verified
The commands in the four new target playbooks come from each provider's current documentation, but no end-to-end deploy was run against a live account for this release. If a command has drifted, open an issue — there's a template for it.
Four provider facts are explicitly marked as unconfirmed in the playbooks: Cloudflare publishes no bandwidth number for Pages; there is no formal deprecation notice for wrangler pages publish (it's simply absent from current docs); two Netlify doc pages disagree on whether an unclaimed Drop site is publicly reachable; and Render's CLI is not documented as being able to create a static site.
Requirements
macOS or Linux. Windows users should install under WSL2. For a static site, no CLI is required at all — every static target except Render has a complete browser route.
License
MIT.