CtrlK
BlogDocsLog inGet started
Tessl Logo

web-quality-audit

Comprehensive web quality audit covering performance, accessibility, SEO, and best practices in a single review. Use when asked to "audit my site", "review web quality", "run lighthouse audit", "check page quality", or "optimize my website" across multiple areas at once. Orchestrates specialized skills for depth. Do NOT use for single-area audits — prefer core-web-vitals, web-accessibility, seo, or web-best-practices for focused work.

55

Quality

62%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./packages/skills-catalog/skills/(quality)/web-quality-audit/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

35%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is well-organized as a checklist and provides a useful severity scheme and output template, but it is verbose with web-quality knowledge Claude already has and lacks executable audit guidance — notably, it never references the bundled scripts/analyze.sh. Tightening the inline explanations and wiring in the script would materially improve it.

Suggestions

Trim the per-check explanations that restate common knowledge (LCP/INP/CLS thresholds, WCAG ratios, meta-description lengths); keep them as a terse checklist and delegate depth to the referenced sibling skills.

Reference and invoke scripts/analyze.sh from the 'How it works' section so Claude has an executable first step instead of only 'Analyze the provided code/project'.

Move the bulk of the 150+ inline category checks into a reference file (e.g. references/checks.md) and keep SKILL.md as a concise overview pointing to it, improving progressive disclosure.

DimensionReasoningScore

Conciseness

The body extensively restates well-known Lighthouse/WCAG knowledge Claude already has (e.g. 'LCP < 2.5s ... Optimize images, fonts, and server response time', WCAG 4.5:1 contrast, meta description 150-160 chars), matching 'noticeably verbose; several unnecessary explanations or padded sections'. It is not a 3 because the padding is pervasive rather than a few stray over-explanations, and not a 1 because the material is organized rather than a formless wall.

2 / 5

Actionability

The 'How it works' section gives only high-level hints ('Analyze the provided code/project for quality issues') with no executable commands, and the bundled scripts/analyze.sh is never referenced or invoked from the body. This matches 'minimal concrete guidance; high-level hints but missing the specific steps to execute'. It is not a 3 because there is no executable code or command sequence to run the audit, and not a 1 because the output-format template and severity table offer some concrete structure.

2 / 5

Workflow Clarity

A four-step sequence is listed (Analyze, Categorize by severity, Provide recommendations, Include code examples) but with no validation or verification checkpoints, matching 'steps listed but validation gaps; sequence present but checkpoints missing or implicit'. It is not a 4 because no checkpoints or feedback loops are present, and not a 2 because the steps are coherent and in a sensible order.

3 / 5

Progressive Disclosure

The References section clearly signals one-level-deep sibling-skill links, but the 150+ inlined checks remain in SKILL.md rather than being split into reference files, and the bundled scripts/analyze.sh is never linked from the body. This matches 'some structure but could be better organized; references present but not clearly signaled; content that should be separate is inline'. It is not a 4 because of the unreferenced bundle script and the inlined bulk checklist, and not a 2 because structure and clear sibling references do exist.

3 / 5

Total

10

/

20

Passed

Description

90%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is excellent: it clearly states what the skill does, when to use it with concrete natural trigger phrases, and explicitly distinguishes it from sibling single-area skills. The only mild weakness is that the stated actions (audit/orchestrate) stay at a high level rather than enumerating concrete operations.

DimensionReasoningScore

Specificity

It names the domain ('web quality audit') and the four covered areas plus the verb 'orchestrates specialized skills', but the actions remain at the audit/review level rather than listing multiple concrete operations, matching the 'names domain and 1-2 concrete actions' anchor. It is not a 4 because it lacks several specific concrete actions, and not a 2 because it does name concrete areas and an orchestration action.

3 / 5

Completeness

It explicitly answers 'what' ('Comprehensive web quality audit covering performance, accessibility, SEO, and best practices in a single review') and 'when' with concrete trigger phrases, plus explicit negative guidance. This matches the 'clearly and explicitly answers both what AND when with concrete trigger phrases' anchor.

5 / 5

Trigger Term Quality

It includes natural phrases users would actually say — 'audit my site', 'review web quality', 'run lighthouse audit', 'check page quality', 'optimize my website' — giving comprehensive coverage with synonyms. It clearly exceeds the 4 anchor by spanning multiple natural variations rather than missing common terms.

5 / 5

Distinctiveness Conflict Risk

It carves a clear multi-area niche and explicitly steers away from siblings ('Do NOT use for single-area audits — prefer core-web-vitals, web-accessibility, seo, or web-best-practices'), yielding minimal conflict risk. It exceeds the 4 anchor by providing explicit disambiguation against closely related skills.

5 / 5

Total

18

/

20

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 5 suspicious

Warning

Total

15

/

16

Passed

Repository
tech-leads-club/agent-skills
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.