agentleFS
TheGoat395TheGoat395/Codex-Skills/skills/performance-audit-websites/SKILL.md

performance-audit-websites

Skill136 starsChanged 5 months agoMITView on GitHub

Diagnose measured runtime and Core Web Vitals.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is 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.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill to keep premium sites fast enough that visual ambition does not punish users.

    line 8
  2. Very specific:

    Read Performance Audit Websites Guide before claiming the site is ready.

    line 15

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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

Performance Audit Websites

Use this skill to keep premium sites fast enough that visual ambition does not punish users. Measure first and optimize the dominant constraint; do not apply framework folklore as proof.

Own measured diagnosis and implementation. Route pre-build numeric budgets, acceptance thresholds, and visual-richness policy to $performance-budget-lab.

Workflow

  1. Inspect the affected surface, relevant project scripts, target URL and available inspection tooling; reuse existing context.
  2. Read Performance Audit Websites Guide before claiming the site is ready. For React or Next.js implementation work, also read React and Next.js performance.
  3. Record a reproducible baseline and identify the dominant request, rendering, interaction or layout-shift cost. When optimization is authorized, change the measured bottleneck and compare under matched build/device/cache conditions.
  4. Fix issues when they are in scope; otherwise record exact evidence and remaining risk.
  5. Summarize commands, URLs, screenshots/checks, changed files, and what was not tested.

Separate field data, controlled lab data, source inspection, and inference. A Lighthouse score from one machine is not a field-performance guarantee; an optimized source pattern is not a measured user improvement.

Scoped execution

Apply the shared web contract once when execution crosses phases; reuse it if already read. Load only the specialist guidance relevant to the requested surface and deliverable.

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.