web-performance-audit
Audit web performance using Chrome DevTools MCP. Use when asked to audit, profile, debug, or optimize page load performance, Lighthouse scores, or site speed.
Install with Tessl CLI
npx tessl i github:warpdotdev/oz-skills --skill web-performance-audit93
Does it follow best practices?
Validation for skill structure
Discovery
N/ABased on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
Something went wrong
Implementation
92%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a high-quality skill with excellent actionability and workflow clarity. It provides concrete tool calls, specific thresholds, and a clear multi-phase process with validation checkpoints. The main weakness is that the codebase analysis section could be extracted to a separate reference file to improve progressive disclosure for this longer skill.
Suggestions
Consider extracting Phase 5 (Codebase Analysis) into a separate CODEBASE_ANALYSIS.md file and linking to it, keeping SKILL.md focused on the core MCP-based audit workflow
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, using tables for quick reference, avoiding explanations of concepts Claude already knows (like what Core Web Vitals are), and every section serves a clear purpose without padding. | 3 / 3 |
Actionability | Provides fully executable tool calls with exact syntax, specific thresholds for metrics, concrete examples of what to look for, and actionable recommendations like 'compress hero.png (450KB) to WebP' rather than vague guidance. | 3 / 3 |
Workflow Clarity | Clear 5-phase workflow with explicit checklist for tracking progress, troubleshooting steps for common failures, and logical sequencing from trace capture through analysis to codebase review with clear skip conditions. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections and tables, but the skill is fairly long (~200 lines) and could benefit from splitting detailed framework detection and codebase analysis into separate reference files rather than inline. | 2 / 3 |
Total | 11 / 12 Passed |
Validation
93%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 15 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata' field is not a dictionary | Warning |
Total | 15 / 16 Passed | |
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.