best-practices

Apply modern web development best practices for security, compatibility, and code quality. Use when asked to "apply best practices", "security audit", "modernize code", "code quality review", or "check for vulnerabilities".

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

82%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 content is a high-quality, code-dense reference: highly actionable with executable examples and a clear audit workflow backed by a real one-level reference file. The main gap is conciseness/progressive-disclosure trade-off — the body inlines a lot of material that, in a strict overview-and-reference model, could live in additional bundle files.

Suggestions

Move the larger code pattern collections (e.g. deprecated APIs, performance, code-quality examples) into a COMPATIBILITY.md / PATTERNS.md reference and keep SKILL.md as a tighter overview with the audit workflow and checklist, improving both conciseness and progressive_disclosure.

Make the audit workflow's exit/checkpoint conditions explicit (e.g. 'Stop when no new high/critical findings remain on re-run') to push workflow_clarity to 5.

Dimension	Reasoning	Score
Conciseness	The body is dominated by lean ❌/✅ code examples with almost no concept explanation Claude lacks (no 'what is HTTPS' padding), though the overall length is high and a few sections (e.g. the full React ErrorBoundary class) are more elaborate than strictly needed, keeping it just below anchor 5.	4 / 5
Actionability	Nearly every section gives executable, copy-paste-ready code or concrete commands (doctype/charset/viewport HTML, feature-detection JS, npm audit, lighthouse_audit MCP call, webpack devtool configs), covering the common cases, matching anchor 5.	5 / 5
Workflow Clarity	The 'Evidence-led audit workflow' is a clear numbered 4-step sequence with a feedback loop ('Fix the implicated code, re-run the same audit') plus a closing checklist, but checkpoints are slightly implicit (e.g. when to stop supplementing runtime evidence) so it sits at anchor 4 rather than 5.	4 / 5
Progressive Disclosure	Security detail is split into a clearly-signaled, one-level-deep reference ('Read [the security reference](references/SECURITY.md) when security is in scope') and the body is well-sectioned, but a large volume of pattern examples is inlined in SKILL.md rather than split into further reference files, so it does not fully reach the anchor 5 'overview pointing to detailed materials' ideal.	4 / 5
	Total	17 / 20 Passed

Description

78%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 strong: it explicitly answers both what and when with multiple natural trigger phrases in third person. Its main weakness is that the action language is generic ('apply best practices') and the triggers under-cover the compatibility domain it claims.

Suggestions

Replace the generic verb with one or two concrete actions (e.g., 'Audit rendered pages for security, compatibility, and code-quality issues, and apply fixes') to lift specificity.

Add compatibility-oriented trigger phrases such as 'browser compatibility check' or 'is my code modern' to round out trigger coverage across all three stated domains.

Dimension	Reasoning	Score
Specificity	Names the domain ('modern web development') and three focus areas ('security, compatibility, and code quality') but the only action is the generic verb 'Apply...best practices' with no concrete operations, matching anchor 3 rather than 4 which requires several specific actions.	3 / 5
Completeness	Clearly states what ('Apply modern web development best practices for security, compatibility, and code quality') and an explicit 'Use when asked to...' clause with concrete trigger phrases, matching the anchor 5 example.	5 / 5
Trigger Term Quality	Provides several natural phrases users would say — '"apply best practices"', '"security audit"', '"modernize code"', '"code quality review"', '"check for vulnerabilities"' — but coverage is incomplete: no compatibility/browser-support synonyms despite compatibility being a stated focus, so it sits below anchor 5.	4 / 5
Distinctiveness Conflict Risk	Distinct, specific triggers reduce conflict risk, but the broad 'web development best practices' niche overlaps with closely related skills (the body itself references a sibling web-quality-audit skill), placing it at anchor 4 rather than 5.	4 / 5
	Total	16 / 20 Passed

Validation

93%

Warnings & errors only

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
relative_links	Relative link issues: 1 suspicious	Warning

	Total	15 / 16 Passed

Repository: addyosmani/web-quality-skills
Path: skills/best-practices/SKILL.md
Commit: afa8da9

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

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.