Web Quality Audit
CheckedHelps with web development, auditing as part of agent workflows workflows.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
- 1
Run this in your project
terminal$ npx skills add tech-leads-club/agent-skills --skill web-quality-audit -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
tech-leads-club
Taken from the source listing. We haven't verified who controls this account.
Install target
Live repository
Not pinned. Installing fetches whatever the repository holds at the time you run the command.
Automated safety checks
This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.
Declares what it does: passed
SKILL.md parses and declares a name and a description.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No undeclared network calls: passed
Makes no network calls.
Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.
No obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
No credential access: passed
Reads no keys, tokens, keychains or credential files.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
No pipe-to-shell installers: passed
No pipe-to-shell or download-and-run installers.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
Pinned to a commit: passed
Scanned tech-leads-club/agent-skills at 6df68d5202.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- 6df68d5202
- Scanned
- 2 files, 282 lines
About this skill
What it does
The Web Quality Audit skill enables an AI agent to perform comprehensive quality reviews of web development projects based on Google Lighthouse audits. It analyzes code and project structure, categorizes findings by severity (Critical, High, Medium, Low), and provides specific, actionable recommendations for improvement. The audit covers key areas including Performance, Accessibility, SEO, and Best Practices across over 150 checks.
When to use it
- When needing a comprehensive assessment of a web project's quality before launch or major updates.
- To identify and prioritize performance bottlenecks impacting user experience (e.g., slow LCP scores).
- To ensure accessibility compliance for users with disabilities.
- As part of automated workflows to maintain consistent code quality standards.
Key capabilities
- Performance Audit: Evaluates Core Web Vitals (LCP, INP, CLS) and resource optimization areas like image compression, JavaScript minimization, and CSS efficiency.
- Accessibility Audit: Checks for perceivable elements such as text alternatives for images and sufficient color contrast.
- Actionable Recommendations: Provides specific guidance and code examples to address identified issues.
- Severity Categorization: Classifies findings by severity (Critical, High, Medium, Low) to prioritize remediation efforts.
Example prompts
- "Audit the web project at [URL] for performance and accessibility issues."
- "Analyze this code snippet [code snippet] and identify any potential quality concerns related to SEO best practices."
- "Perform a full web quality audit of my project, focusing on Core Web Vitals improvements."
Tips & gotchas
- The skill relies on Google Lighthouse audits; ensure the target website or codebase is accessible for analysis.
- Performance issues often require more complex solutions than simple code changes; be prepared to investigate underlying infrastructure and design choices.
- Prioritize addressing "Critical" and "High" severity findings first, as these have the greatest impact on user experience and accessibility.