vitals-fixer

What This Skill Does

The vitals-fixer skill is a diagnostic and corrective agent designed to optimize web performance specifically targeting Google's Core Web Vitals metrics: Largest Contentful Paint (LCP), Interaction to Next Paint (INP), and Cumulative Layout Shift (CLS). Instead of providing generic documentation, the tool performs a static analysis of your source code and cross-references identified patterns with known performance anti-patterns. It detects common issues such as unoptimized image assets lacking explicit dimensions, render-blocking JavaScript dependencies, excessive DOM depth, and heavy main-thread blocking tasks. By providing actionable code suggestions, it transforms abstract audit results into concrete refactoring tasks for developers.

Installation

To integrate this skill into your environment, use the OpenClaw management utility. Run the following command in your terminal:

clawhub install openclaw/skills/skills/lxgicstudios/vitals-fixer

Ensure your local environment is running Node.js 18 or higher to ensure compatibility with the scanning engine. No global configuration files are required, as the tool functions as an ad-hoc runner using npx.

Use Cases

This skill is ideal for:

• Recovering SEO rankings after a drop caused by poor Google Search Console vitals reports.
• Preparing production applications for enterprise-grade Lighthouse audits.
• Debugging intermittent layout shift issues during development cycles.
• Training junior developers by providing real-time, context-aware performance feedback on pull requests.
• Automating performance regressions by integrating the check into CI/CD pipelines before deployment.

Example Prompts

1. "Run the vitals-fixer on the ./src directory and prioritize the LCP issues found in the hero section components."
2. "Analyze my current codebase using the URL https://myapp.com and generate a markdown report outlining the top 5 contributors to my poor CLS score."
3. "Scan the project and suggest specific code refactors to reduce heavy JavaScript execution blocking the main thread."

Tips & Limitations

For best results, always run the tool against production-ready builds rather than development servers, as asset bundling and minification affect metric accuracy significantly. Start by resolving LCP issues, as these yield the highest perceived performance gains. Note that while the tool offers precise code suggestions, it cannot account for third-party network latency or server-side response times outside your code repository. Always validate suggestions with a standard Lighthouse audit after applying patches to confirm regression-free performance improvements.