agentsclimarketplace

Site readiness

Skill ImYourBoyRoy/Portable_Web_toolkit/skills/site-readiness

Portable Astro + Cloudflare toolkit with versioned skills for Codex, Cursor, Claude, and Antigravity; readiness, deployment, discovery, and starter CLIs.

Install
npx -y skills add ImYourBoyRoy/Portable_Web_toolkit --skill site-readiness

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

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.

SKILL.md

2.1 KB, as published. Nobody here has run it

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

Shortcuts: 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

FlagEffect
--apply-safe-fixesAuthorized project-init apply-safe (never overwrites)
--install-depsSeparately authorize dependency installation
--buildRun the repository-authorized build and create its artifacts
--skip-networkOffline/sandbox — skip integration

Modes (auto)

sandbox | local | full (network + CF .env)

Outputs

  • output/site-readiness-*.jsonagents read this first
  • output/site-readiness-*.md — human summary
  • Exit: 0 pass, 2 warn, 1 fail

Workflow

  1. Run readiness
  2. Read nextSteps + recommendedFixes in JSON
  3. Propose fixes; apply only the authorized set, then re-run
  4. Then portable-web-toolkit for deploy
  5. 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.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.