agentleFS
Sign inStart free
ImYourBoyRoyImYourBoyRoy/Portable_Web_toolkit/skills/site-maintenance/SKILL.md

site-maintenance

Skill2 starsChanged 4 months agoMITView on GitHub

Run the Portable Web Toolkit healthy maintenance loop: package refresh, local cache purge, build/smoke, media/fonts/legal/cookies pass, staging then production deploy, remote cache purge and warm, PageSpeed, and safe fixes. Use checkpoints before deploy or Cloudflare --apply. Read HOW_TO.md.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Follow repository HOW_TO.md (full maintenance loop) and Web_Toolkit/OPERATIONS.md.

    line 8
  2. Distinctive:

    Update local agent environment if needed (ask before privileged installs).

    line 12
  3. Distinctive:

    Prefer staging before production.

    line 24
  4. Very specific:

    Prefer toolkit CLIs; record outcomes in client MEMORY.md.

    line 26

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Site Maintenance

Follow repository HOW_TO.md (full maintenance loop) and Web_Toolkit/OPERATIONS.md.

Default order (checkpoints)

  1. Update local agent environment if needed (ask before privileged installs).
  2. package-updater on client package.json (runs npx @astrojs/upgrade for Astro sites; TypeScript stays on ^6.x) → approve → npm install.
  3. Local cache purge → check → build → discovery-doctor.
  4. Media / fonts / legal / cookies (HOW_TO §8): prefer WebP/AVIF/SVG, self-hosted fonts, legal page, cookies notice when analytics are on.
  5. Local / staging smoke.
  6. Explicit OK → production deploy (headers-deploy write-deploy as required).
  7. Targeted remote cache purge (dry-run → apply) → warm key production URLs.
  8. PageSpeed both strategies → minimal CWV fix plan → approve → re-measure.

Rules

  1. Dry-run Cloudflare mutations before --apply.
  2. Prefer staging before production.
  3. Never commit secrets.
  4. Prefer toolkit CLIs; record outcomes in client MEMORY.md.
  5. Flag poorly rendered images; convert on-page JPG/PNG via image-pipeline when WebP/AVIF fits.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free