Validating performance budgets
Validate application performance against defined budgets to identify regressions early. Use when checking page load times, bundle sizes, or API response times against thresholds. Trigger with phrases like "validate performance budget", "check performance metrics", or "detect performance regression".From its SKILL.md
npx -y skills add jeremylongshore/claude-code-plugins-plus-skills --skill validating-performance-budgetsAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
What its file declares
Copied from the file, not written here
The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
4.3 KB, 661 tokens by cl100k_base, as published. Nobody here has run it
Performance Budget Validator
Validate page load times, bundle sizes, and API response times against predefined performance budgets to catch regressions before they reach production.
Overview
This skill allows Claude to automatically validate your application's performance against predefined budgets. It helps identify performance regressions and ensures your application maintains optimal performance characteristics.
How It Works
- Analyze Performance Metrics: Claude analyzes current performance metrics, such as page load times, bundle sizes, and API response times.
- Validate Against Budget: The plugin validates these metrics against predefined performance budget thresholds.
- Report Violations: If any metrics exceed the defined budget, the skill reports violations and provides details on the exceeded thresholds.
When to Use This Skill
This skill activates when you need to:
- Validate performance against predefined budgets.
- Identify performance regressions in your application.
- Integrate performance budget validation into your CI/CD pipeline.
Examples
Example 1: Preventing Performance Regressions
User request: "Validate performance budget for the homepage."
The skill will:
- Analyze the homepage's performance metrics (load time, bundle size).
- Compare these metrics against the defined budget.
- Report any violations, such as exceeding the load time budget.
Example 2: Integrating with CI/CD
User request: "Run performance budget validation as part of the build process."
The skill will:
- Execute the performance budget validation command.
- Check all defined performance metrics against their budgets.
- Report any violations that would cause the build to fail.
Best Practices
- Budget Definition: Define realistic and achievable performance budgets based on current application performance and user expectations.
- Metric Selection: Choose relevant performance metrics that directly impact user experience, such as page load times and API response times.
- CI/CD Integration: Integrate performance budget validation into your CI/CD pipeline to automatically detect and prevent performance regressions.
Integration
This skill can be integrated with other plugins that provide performance metrics, such as website speed test tools or API monitoring services. It can also be used in conjunction with alerting plugins to notify developers of performance budget violations.
Prerequisites
- Performance budget definitions in ${CLAUDE_SKILL_DIR}/performance-budgets.json
- Access to performance testing tools (Lighthouse, WebPageTest)
- Build output directory for bundle analysis
- Historical performance metrics for comparison
Instructions
- Load performance budget configuration
- Collect current performance metrics (load time, bundle size, API latency)
- Compare metrics against defined budget thresholds
- Identify budget violations and severity
- Generate detailed violation report
- Provide remediation recommendations
Output
- Performance budget validation report
- List of metrics exceeding budget thresholds
- Comparison with previous measurements
- Detailed breakdown by metric category
- Actionable recommendations for fixes
Error Handling
If budget validation fails:
- Verify budget configuration file exists
- Check performance testing tool availability
- Validate metric collection permissions
- Ensure network access to test endpoints
- Review budget threshold definitions
Resources
- Performance budget best practices
- Lighthouse performance scoring guide
- Bundle size optimization techniques
- CI/CD integration patterns for performance testing
What ships with it: 6 files
47.2 KB alongside SKILL.md, 3 of them executable
assets/
- README.md67 B
references/
- README.md71 B
scripts/
- create_budget.pyruns13.1 KB
- README.md446 B
- report_violation.pyruns17.6 KB
- validate_budget.pyruns16.0 KB
Gives 0 of the 12 instructions most performance cost skills give in 661 tokens
Counted across 797 of the 1,117 authors here whose files we hold, read 2026-09-06
- Check for product marketing context firstin 46 of 797, across 20 files
- Measure before optimizingin 31 of 797, across 25 files
- Profile first to identify the actual bottleneckin 23 of 797, across 22 files
- Verify your robots.txt allows AI crawlersin 21 of 797, across 12 files
- Import directly and avoid barrel filesin 19 of 797, across 15 files
- Spawn all runs in the same turnin 18 of 797, across 11 files
- Write a draft of the skillin 17 of 797, across 10 files
- Understand the user's intentin 17 of 797, across 10 files
- Use React.cache for per-request deduplicationin 16 of 797, across 11 files
- Profile before optimizingin 16 of 797, across 14 files
- Include specific numbers with sourcesin 15 of 797, across 8 files
- Add lazy loading to below-fold imagesin 15 of 797, across 10 files
Said here and by no other author read
- Load performance budget configuration
- Collect current performance metrics
- Compare metrics against budget thresholds
- Identify budget violations and severity
- Generate detailed violation report
- Provide remediation recommendations
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.