agentleFS
Sign inStart free
ImYourBoyRoyImYourBoyRoy/Portable_Web_toolkit/skills/pagespeed-diagnostics/SKILL.md

pagespeed-diagnostics

Skill2 starsChanged 4 months agoMITView on GitHub

Run Portable Web Toolkit PageSpeed Insights diagnostics (Google PSI) for toolkit-managed sites. Use when measuring Core Web Vitals or PSI categories after deploy or during maintenance. Requires GOOGLE_PAGESPEED_API_KEY in the client .env.

  • Reads credentials

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Prefer measuring after remote cache warm (cold edge skews scores).

    line 30

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

PageSpeed Diagnostics

Thin skill for Google PageSpeed Insights via the toolkit CLI.

Prerequisites

  • Client .env has GOOGLE_PAGESPEED_API_KEY (section A).
  • *.site-profile.json and linked Web_Toolkit/.

Commands

node ./Web_Toolkit/pagespeed_diagnostics/bin/pagespeed-diagnostics.mjs run \
  --site-profile ./<site>.site-profile.json --strategy both

# Agent-friendly batch / regression
node ./Web_Toolkit/pagespeed_diagnostics/bin/pagespeed-diagnostics.mjs agent-batch \
  --site-profile ./<site>.site-profile.json --routes core --strategy mobile
node ./Web_Toolkit/pagespeed_diagnostics/bin/pagespeed-diagnostics.mjs agent-diff \
  --site-profile ./<site>.site-profile.json

Rules

  1. Prefer measuring after remote cache warm (cold edge skews scores).
  2. Summarize CWV + top opportunities; propose a minimal fix plan before editing.
  3. 100/100/100/100 is a target — do not break brand, forms, or a11y chasing scores.

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