Agent skill

Web Quality Audit

by midudev in midudev/100cosas.dev

Comprehensive web quality audit covering performance, accessibility, SEO, and best practices.

MITAuto-check passedFrontend & Design

Install Web Quality Audit

skills CLI
$ npx skills add midudev/100cosas.dev --skill web-quality-audit -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install midudev/100cosas.dev web-quality-audit --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/midudev/100cosas.dev.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/web-quality-audit .claude/skills/web-quality-audit && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
web-quality-audit
GitHub stars
114
Used in
3 other repos
Token cost
~1.7k tokens
SKILL.md length
684 words
Files
2 (incl. scripts)
Skills in repo
3
Repo updated
First seen
Licence
MIT

At a glance

Comprehensive web quality audit covering performance, accessibility, SEO, and best practices.

  • Works in 4 steps: Analyze the provided code/project for… → Categorize findings by severity… → Provide specific, actionable… → …
  • Asked to audit my site
  • SKILL.md covers How it works, Audit categories, Severity levels and Audit output format, plus 2 more sections
  • Runs Shell scripts from its folder

What it does

Web Quality Audit is an agent skill from midudev/100cosas.dev. Comprehensive web quality audit covering performance, accessibility, SEO, and best practices. Use when asked to "audit my site", "review web quality", "run lighthouse audit", "check page quality", or "optimize my website".

Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including scripts (for example `scripts/analyze.sh`).

It sits in Frontend & Design, covering Web performance and Accessibility. The repository describes itself as: Aprende y mejora en programación con consejos de grandes referentes. The licence is MIT.

When your agent uses it

  • Asked to audit my site
  • Review web quality
  • Run lighthouse audit
  • Check page quality

Example prompts

  • “audit my site”
  • “review web quality”
  • “run lighthouse audit”
  • “/web-quality-audit”

Requirements

  • A Bash shell

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. Analyze the provided code/project for quality issues
  2. Categorize findings by severity (Critical, High, Medium, Low)
  3. Provide specific, actionable recommendations
  4. Include code examples for fixes

What it can do on your machine

Read from SKILL.md and the folder at commit d62cf52. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 1 file in scripts/ (Shell), which the agent can run.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Web Quality Audit loads about 1.7k tokens when it runs. Until then it costs about 60 tokens; SKILL.md has 684 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~60
When it runs · the whole SKILL.md, loaded when a task matches
~1.7k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from midudev/100cosas.dev at commit d62cf52, republished under its MIT licence (© midudev). 684 words, ~1,656 tokens.

Download SKILL.mdSave it as .claude/skills/web-quality-audit/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
web-quality-audit
description
Comprehensive web quality audit covering performance, accessibility, SEO, and best practices. Use when asked to "audit my site", "review web quality", "run lighthouse audit", "check page quality", or "optimize my website".
license
MIT
metadata.author
web-quality-skills
metadata.version
1.0

Web quality audit

Comprehensive quality review based on Google Lighthouse audits. Covers Performance, Accessibility, SEO, and Best Practices across 150+ checks.

How it works

  1. Analyze the provided code/project for quality issues
  2. Categorize findings by severity (Critical, High, Medium, Low)
  3. Provide specific, actionable recommendations
  4. Include code examples for fixes

Audit categories

Performance (40% of typical issues)

Core Web Vitals — Must pass for good page experience:

  • LCP (Largest Contentful Paint) < 2.5s. The largest visible element must render quickly. Optimize images, fonts, and server response time.
  • INP (Interaction to Next Paint) < 200ms. User interactions must feel instant. Reduce JavaScript execution time and break up long tasks.
  • CLS (Cumulative Layout Shift) < 0.1. Content must not jump around. Set explicit dimensions on images, embeds, and ads.

Resource Optimization:

  • Compress images. Use WebP/AVIF with fallbacks. Serve correctly sized images via srcset.
  • Minimize JavaScript. Remove unused code. Use code splitting. Defer non-critical scripts.
  • Optimize CSS. Extract critical CSS. Remove unused styles. Avoid @import.
  • Efficient fonts. Use font-display: swap. Preload critical fonts. Subset to needed characters.

Loading Strategy:

  • Preconnect to origins. Add <link rel="preconnect"> for third-party domains.
  • Preload critical assets. LCP images, fonts, and above-fold CSS.
  • Lazy load below-fold content. Images, iframes, and heavy components.
  • Cache effectively. Long cache TTLs for static assets. Immutable caching for hashed files.
Accessibility (30% of typical issues)

Perceivable:

  • Text alternatives. Every <img> has meaningful alt text. Decorative images use alt="".
  • Color contrast. Minimum 4.5:1 for normal text, 3:1 for large text (WCAG AA).
  • Don't rely on color alone. Use icons, patterns, or text alongside color indicators.
  • Captions and transcripts. Video has captions. Audio has transcripts.

