site-readiness
Skill2 starsChanged 4 months agoMITView on GitHub
Run sandbox-aware readiness checks for a Portable Web Toolkit-managed Astro client site and produce structured next actions. Use before material site work, after scaffolding or configuration changes, during release preparation, or when project state is uncertain. Do not treat readiness findings as authorization to install, update, deploy, or mutate infrastructure.
- Reads credentials
1 other project uses a version of this.
Adopted by
Most recently taken up by
- XPOZpublic/geo-seo-agenttheir own version, first seen Aug 26, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- XPOZpublic/geo-seo-agent★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository15 other files it gives its agents.
- AGENTS.mdAGENTS.md
- Web_Toolkit/AGENTS.mdAGENTS.md
- brand-doctorSkill
- discovery-doctorSkill
- image-pipelineSkill
- instagram-cloneSkill
- pagespeed-diagnosticsSkill
- portable-web-toolkit-routerSkill
- portable-web-toolkitSkill
- site-maintenanceSkill
- site-onboardingSkill
- site-starterSkill
- toolkit-updateSkill
- vectorize-pipelineSkill
- wcag-auditorSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Run before material work when current readiness evidence is absent or stale.
- Very specific: line 50
Read nextSteps + recommendedFixes in JSON
- Distinctive: line 53
site-doctor: only when site is live
- Distinctive: line 57
toolkit-update: when comparison or migration is requested.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Site Readiness
Run before material work when current readiness evidence is absent or stale.
Preflight
Resolve the active client repository, read its applicable instructions, and preserve unrelated work. Confirm the toolkit link and site profile belong to this client before running commands.
Command
node ./Web_Toolkit/site_readiness/bin/site-readiness.mjs run --project-root . --site-profile ./<name>.site-profile.jsonShortcuts: npm run readiness | npm run readiness:fix
An ordinary readiness request may write its diagnostic reports but does not
apply project fixes. Do not use readiness:fix or any mutation flag without
separate authorization for the proposed fixes.
Flags
| Flag | Effect |
--apply-safe-fixes | Authorized project-init apply-safe (never overwrites) |
--install-deps | Separately authorize dependency installation |
--build | Run the repository-authorized build and create its artifacts |
--skip-network | Offline/sandbox — skip integration |
Modes (auto)
sandbox | local | full (network + CF .env)
Outputs
output/site-readiness-*.json— agents read this firstoutput/site-readiness-*.md— human summary- Exit: 0 pass, 2 warn, 1 fail
Workflow
- Run readiness
- Read
nextSteps+recommendedFixesin JSON - Propose fixes; apply only the authorized set, then re-run
- Then portable-web-toolkit for deploy
- site-doctor only when site is live
Record the toolkit version as context. A newer toolkit version is a separate finding, not permission to pull source or reinstall skills. Use toolkit-update when comparison or migration is requested.
Never auto-applied
Deploy, DNS, cf-agent --apply, cache purge, registrar.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.