AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified Apache-2.0 Self-run

Cloudflare Pages Stale Assets

skill-jinning6-noosphere-cloudflare-pages-stale-assets · by JinNing6

Diagnose and fix Cloudflare Pages deployments where the live site still shows old CSS, JavaScript, native controls, untranslated text, or stale UI after a successful deploy. Use for static websites on Cloudflare Pages, custom domains, pages.dev previews, browser-cache disagreements, and "it deployed but I still see the old page" reports.

↗ Repository
— No reviews yet
0 installs
7 views
0.0% view→install

Install

$ agentstack add skill-jinning6-noosphere-cloudflare-pages-stale-assets

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • ✓ Prompt-injection patterns
  • ✓ Secret / credential exfiltration
  • ✓ Dangerous shell & filesystem operations
  • ✓ Untrusted network calls
  • ✓ Known-malicious package signatures

What it can access

  • ✓ Network access No
  • ✓ Filesystem access No
  • ✓ Shell / process execution No
  • ✓ Environment & secrets No
  • ✓ Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-jinning6-noosphere-cloudflare-pages-stale-assets)

Reliability & compatibility

✓ Security review passed
0 installs to date
— no reviews yet
● 26d ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Cloudflare Pages Stale Assets? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Cloudflare Pages Stale Assets

Use this before changing UI code again. First prove whether the failure is deployment, domain routing, edge/browser cache, or runtime JavaScript.

Workflow

  1. Confirm the repo state:
  • Read project agent rules first.
  • Check the current branch, latest commit, and dirty files.
  • Identify the exact generated/static output directory used by Pages.
  1. Compare every live hostname:
  • Fetch https://.pages.dev/, the apex custom domain, and www.
  • Add a cache-busting query to HTML, CSS, and JS URLs, for example ?codex_check=.
  • Record status, redirect target, ETag, CF-Cache-Status, Age, and whether the expected new code appears.
  1. Distinguish failure layers:
  • Deployment: latest commit is not in the live HTML.
  • Domain routing: pages.dev is current but custom domain is stale or SSL/route-broken.
  • Asset cache: HTML is current but references unversioned old CSS/JS.
  • Browser cache: network fetch is current but the user's browser still displays old assets.
  • Runtime: assets are current but console errors prevent enhancement.
  1. Fix at the owning layer:
  • If production branch is wrong, fix Pages branch control or redeploy the intended branch.
  • If custom domain differs, fix Pages custom domain binding and DNS before editing UI.
  • If stale CSS/JS is plausible, version static asset URLs in every HTML page, such as style.css?v= and language.js?v=.
  • If runtime fails, inspect console errors and fix the actual JavaScript exception.
  1. Verify after deploy:
  • Fetch live HTML and confirm it references versioned assets.
  • Fetch versioned CSS/JS and confirm they contain the expected selectors/functions.
  • Use a real browser when possible to confirm DOM enhancement, not only source text.
  • Tell the user whether they need a hard refresh; after versioned assets they usually should not.

Completion Standard

The latest live HTML is proven to reference the intended assets, all affected hostnames are checked or explicitly reported as unreachable, runtime errors are ruled out or fixed, and the final commit includes only task-scoped files.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Write a review

Versions

  • v0.1.0 Imported from the upstream source.

More in Cloud & Infrastructure