Operable:

  • Keyboard accessible. All functionality available via keyboard. No keyboard traps.
  • Focus visible. Clear focus indicators on all interactive elements.
  • Skip links. Provide "Skip to main content" for keyboard users.
  • Sufficient time. Users can extend time limits. No auto-advancing content without controls.

Understandable:

  • Page language. Set lang attribute on <html>.
  • Consistent navigation. Same navigation structure across pages.
  • Error identification. Form errors clearly described and associated with fields.
  • Labels and instructions. All form inputs have associated labels.

Robust:

  • Valid HTML. No duplicate IDs. Properly nested elements.
  • ARIA used correctly. Prefer native elements. ARIA roles match behavior.
  • Name, role, value. Interactive elements have accessible names and correct roles.
Show full SKILL.md (311 more words)Show less
SEO (15% of typical issues)

Crawlability:

  • Valid robots.txt. Doesn't block important resources.
  • XML sitemap. Lists all important pages. Submitted to Search Console.
  • Canonical URLs. Prevent duplicate content issues.
  • No noindex on important pages. Check meta robots and headers.

On-Page SEO:

  • Unique title tags. 50-60 characters. Primary keyword included.
  • Meta descriptions. 150-160 characters. Compelling and unique.
  • Heading hierarchy. Single <h1>. Logical heading structure.
  • Descriptive link text. Not "click here" or "read more".

Technical SEO:

  • Mobile-friendly. Responsive design. Tap targets ≥ 48px.
  • HTTPS. Secure connection required.
  • Fast loading. Performance directly impacts ranking.
  • Structured data. JSON-LD for rich snippets (Article, Product, FAQ, etc.).
Best practices (15% of typical issues)

Security:

  • HTTPS everywhere. No mixed content. HSTS enabled.
  • No vulnerable libraries. Keep dependencies updated.
  • CSP headers. Content Security Policy to prevent XSS.
  • No exposed source maps. In production builds.

Modern Standards:

  • No deprecated APIs. Replace document.write, synchronous XHR, etc.
  • Valid doctype. Use <!DOCTYPE html>.
  • Charset declared. <meta charset="UTF-8"> as first element in <head>.
  • No browser errors. Clean console. No CORS issues.

UX Patterns:

  • No intrusive interstitials. Especially on mobile.
  • Clear permission requests. Only ask when needed, with context.
  • No misleading buttons. Buttons do what they say.

Severity levels

LevelDescriptionAction
CriticalSecurity vulnerabilities, complete failuresFix immediately
HighCore Web Vitals failures, major a11y barriersFix before launch
MediumPerformance opportunities, SEO improvementsFix within sprint
LowMinor optimizations, code qualityFix when convenient

Audit output format

When performing an audit, structure findings as:

markdown
## Audit results

### Critical issues (X found)
- **[Category]** Issue description. File: `path/to/file.js:123`
  - **Impact:** Why this matters
  - **Fix:** Specific code change or recommendation

### High priority (X found)
...

### Summary
- Performance: X issues (Y critical)
- Accessibility: X issues (Y critical)
- SEO: X issues
- Best Practices: X issues

### Recommended priority
1. First fix this because...
2. Then address...
3. Finally optimize...

Quick checklist

Before every deploy
  • Core Web Vitals passing
  • No accessibility errors (axe/Lighthouse)
  • No console errors
  • HTTPS working
  • Meta tags present
Weekly review
  • Check Search Console for issues
  • Review Core Web Vitals trends
  • Update dependencies
  • Test with screen reader
Monthly deep dive
  • Full Lighthouse audit
  • Performance profiling
  • Accessibility audit with real users
  • SEO keyword review

References

For detailed guidelines on specific areas:

© midudev, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file (scripts) in .agents/skills/web-quality-audit of midudev/100cosas.dev.

  • SKILL.md
  • scripts/analyze.sh

Open the folder on GitHubat commit d62cf52

Used in 3 other repositories

We found 3 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 3 other GitHub owners. This page covers the copy in midudev/100cosas.dev, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Web Quality Audit next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Web Quality Audit compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Web Quality Audit this skillmidudev/100cosas.dev1143 repos~1.7kAutomated safety check: PassMIT
Web Quality Auditaddyosmani/web-quality-skills2.9k—~2.6kAutomated safety check: PassMIT
Optimize Loadtextura-agency/next16-claude-starter132—~4.6kAutomated safety check: NotesUnlicense
Accessibilityericrisco/rsc-harness167—~3.4kAutomated safety check: PassMIT
Accessibility Checkmakifbaysal/tasktrooper109—~1.1kAutomated safety check: PassApache-2.0
Web Perfelithrar/dotfiles202—~721Automated safety check: PassMIT

