js-redirects

Use when auditing slow page loads, heavy assets, or rendering delays related to Avoid JavaScript-based redirects. Verify the actual bottleneck in DevTools, Lighthouse, or field data before recommending changes.

Quality

55%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/js-redirects/SKILL.md

Quality

Content

42%

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

The skill is well-structured for progressive disclosure — a lean overview pointing to a real references/rule.md — but the SKILL.md body itself is light on executable guidance and inline validation checkpoints, leaving most actionable and verification content to the reference.

Suggestions

Add one concrete inline example (e.g. a server-side redirect snippet or a DevTools/curl check command) so the body is actionable on its own rather than deferring all code to rule.md.

Include an explicit verify step in the body (e.g. 'Confirm the 3xx is gone via DevTools Network tab or curl -I before considering the fix done') to add a validation checkpoint to the workflow.

Trim the opening explanatory sentence about round-trips and waiting time, since Claude already understands why JS redirects are slow.

Dimension	Reasoning	Score
Conciseness	The body is short and largely free of padding, but sentences like 'JavaScript redirects force an additional round-trip after the initial page load, significantly increasing the time users spend waiting for content' explain a concept Claude already knows, which is mildly unnecessary given the brevity overall.	2 / 3
Actionability	Guidance is abstract: 'Replace JavaScript-based redirects with server-side 301 or 302 redirects in your web server or edge configuration' with no executable code or commands in the SKILL.md body (the example code lives only in the referenced rule.md, which is acceptable for progressive disclosure but the body itself gives no concrete, copy-paste-ready instruction).	1 / 3
Workflow Clarity	Sections (Check, Fix, Explain, Code Review) provide a recognizable sequence, and the description frontmatter urges verifying the bottleneck before recommending changes, but the body lacks explicit validation checkpoints or a measure→confirm loop for the fix; the verifying guidance lives in the reference rather than inline.	2 / 3
Progressive Disclosure	The body is a concise overview that cleanly defers full details to a single, well-signaled one-level-deep reference ('see references/rule.md'), and the referenced file exists in the bundle, matching the good structure anchor.	3 / 3
	Total	8 / 12 Passed

Description

67%

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 has an explicit 'Use when' trigger and answers both what and when, but its trigger phrasing leans on generic performance symptoms (slow loads, heavy assets) rather than the skill's distinctive redirect focus, weakening distinctiveness and specificity.

Suggestions

Lead with the redirect-specific trigger, e.g. 'Use when auditing client-side JavaScript redirects (window.location) that add latency...' so the natural keyword 'redirects' appears up front.

Add the core remediation action to the description — replacing JS redirects with server-side 301/302 redirects — so capabilities are concrete and comprehensive, not just auditing.

Surface natural terms users would actually say ('redirects', 'window.location', 'SEO redirects') to improve trigger term coverage.

Dimension	Reasoning	Score
Specificity	Quotes 'auditing slow page loads, heavy assets, or rendering delays' and 'Verify the actual bottleneck in DevTools, Lighthouse, or field data before recommending changes' name the domain and some concrete actions (audit, verify bottleneck), but the actions are not comprehensive — there is no mention of the core action of replacing JS redirects with server-side 301/302 redirects.	2 / 3
Completeness	Clearly answers both what (auditing slow page loads/heavy assets/rendering delays related to JS redirects and verifying the bottleneck) and when ('Use when auditing slow page loads, heavy assets, or rendering delays') with an explicit 'Use when' trigger clause.	3 / 3
Trigger Term Quality	Includes relevant terms users would say like 'slow page loads,' 'heavy assets,' and 'rendering delays,' plus tool names 'DevTools' and 'Lighthouse,' but lacks common variations a user might say such as 'JavaScript redirects,' 'window.location,' 'redirects,' or 'SEO' as natural triggers.	2 / 3
Distinctiveness Conflict Risk	The 'Avoid JavaScript-based redirects' niche is fairly specific, but the opening 'Use when auditing slow page loads, heavy assets, or rendering delays' is generic performance phrasing that overlaps with many performance skills; the redirect-specificity only appears mid-sentence.	2 / 3
	Total	9 / 12 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
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: thedaviddias/Front-End-Checklist
Path: skills/js-redirects/SKILL.md
Commit: 48405aa

Reviewed: about 12 hours 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.