mcpbeat

Performance Budget Lab

thegoat395/performance-budget-lab

Use for website performance planning, Lighthouse/web-vitals checks, bundle/media/font budgets, Core Web Vitals triage, image/video optimization, animation performance, deployment readiness, and premium-site speed audits.

371 tokens
context cost
the whole folder, loaded on every use
2
files
instructions only
0
copies elsewhere
how many repositories repackaged it
115
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository 
npx skills add https://github.com/TheGoat395/Codex-Skills --skill performance-budget-lab

What comes with it

210 bytes besides the instruction
agents/openai.yaml

The instruction itself

4 sections, as written by the author

Performance Budget Lab

Use this skill to keep visually rich sites fast.

Budget Areas

  • JavaScript bundle size
  • route-level code splitting
  • image dimensions, formats, and lazy loading
  • video poster, preload, autoplay, and reduced-data behavior
  • font loading and fallback metrics
  • animation cost and scroll handlers
  • layout shift sources
  • server rendering/static rendering choices
  • caching and CDN behavior

Workflow

  • Identify stack and deployment target.
  • Inspect package dependencies and route structure.
  • Run available build/lint/test commands.
  • Run Lighthouse or browser performance checks when feasible.
  • Check Core Web Vitals risks: LCP, CLS, INP, TTFB.
  • Optimize media before adding more JS.
  • Prefer CSS and Motion for small interactions; reserve GSAP/R3F/video for clear value.
  • Report tradeoffs honestly when visual richness costs performance.

Output

Give:

  • current risks
  • recommended budgets
  • concrete fixes
  • commands run
  • remaining uncertainty

How to use it

Copy the folder

Take thegoat395/performance-budget-lab from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.