Similar skills

  • Web Quality Audit

    addyosmani/web-quality-skills

    Run an evidence-led web quality audit covering performance, accessibility, SEO, best practices, and agentic browsing.

    2.9k GitHub stars~2.6k tokensUpdated 1 mo ago
    Frontend & DesignAuto-check passed
  • Optimize Load

    textura-agency/next16-claude-starter

    Get a page into Lighthouse's green zone on desktop and mobile, for people AND for the robot form crawlers get — build it, audit all four categories (Performance, Accessibility, Best Practices, SEO)…

    132 GitHub stars~4.6k tokensUpdated yesterday
    Frontend & DesignAuto-check: notes
  • Accessibility

    ericrisco/rsc-harness

    A skill your agent uses when making a web UI conform to WCAG 2.2 Level AA — axe-core or Lighthouse a11y violations, keyboard operability, focus management, ARIA roles/names/live regions, contrast…

    167 GitHub stars~3.4k tokensUpdated yesterday
    Frontend & DesignAuto-check passed
  • Accessibility Check

    makifbaysal/tasktrooper

    A skill your agent uses when a task changes any screen, form, dialog, menu or control - Lighthouse/axe scan of the changed screens, a keyboard walk, and the thresholds that fail a task

    109 GitHub stars~1.1k tokensUpdated yesterday
    Frontend & DesignAuto-check passed
  • Web Perf

    elithrar/dotfiles

    Diagnose page-load and interaction performance using browser traces, network evidence, and source code.

    202 GitHub stars~721 tokensUpdated yesterday
    Frontend & DesignAuto-check passed
  • Best Practices

    tech-leads-club/agent-skills

    Apply modern web development best practices for security, compatibility, and code quality.

    7k GitHub stars~3.2k tokensUpdated 18 days ago
    Frontend & DesignAuto-check passed

More from midudev/100cosas.dev

  • Performance

    midudev/100cosas.dev

    Optimize web performance for faster loading and better user experience.

    114 GitHub starsUsed in 6 repos~2.3k tokens
    Auto-check passed
  • Best Practices

    midudev/100cosas.dev

    Apply modern web development best practices for security, compatibility, and code quality.

    114 GitHub starsUsed in 3 repos~3k tokens
    Auto-check passed

Questions about Web Quality Audit

What does Web Quality Audit do?

Comprehensive web quality audit covering performance, accessibility, SEO, and best practices. dev. Comprehensive web quality audit covering performance, accessibility, SEO, and best practices.

When should I use Web Quality Audit?

Web Quality Audit fits situations like: asked to audit my site; review web quality; run lighthouse audit; check page quality.

How do I install Web Quality Audit in Claude Code?

Run `npx skills add midudev/100cosas.dev --skill web-quality-audit -a claude-code`. Or copy the skill folder (.agents/skills/web-quality-audit in midudev/100cosas.dev) into .claude/skills/web-quality-audit in your project. Claude Code loads it when a task matches its description.

How do I install Web Quality Audit in Codex?

Run `npx skills add midudev/100cosas.dev --skill web-quality-audit -a codex`. Or copy the skill folder (.agents/skills/web-quality-audit in midudev/100cosas.dev) into .agents/skills/web-quality-audit in your project. Codex loads it when a task matches its description.

Can I use Web Quality Audit in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add midudev/100cosas.dev --skill web-quality-audit -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/web-quality-audit, .gemini/skills/web-quality-audit, .github/skills/web-quality-audit and .opencode/skills/web-quality-audit in your project.

What does Web Quality Audit need to run?

Going by SKILL.md and its folder, Web Quality Audit needs a shell for the scripts in its folder. Our summary lists: A Bash shell.

Does Web Quality Audit access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Web Quality Audit safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Web Quality Audit use?

Web Quality Audit is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Web Quality Audit use?

About 1.7k tokens (SKILL.md is roughly 6.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Web Quality Audit?

Skills that share tags, products or a category with Web Quality Audit: Web Quality Audit (addyosmani/web-quality-skills, 2.9k stars), Optimize Load (textura-agency/next16-claude-starter, 132 stars), Accessibility (ericrisco/rsc-harness, 167 stars) and Accessibility Check (makifbaysal/tasktrooper, 109 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Web Quality Audit?

midudev (a GitHub user) maintains it in midudev/100cosas.dev, which has 114 GitHub stars. The repository holds 3 skills in this directory. The repository was last updated on September 28, 2026.

Source: midudev/100cosas.dev on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.