CtrlK
BlogDocsLog inGet started
Tessl Logo

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". Do NOT use for accessibility (use web-accessibility), SEO (use seo), performance (use core-web-vitals), or comprehensive multi-area audits (use web-quality-audit).

63

Quality

75%

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-best-practices/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

68%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.

A well-organized, highly actionable catalog of web best-practice patterns with strong code examples and clear section navigation. Its weaknesses are the absence of an explicit audit workflow with validation feedback loops and the monolithic single-file layout that could offload detail into reference files.

Suggestions

Add an explicit audit workflow with validation checkpoints (e.g. run npm audit -> review findings -> apply fixes -> re-run audit -> only stop when clean) to support the batch 'security audit' trigger.

Move the detailed per-area code catalogs (security headers/CSP, deprecated APIs, compatibility patterns) into one-level-deep reference files and keep SKILL.md as a concise overview with clearly signaled links.

Replace placeholder identifiers (errorTracker, showErrorMessage, showPermissionExplanation) with concrete, runnable snippets or explicitly mark them as illustrative placeholders.

DimensionReasoningScore

Conciseness

The body is mostly lean ❌/✅ code examples with minimal prose and assumes Claude's competence; minor trimmable redundancy exists (the audit checklist re-lists items already shown, and some inline comments restate the obvious), keeping it just below fully lean.

4 / 5

Actionability

Abundant concrete, mostly copy-paste-ready code, headers, and commands (npm audit, CSP, HSTS); minor gaps from placeholder identifiers like errorTracker.captureException, showErrorMessage, and showPermissionExplanation that are not executable as written.

4 / 5

Workflow Clarity

This is a pattern catalog rather than a sequenced workflow; the closing audit checklist gives a rough order of checks but lacks explicit validation/re-run feedback loops for what is effectively a batch audit, which caps workflow clarity at 3.

3 / 5

Progressive Disclosure

Good single-file structure with clear section headers and a clearly signaled Tools table and References list; the minor gap is that all ~600 lines of detailed per-area examples are inlined in SKILL.md rather than split into one-level-deep reference files.

4 / 5

Total

15

/

20

Passed

Description

82%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.

A strong, well-structured description with explicit trigger phrases and excellent negative boundary guidance that sharply limits conflict with sibling skills. The main weakness is the single generic action verb 'Apply', which undersells the concrete capabilities.

Suggestions

Replace the generic 'Apply' with two or three concrete actions (e.g. 'Audit, fix, and document web security, compatibility, and code-quality issues') to lift specificity.

Add a couple of common synonyms to the trigger list such as 'lint', 'security review', or 'code review' for fuller keyword coverage.

DimensionReasoningScore

Specificity

Names the domain ('modern web development best practices') and three concrete areas (security, compatibility, code quality), but the only action verb is the generic 'Apply', so it stops short of listing several specific concrete actions.

3 / 5

Completeness

Explicitly answers both what (apply best practices for security, compatibility, code quality) and when (concrete 'Use when asked to...' trigger phrases), with additional negative boundary guidance as a bonus.

5 / 5

Trigger Term Quality

Includes five natural phrases users would actually say ('apply best practices', 'security audit', 'modernize code', 'code quality review', 'check for vulnerabilities'); a few plausible synonyms (e.g. 'lint', 'security review', 'code review') are missing, keeping it just below comprehensive.

4 / 5

Distinctiveness Conflict Risk

The explicit 'Do NOT use for accessibility/SEO/performance/comprehensive audits' clause with named sibling skills gives it a clear niche and minimal conflict risk.

5 / 5

Total

17

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (617 lines); consider splitting into references/ and linking

Warning

relative_links

Relative link issues: 1 suspicious

Warning

Total

14

/

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.